[FFmpeg-trac] #2210(undetermined:new): AC3 channel layout change midstream causes severe errors

FFmpeg trac at avcodec.org
Sun Feb 24 12:10:10 CET 2013


#2210: AC3 channel layout change midstream causes severe errors
-------------------------------------+-------------------------------------
             Reporter:  agni451      |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:  async        |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by agni451):

 Looks like you're getting the same results as me.  I noticed you tried

 {{{
 ffmpeg -async 1 -skip_initial_bytes 170M -i Ticket2210.ts -qscale 2 -t 25
 outasync1.avi
 }}}

 with -async 1.  I've found that it does the exact same thing as -async
 48000 (fills in the odd gap) even though the documentation says it is a
 special case that only corrects the initial delay and nothing else.

 That -async command is a real timesaver; until I discovered that it worked
 to fill gaps I had to use a combination of an MPEG2 repair tool to log
 errors and a small piece of software of my own design to add the silence
 to fill the gaps.  Unfortunately, it was only correct maybe 80% of the
 time so I would end up taking a lot of time to make sure everything was
 correct and manually crop/pad the audio when it wasn't.  -Async works
 perfectly every time EXCEPT when a channel change is encountered.  If I
 was more than an amateur at programming I would try to find out which
 which library is responsible for the confusion and suggest a correction.
 I am not, however, so all I can do is give the experts a decent sample.
 I'm glad I finally found one, and I hope it helps find the source of the
 error.  Let me know if there's anything else I can do.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2210#comment:20>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list