As an experiment, I was trying to get the software "vmaf" working to calculate the overall quality of a processed video with respect to the original video.
The original video is in avi format, with the processed video based on the original video is now in mp4 format using h265 codec.
I tried to follow the "tutorial" here - vmaf_ffmpeg_windows_tutorial.
Downloaded and installed the modified ffmpeg and the associated "models" as described within the tutorial, and installed them in the default locations (C:\ffmpeg and C:\ffmpeg\model). But every time I run the ffmpeg command within an elevated command window, I get error messages about unable to find/use some option? Possibly a file path issue as described within the tutorial, so I tried forward slashes and back slashes in various combinations for the model file path but I continue to receive the same (or similar) error message about unable to find/use the option!?
[Attachment 76819 - Click to enlarge]
What is wrong here?
Any ideas?
Try StreamFab Downloader and download from Netflix, Amazon, Youtube! Or Try DVDFab and copy Blu-rays!
+ Reply to Thread
Results 1 to 8 of 8
Thread
-
-
escape for colon , change to forward slashes
Code:-lavfi "libvmaf=model_path='C\:/ffmpeg/model/vmaf_v0.6.1.json'"
You will get the wrong results for AVI and MP4 if they use different timebase
There is an example of the syntax used for different container timebases. But it should be 1/AVTB
https://ffmpeg.org/ffmpeg-filters.html#Examples-92 -
Thanks for the reply!
Unfortunately I still get the error message appearing?
Syntax used is basically the same as yours -
Code:-lavfi "libvmaf=model_path='Ç\:/ffmpeg/model/vmaf_v0.6.1.json'" -f null -
Further ideas? -
They keep on changing the syntax every few months.
EDIT: sorry not working, just a secLast edited by poisondeathray; 6th Feb 2024 at 21:18.
-
That article was from 2020. It probably changed a few times in between
This last month should look like this for windows:
Code:-lavfi "libvmaf=model='path=C\\\:/ffmpeg/model/vmaf_v0.6.1.json'"
-
Many thanks for taking the time to find the (current) correct syntax!!
Yes, the latest syntax works!
Why on earth do they keep changing the syntax!? It makes things unnecessarily difficult for users!
Similar Threads
-
Please help me get ffmpeg's sws_dither option working
By Videogamer555 in forum Video ConversionReplies: 6Last Post: 14th Dec 2023, 15:56 -
ffmpeg aresample=async=1 not working on command line
By gareth41 in forum Video ConversionReplies: 5Last Post: 16th Feb 2022, 03:13 -
Lut3d not working on Ffmpeg
By jonathancolledge in forum EditingReplies: 1Last Post: 6th Jun 2021, 12:24 -
Axiom FFmpeg stopped working
By jooj in forum AudioReplies: 1Last Post: 10th Nov 2019, 14:24 -
Audio rate not working ffmpeg
By Budman1 in forum Video ConversionReplies: 2Last Post: 28th Sep 2019, 15:13