[gstreamer-bugs] [Bug 320984] [oggdemux] cannot handle multiple chains

[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=320984

  GStreamer | gst-plugins-base | Ver: HEAD CVS


Philip Allison changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sane at not.co.uk




------- Comment #24 from Philip Allison  2007-01-22 02:10 UTC -------
I have also been experiencing this bug, and can confirm that it is indeed in
oggdemux - the key is in the segment_start value calculated when a new chain
starts, as the OP guessed.

I have taken the liberty of attaching a patch which, in my small test player
(using decodebin), seems to alleviate stream hangs. Old line 1046 looks like
the most likely candidate for causing breakage, as subtracting
chain->begin_time from chain->segment_start is effectively subtracting
something from zero (segment start times are relative to the current time, it
seems, where as begin_time is absolute).

However, with the patch applied, the problem becomes one of __dropping__ data.
I'm not an expert on GStreamer terminology (this is the first time I've looked
at the source), but it sounds to my ears as if some buffer is being prematurely
flushed whenever a new chain starts. The test stream from comment #1 doesn't
stop playing like it used to, but it definitely doesn't sound contiguous.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email