summaryrefslogtreecommitdiffstats
path: root/ext
diff options
context:
space:
mode:
authorSebastian Dröge <slomo@circular-chaos.org>2008-01-27 07:51:06 +0000
committerSebastian Dröge <slomo@circular-chaos.org>2008-01-27 07:51:06 +0000
commit7fa405c9c92ba15c9074e8a50b05d2e65acad8c3 (patch)
tree99ab2eae0bf35e11ed73626ba1ccb3c6135ee2f6 /ext
parent26b4a028d98811c91740b48fbaf461aba77a083d (diff)
downloadgst-plugins-bad-7fa405c9c92ba15c9074e8a50b05d2e65acad8c3.tar.gz
gst-plugins-bad-7fa405c9c92ba15c9074e8a50b05d2e65acad8c3.tar.bz2
gst-plugins-bad-7fa405c9c92ba15c9074e8a50b05d2e65acad8c3.zip
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.
Diffstat (limited to 'ext')
-rw-r--r--ext/soundtouch/gstpitch.cc6
1 files changed, 5 insertions, 1 deletions
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)));
}