[FFmpeg-devel] [PATCH] Add detail to the documentation for ffmpeg -map.

Stefano Sabatini stefano.sabatini-lala
Sun Feb 27 15:00:27 CET 2011

On date Tuesday 2011-02-15 13:49:23 -0500, Ronald S. Bultje encoded:
> Hi,
> On Tue, Feb 15, 2011 at 1:43 PM, Mike Scheutzow
> <mike.scheutzow at alcatel-lucent.com> wrote:
> >> [PATCH] Add detail to the documentation for ffmpeg -map.
> >
> > Ping.
> It looks a lot better than the original text to me.
> Maybe add another example for simple 1-file input to 1-file output
> (but the input file has two audio streams and you want to drop one of
> them). That's the "simple" case of your "a little more complex"
> example (which is actually very helpful).
> To prevent other often-occurring FAQs, add a last example for 1 input
> file to multiple output files.
> But anyway, what I really wanted to say is that I prefer to leave
> doc-patches for our doc experts.

Updated with more additions and examples.

I also changed the syntax suggested by the doc:
@item -map @var{input_file_id}:@var{input_stream_id}[:@var{sync_file_id}:@var{sync_stream_id}]
@item -map
@var{input_file_id}. at var{input_stream_id}[:@var{sync_file_id}. at var{sync_stream_id}]

'.' is more consistent with the av_dump_format() output, and more
readable (but opt_map() accepts any separator with non-numerical
characters, for example also "0?1" will do).

BTW I also suggest to add a -dry-run option, this should help to check
the mapping before the output is actually burnt.
FFmpeg = Faithful Fancy Mean Philosofic Eager Guru

More information about the ffmpeg-devel mailing list