mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-01-09 08:55:33 +00:00
Code Issues 1 Projects Releases Wiki Activity

Small docs fixes.

Browse source 
Original commit message from CVS:
* docs/design/part-live-source.txt:
* gst/gstclock.h:
Small docs fixes.
This commit is contained in:
Wim Taymans 2006-10-18 13:21:56 +00:00
parent 5e4699885a
commit c0a833edca
3 changed files with 21 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
ChangeLog
View file

@ -1,3 +1,9 @@
2006-10-18 Wim Taymans <wim@fluendo.com>
* docs/design/part-live-source.txt:
* gst/gstclock.h:
Small docs fixes.
2006-10-18 Tim-Philipp Müller <tim at centricular dot net>
* gst/gstbuffer.h:

18
docs/design/part-live-source.txt
View file

@ -41,7 +41,17 @@ buffer arrives at the sink, it will already be late and will be dropped.
The latency is the time it takes to construct one buffer of data. This latency
could be exposed by latency queries.
Theses latency queries need to be done by the managing pipeline for all sinks.
They can only be done after the meassurements have been taken (all are
prerolled). Thus in pipeline:state_changed:PAUSED_TO_PLAYING we need
get the max-latency and set this as a sync-offset in all sinks.
Theses latency queries could to be done by the managing pipeline for all sinks.
In that case they can only be done after the meassurements have been taken (all
are prerolled). Thus in pipeline:state_changed:PAUSED_TO_PLAYING we need
get the max-latency and set this as a sync-offset in all sinks. The problem is
that in a live pipeline, we set the pipeline to PLAYING before waiting for the
sinks to preroll.
Another possibility would be to configure a fixed latency in a pipeline that
would automatically be configured on any sink in the case of a NO_PREROLL
element. For decoupled elements this is practically the only viable way to
introduce enough latency that does not starve the sinks.
The current latency can also be measured in the sinks and the pipeline could
optimize it to the lowest possible latency.

2
gst/gstclock.h
View file

@ -204,7 +204,7 @@ typedef struct _GstClockClass GstClockClass;
* @clock: The clock that triggered the callback
* @time: The time it was triggered
* @id: The #GstClockID that expired
* @user_data: user data passed in the async_wait call
* @user_data: user data passed in the gst_clock_id_wait_async() function
*
* The function prototype of the callback.
*