[gstreamer-bugs] [Bug 329198] GStreamer-CRITICAL: gst_pad_activate_pull: assertion `old == GST_ACTIVATE_NONE' failed

[GStreamer (bugzilla.gnome.org)]

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=329198
 GStreamer | gst-plugins-good | Ver: HEAD CVS


Jan Schmidt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thaytan at mad.scientist.com,
                   |                            |wim at fluendo.com
         AssignedTo|gstreamer-                  |thaytan at mad.scientist.com
                   |bugs at lists.sourceforge.net  |




------- Comment #5 from Jan Schmidt  2006-01-30 13:32 UTC -------
Yeah, I've seen this too - it happens on any file that has ID3 information, but
where GStreamer can't detect the type within ID3 (broken mp3 files, as Mitch
says, among others)

I'm not quite sure where the failure is in the chain of events, but it goes
something like this:

decodebin detects that the file contains ID3 tags and connects id3demux
id3demux reads the id3 tag(s) and then attempts to determine the type of the
file within the id3 tag(s).
It can't detect the type, sends an error message, and returns FALSE from the
pad activation.
Decodebin ignores the error that id3demux didn't change state and continues on.
It doesn't have any more dynamic elements, so completes its state change.
The typefind element switches to PUSH mode.
As decodebin proceeds to state PAUSED, the core attempts to activate the
id3demux pads again, causing id3demux to attempt to activate PULL mode on
typefind's src pad, which fails because typefind is already in push mode.

There are a couple of places in this sequence where things aren't working
perfectly, I'm just not sure what it SHOULD like so I can't fix it.


-- 
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.