ext/soundtouch/gstpitch.cc: Don't send a LATENCY event for now until we get the usage...

Original commit message from CVS:
* ext/soundtouch/gstpitch.cc:
Don't send a LATENCY event for now until we get the usage right.

diff --git a/ChangeLog b/ChangeLog
index 97930237a1a86f59aedd828b41e94fc5be400fe2..ba7b54d32d9ba9b1245cc79eea7fe1fecfa1c37d 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -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>
 
        * ext/soundtouch/gstpitch.cc:

diff --git a/ext/soundtouch/gstpitch.cc b/ext/soundtouch/gstpitch.cc
index 9e68fda4cdd1e2482b18d69ddd68c883d38d151d..b25322987b66a1d244ddc5b5a1f902f04c9bea9b 100644 (file)
--- 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)));
   }