mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-04-26 06:54:49 +00:00
Code Issues 1 Projects Releases Wiki Activity

libs/gst/base/gstbasesink.c: Forward LATENCY events upstreams so that elements know about the total pipeline latency....

Browse source 
Original commit message from CVS:
* libs/gst/base/gstbasesink.c: (gst_base_sink_send_event):
Forward LATENCY events upstreams so that elements know about the total
pipeline latency. Fixes #555307.
This commit is contained in:
Wim Taymans 2008-10-08 14:21:13 +00:00
parent 18e2042e28
commit 1fb53a23a1
2 changed files with 12 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
ChangeLog
View file

@ -1,3 +1,9 @@
2008-10-08 Wim Taymans <wim.taymans@collabora.co.uk>
* libs/gst/base/gstbasesink.c: (gst_base_sink_send_event):
Forward LATENCY events upstreams so that elements know about the total
pipeline latency. Fixes #555307.
2008-10-08 Jan Schmidt <jan.schmidt@sun.com> 2008-10-08 Jan Schmidt <jan.schmidt@sun.com>
* plugins/elements/gstqueue.c: * plugins/elements/gstqueue.c:

13
libs/gst/base/gstbasesink.c
View file

@ -1605,6 +1605,9 @@ no_clock:
* to a state change to READY or a FLUSH event (in which case this function * to a state change to READY or a FLUSH event (in which case this function
* returns #GST_FLOW_WRONG_STATE). * returns #GST_FLOW_WRONG_STATE).
* *
* This function should only be called with the PREROLL_LOCK held, like in the
* render function.
*
* Since: 0.10.11 * Since: 0.10.11
* *
* Returns: #GST_FLOW_OK if the preroll completed and processing can * Returns: #GST_FLOW_OK if the preroll completed and processing can
@ -3128,13 +3131,9 @@ gst_base_sink_send_event (GstElement * element, GstEvent * event)
GST_DEBUG_OBJECT (basesink, "latency set to %" GST_TIME_FORMAT, GST_DEBUG_OBJECT (basesink, "latency set to %" GST_TIME_FORMAT,
GST_TIME_ARGS (latency)); GST_TIME_ARGS (latency));
/* don't forward, yet. FIXME. The latency event should likely be forwarded /* We forward this event so that all elements know about the global pipeline
* to upstream element so that they can configure themselves. Each element * latency. This is interesting for an element when it wants to figure out
* would subtract the amount of LATENCY it can maximally compensate for. * when a particular piece of data will be rendered. */
* It's currently not very useful; even if this sink cannot compensate for
* all the latency, upstream will block while this sink waits which will
* trigger implicit buffering and latency there. */
forward = FALSE;
break; break;
} }
default: default: