[Bug 691570] [isomp4/qtdemux] lots of critical warnings on this sample file

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Fri Nov 29 12:55:30 PST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=691570
  GStreamer | gst-plugins-good | 1.x

Thiago Sousa Santos <thiago.sousa.santos> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|1.0.6                       |1.3.1
         OS/Version|Linux                       |All

--- Comment #8 from Thiago Sousa Santos <thiago.sousa.santos at collabora.co.uk> 2013-11-29 20:49:18 UTC ---
commit 45c16599ff4a3d674bd651cdb3babbc00af8d06c
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Fri Nov 15 08:54:07 2013 -0300

    qtdemux: avoid re-reading the same moov and entering into loop

    In the scenario of "mdat | moov (with fragmented artifacts)" qtdemux
    could read the moov again after the mdat because it was considering the
    media as a fragmented one.

    To avoid this loop this patch makes it store
    the last processed moov_offset to avoid parsing it again.
    And it also checks if there are any samples to play before
    resturning to the mdat, so that it knows there is new data to be played.

    https://bugzilla.gnome.org/show_bug.cgi?id=691570

commit fcc78aa3bdff35574425e2953e8bd119279d6354
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Fri Nov 15 00:52:53 2013 -0300

    qtdemux: do not free streams if they were not created locally

    When parsing a trak only free streams on failures if those streams
    were created locally. They could have been created from a previous
    fragment, in this case we they have valid info from the other fragment.
    Including pads.

    https://bugzilla.gnome.org/show_bug.cgi?id=691570

-- 
Configure bugmail: https://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