[FFmpeg-trac] #9337(ffmpeg:new): 'atempo' didn't work unless '-map 0' was added

[FFmpeg]

#9337: 'atempo' didn't work unless '-map 0' was added
-------------------------------------+----------------------------------
             Reporter:  markfilipak  |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  ffmpeg
              Version:  git-master   |               Resolution:
             Keywords:  atempo       |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+----------------------------------
Comment (by markfilipak):

 Replying to [comment:5 Gyan]:
 > Replying to [comment:4 markfilipak]:
 > > Sorry, I guess replying to the email doesn't work. So, I'll repeat my
 reply here, now.
 > >
 > > Hi Gyan, Thanks.
 > >
 > > Actually, it's the other way around; [0:0] & [0:1] are from the graph
 and [0:3] & [0:4] are from '-map 0'. Yes, that was surprising, but it's
 not really the issue.
 >
 >
 > Check again. From 3.log
 >
 > '''
 > Stream #0:0 -> #0:0 (mpeg2video (native) -> hevc (libx265))
 > Stream #0:1 -> #0:1 (ac3 (native) -> ac3 (native))
 > setpts (graph 0) -> Stream #0:2 (libx265)
 > atempo (graph 0) -> Stream #0:3 (ac3)
 > '''

 A sidetrack: Ah! You're right. Sorry. But something is strange. 4.mkv is:

 {{{
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
   Stream #0:1 -> #0:1 (copy)
 }}}

 and has synchonized audio as shown when the boy slams the screen door (so
 'atempo' in the graph worked for them), while 5.mkv is:

 {{{
 Stream mapping:
   Stream #0:2 -> #0:0 (copy)
   Stream #0:3 -> #0:1 (copy)
 }}}

 (so are from '-map 0').
 Something is backwards.

 To the real issue, why does 'atempo' not work unless I add '-map 0'?
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9337#comment:6>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker