Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Allow AOM_HAVE_TUNE_IQ #2599

Closed
wants to merge 1 commit into from
Closed

Conversation

vrabaud
Copy link
Collaborator

@vrabaud vrabaud commented Feb 7, 2025

No description provided.

@vrabaud vrabaud added this to the v1.2.0 milestone Feb 7, 2025
@vrabaud
Copy link
Collaborator Author

vrabaud commented Feb 7, 2025

wantehchang@, is that what you had in mind? The libaom bump is just for the tests

@vrabaud vrabaud requested a review from wantehchang February 7, 2025 12:39
Copy link
Collaborator

@wantehchang wantehchang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vincent: Thanks for looking into this.

apps/avifenc.c Show resolved Hide resolved
src/codec_aom.c Show resolved Hide resolved
cmake/Modules/LocalAom.cmake Show resolved Hide resolved
if (!lossless && !codec->internal->tuningSet) {
#if defined(AOM_HAVE_TUNE_IQ)
if (aomUsage == AOM_USAGE_ALL_INTRA &&
aom_codec_control(&codec->internal->encoder, AOME_SET_TUNING, AOM_TUNE_IQ) != AOM_CODEC_OK) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not ready to make AOM_HAVE_TUNE_IQ the default in libavif yet. But we can think about how to make the new tuning mode more discoverable.

For example, if we release libavif v1.2.0 after libaom v3.12.0 is released, we can mention the libaom codec-specific option tune=iq in the libavif v1.2.0 release notes.

@wantehchang wantehchang removed this from the v1.2.0 milestone Feb 8, 2025
@wantehchang
Copy link
Collaborator

Vincent: I removed the v1.2.0 milestone from this pull request. It should not require any change to libavif to use the new tune=iq codec-specific option in libaom v3.12.0.

@gitoss
Copy link

gitoss commented Feb 9, 2025

Vincent: I removed the v1.2.0 milestone from this pull request. It should not require any change to libavif to use the new tune=iq codec-specific option in libaom v3.12.0.

I've compiled latest git libaom-av1 + libavif and can confirm --codec aom --advanced tune=iq works (without changing the hardcoded limits for older aom versions).

We are not ready to make AOM_HAVE_TUNE_IQ the default in libavif yet. But we can think about how to make the new tuning mode more discoverable.

The new tune should only be default for non-animated avif, otherwise there's an error " * aom_codec_set_option("tune", "iq") failed: Codec does not implement requested capability:"

That's probably because tune=iq sets --deltaq-mode=6 which "can only be set in all intra mode". The exact command line with --advanced tune=iq works just fine with single-image input.

@vrabaud
Copy link
Collaborator Author

vrabaud commented Feb 11, 2025

Ok, let's wait for setting it by default then.

@vrabaud vrabaud closed this Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants