[Bug 710609] New: ASF demux : bug fix - check mo_size

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Tue Oct 22 09:53:27 CEST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=710609
  GStreamer | gst-plugins-ugly | 1.0.7

           Summary: ASF demux : bug fix - check mo_size
    Classification: Platform
           Product: GStreamer
           Version: 1.0.7
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-ugly
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: meeshel78 at hotmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=257818)
 View: https://bugzilla.gnome.org/attachment.cgi?id=257818
 Review: https://bugzilla.gnome.org/review?bug=710609&attachment=257818

bug fix - check mo_size field is not mandatory. So, don't need to mo_size value
check when merge the payload.

Media object size is not mandatory field in ASF specification.

And actually, some file has no media object size field in payload except first
payload of each ES data.
Like this....
1st payload : mo_id = 1, mo_offset = 0, mo_size = 8021 bytes
2nd payload : mo_id = 1, mo_offset = 2500  (has no mo_size)
3rd payload : mo_id = 1, mo_offset = 5000 (has no mo_size)

But asf demux always check the previous payload's media object size and current
payload's media object size when merge it.

Cause of it, some file always fail to parse payload.

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