#10801(undetermined:new): -map + filter causes two copies of a stream in recent versions
#10801: -map + filter causes two copies of a stream in recent versions -------------------------------------+------------------------------------- Reporter: TomTop | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- In recent versions of FFmpeg (eg. 6.1), the following command line will not work as it did with older versions (eg. 4.4): {{{ % ffmpeg -i input -map 0:0 -map 0:1 -filter_complex "[0:0]scale=1280:-1" ... output }}} Usually this would result in a file where stream 0 is scaled to width 1280 and stream 1 is the audio. In newer versions of FFmpeg, the result holds the two expected streams and an unexpected copy of the original video, most likely due to the -map 0:0 argument. Is this a bug or a change in how FFmpeg works? -- Ticket URL: <https://trac.ffmpeg.org/ticket/10801> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#10801: -map + filter causes two copies of a stream in recent versions --------------------------------+---------------------------------- Reporter: TomTop | Owner: (none) Type: defect | Status: new Priority: normal | Component: ffmpeg Version: 6.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------- Changes (by TomTop): * version: unspecified => 6.1 * component: undetermined => ffmpeg -- Ticket URL: <https://trac.ffmpeg.org/ticket/10801#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#10801: -map + filter causes two copies of a stream in recent versions --------------------------------+----------------------------------- Reporter: TomTop | Owner: (none) Type: defect | Status: closed Priority: normal | Component: ffmpeg Version: 6.1 | Resolution: invalid Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+----------------------------------- Changes (by Gyan): * status: new => closed * resolution: => invalid Comment: It was the earlier behaviour that was buggy. A stream exiting a complex filtergraph has to be included in an output file. Earlier, if such a stream was unlabelled, any explicitly mapped stream of the same media type would be ignored. That was fixed in 6.0. See the chapter on [https://ffmpeg.org//ffmpeg.html#Stream-selection Stream selection]. The correct way to filter a mapped stream is to specify a simple filterchain. This is done via `-vf / -filter:v:X` for video and `-af / -filter:a:X` for audio where X is the ''output'' stream index of that type. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10801#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg