summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--ChangeLog5
-rw-r--r--ext/soundtouch/gstpitch.cc6
2 files changed, 10 insertions, 1 deletions
diff --git a/ChangeLog b/ChangeLog
index 97930237..ba7b54d3 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,6 +1,11 @@
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>
+
+ * ext/soundtouch/gstpitch.cc:
* ext/soundtouch/gstpitch.hh:
Implement LATENCY query and notify about latency changes.
Unfortunately we don't have a fixed latency but it changes
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)));
}