Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: MCC CS <mcccs@gmx.com>
To: ffmpeg-devel@ffmpeg.org, timo@rothenpieler.org
Subject: Re: [FFmpeg-devel] Guidance needed for a semi-breaking change
Date: Wed, 27 Apr 2022 15:06:04 +0200
Message-ID: <trinity-cb78ccd0-d360-45b0-9d74-5a862628fccb-1651064764104@3c-app-mailcom-bs12> (raw)
In-Reply-To: <d2fd5490-10b7-136a-a9df-04b506659b00@rothenpieler.org>

I wasn't considering a breaking change, those using
-aac_at_quality 0 or -aac_at_quality 2 would continue to use those.
However, would moving -aac_at_quality 0 from HIGH (currently highest
used by FFMPEG) to MAX be welcome? I'd assume that those using
-aac_at_quality 0 do so to use the highest quality option available.

If not, extending the range (0,2) to (-1,3) without moving any
previous options would work. From what I understand negative
numbers are OK in ffmpeg since `-q:a -1` produces higher quality
than `-q:a 0` for me.

How about this?

Thanks again

Sent: Wednesday, April 27, 2022 at 1:49 PM
From: "Timo Rothenpieler" <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Guidance needed for a semi-breaking change
You need to keep API and ABI compatibility, cause otherwise it's a
breaking change which can only happen at a major bump.
Any and all existing applications and commandline need to keep working
as they do right now.

What you could do is convert the option into a OPT_TYPE_CONST one, and
offer the new values as actual textual option, and set up the numerical
values so that they align with what's currently offered.
_______________________________________________
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:[~2022-04-27 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 12:42 MCC CS
2022-04-27 12:49 ` Timo Rothenpieler
2022-04-27 13:06   ` MCC CS [this message]
2022-04-27 13:15     ` Timo Rothenpieler
2022-04-27 13:18       ` Nicolas George
2022-04-27 14:07         ` MCC CS
2022-04-27 15:18           ` Timo Rothenpieler
2022-04-27 18:05             ` MCC CS

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=trinity-cb78ccd0-d360-45b0-9d74-5a862628fccb-1651064764104@3c-app-mailcom-bs12 \
    --to=mcccs@gmx.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=timo@rothenpieler.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