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

CRF-SEARCh with nvenc way off based compared to finished product score #228

Open
raysv opened this issue Oct 22, 2024 · 1 comment
Open

Comments

@raysv
Copy link

raysv commented Oct 22, 2024

Hi,
was about to check out how nvenc is fearing with HEVC now, and did two Episodes of a series to test.
Useing crf-search with min-samples 6, and with the crf its giving me, it should produce vmaf score of 95.
However, when i after encoding it run a full vmaf check on both episodes, the actuall vmaf ended up being vmaf 40.6 and 41.7.

Any snuggestions to why this might happend? The size of the files however is pretty spot on.

@raysv
Copy link
Author

raysv commented Oct 25, 2024

Seems like its the files that have VC1 that this problem is with, if the original is in AVC its better. However CRFSEARCH still overshoots VMAF usually with up to 2-3 points, so when ab-av1 says it will end up at 95, it end product usually is 92-93. Any tips to what to tweak to get it alittle closer?

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

1 participant