Commit adfd199b authored by Wim Taymans's avatar Wim Taymans

docs/design/draft-latency.txt: Updates.

Original commit message from CVS:
* docs/design/draft-latency.txt:
Updates.
* gst/gstelement.h:
* gst/gststructure.c:
* gst/gsttrace.c:
Small typo fixes.
parent 2b633222
2007-01-09 Wim Taymans <wim@fluendo.com>
* docs/design/draft-latency.txt:
Updates.
* gst/gstelement.h:
* gst/gststructure.c:
* gst/gsttrace.c:
Small typo fixes.
2007-01-09 Tim-Philipp Müller <tim at centricular dot net>
* tests/check/.cvsignore:
......
......@@ -293,20 +293,20 @@ A flush in a pipeline can happen in the following cases:
- flushing seek in the pipeline
- performed by the application on the pipeline
- performed by the application on and element
- performed by the application on an element
- flush preformed by an element
- after receiving a navigation event (DVD, ...)
When a playing sink is flushed by a FLUSH_START event, a LOST_PLAYING message is
When a playing sink is flushed by a FLUSH_START event, a LOST_PREROLL message is
posted and kept by the parent bin. When the element prerolls, it posts a
PREROLLED message.
When all LOST_PLAYING messages are matched with a PREROLLED message, the bin
When all LOST_PREROLL messages are matched with a PREROLLED message, the bin
will capture a new base time from the clock and will bring all the prerolled
sinks back to playing after setting the new base time on them. It's also
possible to add additional latency calculations.
The difference with the NEED_PREROLL/PREROLLED and LOST_PLAYING/PREROLLED
The difference with the NEED_PREROLL/PREROLLED and LOST_PREROLL/PREROLLED
message pair is that the latter makes the pipeline acquire a new base time for
the PREROLLED elements.
......
......@@ -254,7 +254,7 @@ typedef enum
/**
* GST_ELEMENT_ERROR:
* @el: the element that throws the error
* @el: the element that generates the error
* @domain: like CORE, LIBRARY, RESOURCE or STREAM (see #GstGError)
* @code: error code defined for that domain (see #GstGError)
* @text: the message to display (format string and args enclosed in
......@@ -263,7 +263,7 @@ typedef enum
enclosed in parentheses)
*
* Utility function that elements can use in case they encountered a fatal
* data processing error. The pipeline will throw an error signal and the
* data processing error. The pipeline will post an error message and the
* application will be requested to stop further media processing.
*/
#define GST_ELEMENT_ERROR(el, domain, code, text, debug) \
......@@ -281,7 +281,7 @@ G_STMT_START { \
/**
* GST_ELEMENT_WARNING:
* @el: the element that throws the error
* @el: the element that generates the warning
* @domain: like CORE, LIBRARY, RESOURCE or STREAM (see #GstGError)
* @code: error code defined for that domain (see #GstGError)
* @text: the message to display (format string and args enclosed in
......@@ -290,7 +290,7 @@ G_STMT_START { \
enclosed in parentheses)
*
* Utility function that elements can use in case they encountered a non-fatal
* data processing problem. The pipeline will throw a warning signal and the
* data processing problem. The pipeline will post a warning message and the
* application will be informed.
*/
#define GST_ELEMENT_WARNING(el, domain, code, text, debug) \
......
......@@ -890,8 +890,8 @@ gst_structure_foreach (const GstStructure * structure,
* @user_data: private data
*
* Calls the provided function once for each field in the #GstStructure. In
* contrast to gst_structure_foreach(), the function may modify the fields. The
* structure must be mutable.
* contrast to gst_structure_foreach(), the function may modify but not delete the
* fields. The structure must be mutable.
*
* Returns: TRUE if the supplied function returns TRUE For each of the fields,
* FALSE otherwise.
......
......@@ -248,7 +248,7 @@ static GList *_gst_alloc_tracers = NULL;
/**
* gst_alloc_trace_available:
*
* Check if alloc tracing was commiled into the core
* Check if alloc tracing was compiled into the core
*
* Returns: TRUE if the core was compiled with alloc
* tracing enabled.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment