[gstreamer-bugs] [Bug 429322] [matroska-demux] hangs if file starts at non-zero timestamp

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

  GStreamer | gst-plugins-good | Ver: 0.10.5

Sebastian Dröge changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #86292|0                           |1
        is obsolete|                            |
         AssignedTo|slomo at circular-chaos.org    |gstreamer-
                   |                            |bugs at lists.sourceforge.net
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.9




------- Comment #4 from Sebastian Dröge  2008-06-19 08:22 UTC -------
2008-06-19  Sebastian Dröge  <slomo at circular-chaos.org>

        * gst/matroska/matroska-demux.c:
        (gst_matroska_demux_parse_blockgroup_or_simpleblock):
        If a gap of more than 1/2 second is found in one stream send a
        NEWSEGMENT event to not stall the pipeline if the gap is too large.
        This also fixes Matroska files where the first buffer doesn't start
        at timestamp 0. Fixes bug #429322.

        The duration of a block is the default duration multiplied with the
        number of laces. Every lace is one frame and the default duration
        is the duration of one frame. This fixes playback of files that use
        lacing for some tracks.


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