ffmpeg without in-build models
External VMAF model should be specified as model_path=file.json
ffmpeg with in-build models
External VMAF model should be specified as model=path=file.json
If the model specified in old format as model_path=file.json, ffmpeg says that model_path option is deprecated and model=path=... should be used.
In fact, it will not use the external VMAF model at all and defaulting to in-build model vmaf_v0.6.1.
So, for now json models must not be used with ffmpeg that supports in-build VMAF models (alternatively, Filter can be re-defined in FFMetrics.conf to workaround the issue).
To fix the issue, model_path must not be used if in-build VMAF models are supported by ffmpeg.
P.S. Probably the same issue is with options phone_model and pool (have not checked yet)
fifonik
commented
1 year ago
ffmpeg without in-build models External VMAF model should be specified as
model_path=file.jsonffmpeg with in-build models External VMAF model should be specified as
model=path=file.jsonIf the model specified in old format asmodel_path=file.json, ffmpeg says that model_path option is deprecated andmodel=path=...should be used. In fact, it will not use the external VMAF model at all and defaulting to in-build model vmaf_v0.6.1.So, for now json models must not be used with ffmpeg that supports in-build VMAF models (alternatively, Filter can be re-defined in FFMetrics.conf to workaround the issue). To fix the issue, model_path must not be used if in-build VMAF models are supported by ffmpeg.
P.S. Probably the same issue is with options phone_model and pool (have not checked yet)