From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/3] doc/encoders/libx264: review and extend option description Date: Sun, 19 Nov 2023 12:34:09 +0100 Message-ID: <ZVnysXjfaHjoJ+Ww@mariano> (raw) In-Reply-To: <ZUa3ArDmlrmZ2PTn@mariano> On date Saturday 2023-11-04 22:26:27 +0100, Stefano Sabatini wrote: > On date Wednesday 2023-09-06 11:04:49 +0530, Gyan Doshi wrote: > [...] > > Sorry for the slow reply. > > > > -Argument is a list of @var{key}=@var{value} couples separated by > > > -":". In @var{filter} and @var{psy-rd} options that use ":" as a separator > > > -themselves, use "," instead. They accept it as well since long ago but this > > > -is kept undocumented for some reason. > > > +@option{x264-param} is functionally the same as the @option{x264opts}, > > > +but is duplicated for compatibility with the Libav fork. > > > > There is a difference, in that x264opts accepts boolean args without a > > value. > > Right. > > > > + > > > +The argument for both options is a list of @var{key}=@var{value} > > > +couples separated by ":". In @var{filter} and @var{psy-rd} options > > > +that use ":" as a separator themselves, use "," instead. They accept > > > +it as well since long ago but this is kept undocumented for some > > > +reason. > > > + > > > +For example, the options might be provided as: > > > +@example > > > +level=30:bframes=0:weightp=0:cabac=0:ref=1:vbv-maxrate=768:vbv-bufsize=2000:analyse=all:me=umh:no-fast-pskip=1:subq=6:8x8dct=0:trellis=0 > > > +@end example > > > For example to specify libx264 encoding options with @command{ffmpeg}: > > > @example > > > ffmpeg -i foo.mpg -c:v libx264 -x264opts keyint=123:min-keyint=20 -an out.mkv > > > @end example > > > +To get the complete list of the libx264 options, invoke the command > > > +@command{x264 --fullhelp} or consult the libx264 documentation. > > > > > May want to make it clear that x264 refers to the standalone CLI tool. > > Isn't that clear enough? (we use the same formula in other places, > e.g. in x265 docs). > > From a11eafe5a61a572f4e9ab9e4ab9907bba98300e4 Mon Sep 17 00:00:00 2001 > From: Stefano Sabatini <stefasab@gmail.com> > Date: Sat, 26 Aug 2023 01:10:09 +0200 > Subject: [PATCH] doc/encoders/libx264: review and extend option description > > Also, merge x264opts and x264-opts option docs to avoid duplication > and make it clearer that they provide mostly the same functionality. > --- > doc/encoders.texi | 65 ++++++++++++++++++++++++++--------------------- > 1 file changed, 36 insertions(+), 29 deletions(-) Will apply in a few days if I see no comments. _______________________________________________ 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-11-19 11:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-26 1:10 Stefano Sabatini 2023-08-26 1:10 ` [FFmpeg-devel] [PATCH 2/3] lavc: clarify meaning of avctx.level option Stefano Sabatini 2023-08-26 1:10 ` [FFmpeg-devel] [PATCH 3/3] doc/encoders/libx264: clarify meaning of level option Stefano Sabatini 2023-09-06 5:37 ` Gyan Doshi 2023-10-06 7:54 ` Stefano Sabatini 2023-09-05 23:11 ` [FFmpeg-devel] [PATCH 1/3] doc/encoders/libx264: review and extend option description Stefano Sabatini 2023-09-06 5:34 ` Gyan Doshi 2023-11-04 21:26 ` Stefano Sabatini 2023-11-19 11:34 ` Stefano Sabatini [this message] 2023-12-03 12:06 ` 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=ZVnysXjfaHjoJ+Ww@mariano \ --to=stefasab@gmail.com \ --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