[gstreamer-bugs] [Bug 399264] pipeline fails to preroll with Vorbis/Theora clip

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=399264

  GStreamer | gst-plugins | Ver: 0.10.11

Jan Schmidt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thaytan at mad.scientist.com




------- Comment #13 from Jan Schmidt  2009-03-30 22:20 UTC -------
I just found this bug browsing through the bugs list. I can reproduce the issue
just fine.

The bug is related to the way decodebin handles it's internal buffers. It tries
to grow the buffers to ensure that the amount of buffering is kept as small as
possible, but large enough to cope with the muxing offset in the input. In this
case, it's failing badly, due to a big FIXME in the queue_underrun_cb function
in decodebin.c - the pipeline has underruns on the theora path, but it doesn't
trigger the expansion of the vorbis path buffering because it proved to be too
difficult to figure out or something.

The bug is gone with decodebin2, which uses an internal multiqueue element to
manage the buffering.

This pipeline works fine, by artificially adding buffering to the vorbis chain
gst-launch-0.10 filesrc location=A_New_Computer--small.ogg ! queue ! decodebin
name=decode decode. ! queue max-size-time=2000000000 ! audioconvert !
audioresample ! autoaudiosink decode. ! queue ! ffmpegcolorspace ! videoscale !
autovideosink

Is using decodebin2 a sufficient fix for you?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=399264.