mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-06-07 07:58:51 +00:00
ext/soundtouch/gstpitch.cc: Don't send a LATENCY event for now until we get the usage right.
Original commit message from CVS: * ext/soundtouch/gstpitch.cc: Don't send a LATENCY event for now until we get the usage right.
This commit is contained in:
parent
26b4a028d9
commit
7fa405c9c9
2 changed files with 10 additions and 1 deletions
|
@ -1,3 +1,8 @@
|
||||||
|
2008-01-27 Sebastian Dröge <slomo@circular-chaos.org>
|
||||||
|
|
||||||
|
* ext/soundtouch/gstpitch.cc:
|
||||||
|
Don't send a LATENCY event for now until we get the usage right.
|
||||||
|
|
||||||
2008-01-27 Sebastian Dröge <slomo@circular-chaos.org>
|
2008-01-27 Sebastian Dröge <slomo@circular-chaos.org>
|
||||||
|
|
||||||
* ext/soundtouch/gstpitch.cc:
|
* ext/soundtouch/gstpitch.cc:
|
||||||
|
|
|
@ -818,7 +818,11 @@ gst_pitch_update_latency (GstPitch * pitch, GstClockTime timestamp)
|
||||||
pitch->min_latency = min_latency;
|
pitch->min_latency = min_latency;
|
||||||
pitch->max_latency = max_latency;
|
pitch->max_latency = max_latency;
|
||||||
|
|
||||||
gst_pad_push_event (pitch->sinkpad, gst_event_new_latency (max_latency));
|
/* FIXME: what about the LATENCY event? It only has
|
||||||
|
* one latency value, should it be current, min or max?
|
||||||
|
* Should it include upstream latencies?
|
||||||
|
*/
|
||||||
|
|
||||||
gst_element_post_message (GST_ELEMENT (pitch),
|
gst_element_post_message (GST_ELEMENT (pitch),
|
||||||
gst_message_new_latency (GST_OBJECT (pitch)));
|
gst_message_new_latency (GST_OBJECT (pitch)));
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue