[libav-bugs] [Bug 1080] New: Fixing aac-adts header parsing for byte sequence 0xFF 0xFF 0xF1

bugzilla at libav.org bugzilla at libav.org
Thu Aug 31 05:02:40 CEST 2017


https://bugzilla.libav.org/show_bug.cgi?id=1080

            Bug ID: 1080
           Summary: Fixing aac-adts header parsing for byte sequence 0xFF
                    0xFF 0xF1
           Product: Libav
           Version: git HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: ---
         Component: libavcodec
          Assignee: bugzilla at libav.org
          Reporter: rohit.bansal at samsung.com

Created attachment 680
  --> https://bugzilla.libav.org/attachment.cgi?id=680&action=edit
Patch file for the fix

if some aac file has following sequence of bytes is 0xFF 0xFF 0xF1 ...., then
current adts parsing logic considers 0xFF 0xFF as the start of header, this
leads to wrong parsing and subsequently wrong frames are output.

As per specification, layer should be 0. So we can add this enhancement to
correctly identify the adts sync byte position.

Patch file attached.

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.libav.org/pipermail/libav-bugs/attachments/20170831/4555a509/attachment.html>


More information about the libav-bugs mailing list