[FFmpeg-trac] #2309(undetermined:new): Continuing -async issues

FFmpeg trac at avcodec.org
Wed Feb 27 14:15:27 CET 2013


#2309: Continuing -async issues
-------------------------------------+-------------------------------------
             Reporter:  agni451      |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:  async        |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by agni451):

 I just created this ticket, but I'd like to add a new finding.  I have a 1
 hour TS file named "full.ts".  I trimmed from this two files "change.ts"
 and "nochange.ts"

 {{{
 ffmpeg -y -i "full.ts" -vcodec copy -acodec copy -ss 00:43:33.000 -t 270
 "change.ts"
 }}}

 {{{
 ffmpeg -y -i "full.ts" -vcodec copy -acodec copy -ss 00:45:13.000 -t 170
 "nochange.ts"
 }}}

 If you look closely, the files start at different times but end at the
 same time.  This way, "change.ts" includes commercials that cause a 2ch--
 6ch change, while "nochange.ts" starts after this and so does not include
 a channel change.

 I then used two different versions of ffmpeg: dc8dd2f (1-29-2013) and
 f6fff8e (2-26-2013) to create four avi files thus:

 {{{
 ffmpeg_1_29.exe -y -i "change.ts" -q:vscale 0 -mbd 2 -acodec ac3 -ab 384k
 -ac 6 -async 48000 "change_1_29.avi"
 }}}

 {{{
 ffmpeg_1_29.exe -y -i "nochange.ts" -q:vscale 0 -mbd 2 -acodec ac3 -ab
 384k -ac 6 -async 48000 "nochange_1_29.avi"
 }}}

 {{{
 ffmpeg_2_26.exe -y -i "change.ts" -q:vscale 0 -mbd 2 -acodec ac3 -ab 384k
 -ac 6 -async 48000 "change_2_26.avi"
 }}}

 {{{
 ffmpeg_2_26.exe -y -i "nochange.ts" -q:vscale 0 -mbd 2 -acodec ac3 -ab
 384k -ac 6 -async 48000 "nochange_2_26.avi"
 }}}

 I expected "change_1_29.avi" to have failed because that version of ffmpeg
 did not yet have the fix from Ticket 2210.  It did fail.  I expected the
 "nochange_1_29.avi" to be just fine, and it was.  I expected
 "change_2_26.avi" to be good since the fix had been released.  It was just
 fine.  I also expected "nochange_2_26.avi" to be fine, since it had no
 channel layout change and it worked fine for the older version. It failed.

 Summary:

 change_1_29.avi    FAIL
 nochange_1_29.avi  SUCCESS
 change_2_26.avi    SUCCESS
 nochange_2_26.avi  FAIL

 For some reason the latest version works fine with a channel change AND
 any errors encountered after that (gaps, timestamp drift), but when there
 is NO channel change, it chokes on the gaps and timestamp drift errors
 that older versions handled just fine.

 Let me know if you want a copy of "change.ts" and "nochange.ts".  They are
 large, together equaling about 900MB (the size is necessary to encompass
 all errors).

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


More information about the FFmpeg-trac mailing list