FaSTTUBe/GST-Tensordecoder-ov_ep
61
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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:
Sebastian Dröge 2008-01-27 07:51:06 +00:00
parent 26b4a028d9
commit 7fa405c9c9
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -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:

6
ext/soundtouch/gstpitch.cc
View File

@ -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)));
} }