mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-25 01:30:38 +00:00
Code Issues 1 Projects Releases Wiki Activity

gst/debug/progressreport.c: Some more docs.

Browse source 
Original commit message from CVS:
* gst/debug/progressreport.c:
Some more docs.
This commit is contained in:
Tim-Philipp Müller 2007-02-08 11:09:15 +00:00
parent ba2af9fa12
commit 6bbee3202a
2 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
2007-02-08 Tim-Philipp Müller <tim at centricular dot net>
* gst/debug/progressreport.c:
Some more docs.
2007-02-07 Tim-Philipp Müller <tim at centricular dot net>
* docs/plugins/inspect/plugin-rtp.xml:

12
gst/debug/progressreport.c
View file

@ -47,6 +47,18 @@
* progress in TIME format, the element is best placed in a 'raw stream'
* section of the pipeline (or after any demuxers/decoders/parsers).
* </para>
* <para>
* Three more things should be pointed out: firstly, the element will only
* query progress when data flow happens. If data flow is stalled for some
* reason, no progress messages will be posted. Secondly, there are other
* elements (like qtdemux, for example) that may also post "progress" element
* messages on the bus. Applications should check the source of any element
* messages they receive, if needed. Finally, applications should not take
* action on receiving notification of progress being 100%, they should only
* take action when they receive an EOS message (since the progress reported
* is in reference to an internal point of a pipeline and not the pipeline as
* a whole).
* </para>
* <title>Example launch line</title>
* <para>
* <programlisting>