diff options
| author | Tim-Philipp Müller <tim@centricular.net> | 2007-02-08 11:09:15 +0000 |
|---|---|---|
| committer | Tim-Philipp Müller <tim@centricular.net> | 2007-02-08 11:09:15 +0000 |
| commit | 6bbee3202a6e6df043f3d441a2bf4dbc25aae3d4 (patch) | |
| tree | d8e9ecaba9e0c88f6e41fd09630a7b546d49090d | |
| parent | ba2af9fa122e0393c8cd61e3fc78f5feb2742471 (diff) | |
gst/debug/progressreport.c: Some more docs.
Original commit message from CVS:
* gst/debug/progressreport.c:
Some more docs.
| -rw-r--r-- | ChangeLog | 5 | ||||
| -rw-r--r-- | gst/debug/progressreport.c | 12 |
2 files changed, 17 insertions, 0 deletions
@@ -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: diff --git a/gst/debug/progressreport.c b/gst/debug/progressreport.c index 0c59b1f5..2650a239 100644 --- a/gst/debug/progressreport.c +++ b/gst/debug/progressreport.c @@ -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> |