GNOME Bugzilla – Bug 699767
typefind: send stream-start after caps
Last modified: 2013-05-07 07:17:58 UTC
The typefind element let segment event go through and sends caps later. This may cause miss ordering of sticky event in pads. It should, arguably, delay the segment event (and buffer, if not already) until it has send the caps event.
Didn't I just fix that in master last week?
I've just updated now and I still get the miss-ordering. To reproduce: Apply this patch to gstreamer, https://bug688188.bugzilla-attachments.gnome.org/attachment.cgi?id=243398 (it will add a warning when sticky event are miss-ordered and run the following pipline (source file type is not important): GST_DEBUG=2 gst-launch-1.0 filesrc location=test.webm ! typefind ! fakesink
It actually behaves differently with the update, it sends the stream-start after the caps. Updating title accordingly.
Created attachment 243442 [details] [review] typefind: Send stream-start before anything else I'm now sending the stream-start when the streaming thread is up for the first time.
Thanks for spotting this :) I missed that last week commit ba354f6b03f6862c502f2d127c0a552a72963cb1 Author: Nicolas Dufresne <nicolas.dufresne@collabora.com> Date: Mon May 6 18:47:44 2013 -0400 typefind: Send stream-start before anything else To do so, send stream-start when the streaming thread goes up for the first time. https://bugzilla.gnome.org/show_bug.cgi?id=699767