-
Notifications
You must be signed in to change notification settings - Fork 29
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
VMAF calculation issue with recent FFmpeg git #142
Comments
Looking through the ab-av1 repository, I can't really find a reason why VMAF calculation is done with pipes instead of a single FFmpeg command. If the reason is pixel format conversion, then the format filter is the way to go. I believe |
Yep pixel format & vfilter. It may be worth trying to crunch it into a single call. I'd need to regression test such a change. |
#177 changes vmaf to a single ffmpeg call. In my testing this produces identical results to previous code though much simpler and easier to reproduce in a manual ffmpeg call. |
Nice! I'll do some before-after testing too and report back. |
#WorksForMe |
I'm having an issue with extremely low (~1) VMAF scores when using an FFmpeg built from recent git code. The score is always this low with any CRF, and ab-av1 keeps going lower and lower until the size of
max-encoded-percent
is reached and it exits.I've tracked the issue down to the following FFmpeg commit: FFmpeg/FFmpeg@c94e9d0
Calculating VMAF normally using FFmpeg still works fine.
The text was updated successfully, but these errors were encountered: