[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):

 I spent the last week creating a very complicated Windows script, but now
 I'm ready to follow-up on this ticket.
 In the last few minutes I altered the script to save the intermediate
 (temp) file (before stripping out the duplicate streams) that has all the
 original streams, doubled.
 You are correct and I was wrong: The 1st set of streams are from '-map 0'
 and the 2nd set of streams are the ones added by '-filter_complex
 "[0:v]settb=expr=1/24,setpts=expr=N[v];[0:a]atempo=1.001[a]" -map "[v]"
 -map "[a]"' -- I used MKVToolNixGUI to figure it out, saving the lower
 numbered streams to one output and the higher numbered streams to another
 output.

 I don't know how my mistake happened and I appolgize for it -- having a
 script should avoid such a mistake in the future.

 I'm going to do more testing with more movies to see whether the sets of
 streams (one from '-map 0' and the other from the '-filter_complex')
 remain reproduceable.

 The bottom line remains: Without '-map 0' in the command, 'atempo' does
 not take affect.

 Should I prepare an entire new presentation and ticket, or should I append
 a new presentation to this ticket? Your call.

 Regards,
 -Mark.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9337#comment:8>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker