From 7fa405c9c92ba15c9074e8a50b05d2e65acad8c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= Date: Sun, 27 Jan 2008 07:51:06 +0000 Subject: 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. --- ChangeLog | 5 +++++ ext/soundtouch/gstpitch.cc | 6 +++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 97930237..ba7b54d3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2008-01-27 Sebastian Dröge + + * ext/soundtouch/gstpitch.cc: + Don't send a LATENCY event for now until we get the usage right. + 2008-01-27 Sebastian Dröge * ext/soundtouch/gstpitch.cc: diff --git a/ext/soundtouch/gstpitch.cc b/ext/soundtouch/gstpitch.cc index 9e68fda4..b2532298 100644 --- a/ext/soundtouch/gstpitch.cc +++ b/ext/soundtouch/gstpitch.cc @@ -818,7 +818,11 @@ gst_pitch_update_latency (GstPitch * pitch, GstClockTime timestamp) pitch->min_latency = min_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_message_new_latency (GST_OBJECT (pitch))); } -- cgit v1.2.1