Skip to content

Support FFmpeg's libvmaf v2.0.0 arguments #724

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

Open
veikk0 opened this issue Feb 13, 2023 · 1 comment
Open

Support FFmpeg's libvmaf v2.0.0 arguments #724

veikk0 opened this issue Feb 13, 2023 · 1 comment

Comments

@veikk0
Copy link

veikk0 commented Feb 13, 2023

Since about a year ago, FFmpeg has supported the new libvmaf API and features, the most significant of which is that the VMAF models are now included in the library itself. So there's no need to point to model files anymore, unless you're using a self-trained/third-party one. So for example, specifying the 4K model is simply done with libvmaf=model=version=vmaf_4k_v0.6.1. Currently to use anything other than the default model with Av1an, you need to download the model in question and use --vmaf-path to specify the model file.

See also #659 and #488.

Also, it would be useful if Av1an used the 4K VMAF model by default for output files significantly larger than 1920x1080. The default model is trained to predict quality on a 1080p HDTV, and for anything larger than that the 4K model should probably be used. av-av1 does this by default (for resolutions larger than 1440p I believe).

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

No branches or pull requests

2 participants
@veikk0 and others