From: Anton Khirnov <anton@khirnov.net> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH 3/3] doc/ffmpeg: expand -bsf documentation Date: Tue, 19 Sep 2023 20:15:07 +0200 Message-ID: <20230919181507.7445-3-anton@khirnov.net> (raw) In-Reply-To: <20230919181507.7445-1-anton@khirnov.net> Explain how to pass options to filters. --- doc/ffmpeg.texi | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi index d2864ff37e..cf47eb68d1 100644 --- a/doc/ffmpeg.texi +++ b/doc/ffmpeg.texi @@ -1893,9 +1893,18 @@ ffmpeg -i inurl -streamid 0:33 -streamid 1:36 out.ts @end example @item -bsf[:@var{stream_specifier}] @var{bitstream_filters} (@emph{output,per-stream}) -Set bitstream filters for matching streams. @var{bitstream_filters} is -a comma-separated list of bitstream filters. Use the @code{-bsfs} option -to get the list of bitstream filters. +Apply bitstream filters to matching streams. + +@var{bitstream_filters} is a comma-separated list of bitstream filter +specifications that will be applied to coded packets in the order they are +written in. Each bitstream filter specification is of the form +@example +@var{filter}[=@var{optname0}=@var{optval0}:@var{optname1}=@var{optval1}:...] +@end example +Any of the ',=:' characters that are to be a part of an option value need to be +escaped with a backslash. + +Use the @code{-bsfs} option to get the list of bitstream filters. @example ffmpeg -i h264.mp4 -c:v copy -bsf:v h264_mp4toannexb -an out.h264 @end example -- 2.40.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-09-19 18:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-19 18:15 [FFmpeg-devel] [PATCH 1/3] tests/fate/ffmpeg: replace deprecated -vbsf with -bsf:v Anton Khirnov 2023-09-19 18:15 ` [FFmpeg-devel] [PATCH 2/3] tests/fate: replace deprecated -vsync with -fps_mode Anton Khirnov 2023-09-19 18:15 ` Anton Khirnov [this message] 2023-09-29 6:30 ` [FFmpeg-devel] [PATCH 3/3] doc/ffmpeg: expand -bsf documentation Stefano Sabatini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230919181507.7445-3-anton@khirnov.net \ --to=anton@khirnov.net \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git