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

[FFmpeg]

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

Comment (by agni451):

 I downloaded both the 2-25-2013 and 2-26-2013 static builds and tested a
 bunch of files with them, and they all seemed to work great.
 Unfortunately, I stumbled upon a new glitch that doesn't occur in builds
 066739f (2-24-2013) and earlier.  I uploaded a 1:40min sample file along
 with short [-v verbose] and long [-v verbose -loglevel 99] outputs running
 under 066739f (1-29-2013) and f6fff8e (2-26-2013).  The 1-29 build handles
 the error approx 11sec in just fine, but the 2-26 build goes crazy and
 adds too much silence (~12sec worth).  Oddly enough, there is NO channel
 layout change in this sample to deal with, just a standard gap error and
 timestamp "drift".

 The exact command I used was
 {{{
 ffmpeg64.exe -v verbose -y -i "K:\!TEST\Dsmall.ts" -c:v mpeg2video
 -q:vscale 0 -mbd 2 -c:a ac3 -ab 448k -ac 6 -async 48000
 "K:\!TEST\D_FIX.ts"
 }}}

 but outputting an avi shows the audio error:
 {{{
 ffmpeg64.exe -v verbose -y -i "K:\!TEST\Dsmall.ts" -q:vscale 0 -mbd 2 -c:a
 ac3 -ab 448k -ac 6 -async 48000 "K:\!TEST\bad.avi"
 }}}

 Basically ffmpeg now handles channel layout changes fine (as far as my
 testing has confirmed), but now it occasionally has problems with gap and
 timestamp drift errors.  I say occasionally because I ran the sample I
 gave in comment 18 (it has channel changes AND gaps AND timestamp drift)
 and it didn't have a problem.  I'm hoping you can see why one would have a
 problem and not the other.  If you need a new copy of the sample from
 comment 18, I can re-upload it.

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