[FFmpeg-devel] Guidance needed for a semi-breaking change

[MCC CS]

The default for AAC_AT is to produce highest quality audio, which I'll keep undoubtedly
in the same direction. However, the question is this:

Should the one who explicitly set `-aac_at_quality 0` (highest quality available) be moved from HIGH to MAX,
HOWEVER causing the side effect of moving everyone up in the quality-speed tradeoff by one,

(or we can eliminate HIGH and just replace it with MAX which has no tradeoffs AFAIK)

OR add `-1`, so that only those who entered no `aac_at_quality` be moved to -1,
and keeping explicit people having set `-aac_at_quality 0` at HIGH for them,
although they might have meant MAX when they started using it?
(i.e. no regression nor improvement for them)

---
Sent: Wednesday, April 27, 2022 at 2:18 PM
From: "Nicolas George" <george at nsup.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel at ffmpeg.org>
Subject: Re: [FFmpeg-devel] Guidance needed for a semi-breaking change
Timo Rothenpieler (12022-04-27):
> Any existing commandline should produce the exact same output after the
> change.

I do not agree.

Small changes in default behavior are acceptable, since the user did not
specify what they want.

(I would argue that changes that fix a bug and changes that are
unambiguously and exclusively an improvement are acceptable.)

Regards,

--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".