[gstreamer-bugs] [Bug 342594] mad doesn't post new-segment after seek
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Sun May 28 05:27:57 PDT 2006
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=342594
GStreamer | gst-plugins-ugly | Ver: 0.10.3
------- Comment #4 from Michael Dominic K. 2006-05-28 12:27 UTC -------
So, the problems seems to be, that mad is pad-allocing a buffer before it sends
a new-segment event. As the pad-alloc triggers the (possible) pad-block, it
gives a false impression that the data is arriving on the pad before the
new-segment event.
I'm not sure if this is a bug or an acceptable behaviour. However, other
plugins always seem to send a new-segment before they alloc a buffer (block the
pad). I think that for consistency reasons mad should behave the same.
Patch attached. It moves the (possible) new-segment sending before the
pad-allocing.
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Gstreamer-bugs
mailing list