Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg_opt: inform user about -b:a and -b:v instead of legacy form
Date: Sat, 9 Dec 2023 13:32:07 -0600
Message-ID: <CA+28BfD=AB6ft+8qc3dN_LL+3ZB3ofDVtQY-O7u79=Fc93UuqA@mail.gmail.com> (raw)
In-Reply-To: <75460395-5a4b-4ac1-99df-23f2c01f2f09@gmail.com>

Roger, will update. Thanks!

On Sat, Dec 9, 2023 at 1:25 PM James Almer <jamrial@gmail.com> wrote:

> On 12/9/2023 4:10 PM, Marth64 wrote:
> > ---
> >   fftools/ffmpeg_opt.c | 8 ++++----
> >   1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/fftools/ffmpeg_opt.c b/fftools/ffmpeg_opt.c
> > index 304471dd03..5e50e5efa2 100644
> > --- a/fftools/ffmpeg_opt.c
> > +++ b/fftools/ffmpeg_opt.c
> > @@ -1721,8 +1721,8 @@ const OptionDef options[] = {
> >       { "force_key_frames", OPT_VIDEO | OPT_STRING | HAS_ARG |
> OPT_EXPERT |
> >                             OPT_SPEC | OPT_OUTPUT,
>            { .off = OFFSET(forced_key_frames) },
> >           "force key frames at specified timestamps", "timestamps" },
> > -    { "b",            OPT_VIDEO | HAS_ARG | OPT_PERFILE | OPT_OUTPUT,
>           { .func_arg = opt_bitrate },
> > -        "video bitrate (please use -b:v)", "bitrate" },
> > +    { "b:v",          OPT_VIDEO | HAS_ARG | OPT_PERFILE | OPT_OUTPUT,
>           { .func_arg = opt_bitrate },
> > +        "video bitrate", "bitrate" },
>
> "b" is for bitrate regardless of media type. The specifier that comes
> after it decides the type. You're probably breaking that by making "b"
> no longer be a valid option.
>
> IMO, change the description to "Stream bitrate".
>
> >       { "hwaccel",          OPT_VIDEO | OPT_STRING | HAS_ARG |
> OPT_EXPERT |
> >                             OPT_SPEC | OPT_INPUT,
>           { .off = OFFSET(hwaccels) },
> >           "use HW accelerated decoding", "hwaccel name" },
> > @@ -1762,8 +1762,8 @@ const OptionDef options[] = {
> >       { "acodec",         OPT_AUDIO | HAS_ARG  | OPT_PERFILE |
> >                           OPT_INPUT | OPT_OUTPUT,
>             { .func_arg = opt_audio_codec },
> >           "force audio codec ('copy' to copy stream)", "codec" },
> > -    { "ab",             OPT_AUDIO | HAS_ARG | OPT_PERFILE |
> OPT_OUTPUT,            { .func_arg = opt_bitrate },
> > -        "audio bitrate (please use -b:a)", "bitrate" },
> > +    { "b:a",            OPT_AUDIO | HAS_ARG | OPT_PERFILE |
> OPT_OUTPUT,            { .func_arg = opt_bitrate },
> > +        "audio bitrate", "bitrate" },
>
> And this just removes "ab" altogether, which is a break with no previous
> warning. b:a already works thanks to "b" above.
>
> Just flag this option as deprecated.
>
> >       { "atag",           OPT_AUDIO | HAS_ARG  | OPT_EXPERT |
> OPT_PERFILE |
> >                           OPT_OUTPUT,
>             { .func_arg = opt_old2new },
> >           "force audio tag/fourcc", "fourcc/tag" },
> _______________________________________________
> 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".
>
_______________________________________________
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".

  reply	other threads:[~2023-12-09 19:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09 19:10 Marth64
2023-12-09 19:24 ` James Almer
2023-12-09 19:32   ` Marth64 [this message]
2023-12-10  1:46   ` [FFmpeg-devel] [PATCH] ffmpeg_opt: clarify that -ab is deprecated Marth64
2023-12-11 18:44   ` [FFmpeg-devel] [PATCH v2] " Marth64

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='CA+28BfD=AB6ft+8qc3dN_LL+3ZB3ofDVtQY-O7u79=Fc93UuqA@mail.gmail.com' \
    --to=marth64@proxyid.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