-
Notifications
You must be signed in to change notification settings - Fork 21
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
1.9.0 crashes with target VMAF #9
Comments
Pretty sure this is an av1an problem as it won't work with SVT 0.9.0. |
Ah, you're right. I checked a few days ago and didn't find any relevant issues, seems like i just barely missed this one master-of-zen/Av1an#556 Feel free to close. |
Upstream has fixed it, but it's not in any release yet. |
I tried the Target VMAF function but it doesn't seem to work for me with any encoder settings.
|
SVT does not work with target VMAF for now. Use CRF |
So is already known to not work with x265, AOM and VPX too? |
If needed that is the log folder of a partially worked try (It started but then stopped encoding with the same error in the prompt) |
So, based on test done: AOM target VMAF:
VPX target VMAF:
x265 target VMAF: Edit: Actually the result are not stable... now again VPX didn't worked |
Actually only a few times (almost none) I got errors that prevented the start of the encoding if I force to not use the system PATH but only the one of the program folder and run it from a folder on an HDD not SSD. Moreover using the latest version of av1an also SVT-AV1 works (recompiling from source, see here for compilation in windows master-of-zen/Av1an#529). I don't understand why on some files created with vpx encoder all metrics (psnr, ssim, vmaf) results on nmkoder are different from others tools. Like vmaf nmkoder: 96, ffmetrics: 25 Edit: Excluding the system path make the auto-crop feature don't work (error says ffmpeg dont have this filter). |
Settings as follows:
Let me know if you need more infos.
The text was updated successfully, but these errors were encountered: