I've been encoding some clips and then analyzing them with the VMAF tool from Netflix, but I don't know how to understand the results.

This is the overall mean section of one of my tests.


The numbers don’t mean anything. They only have value when compared to other values. You can compare the results between two encodes of the same file and determine which encode produced better results.

| improve this answer | |
  • How do I decide what a good threshold is? Like, If I make encodes with varying bitrates, I know more is better, but how much is enough? – chew socks Jun 5 '18 at 20:54
  • That’s subjective. You get to decide what is “good enough” for your case. – SlimSCSI Jun 5 '18 at 21:57
  • If you wanted to encode something so that your average non-expert wouldn't be able to tell the difference from the original, what numbers would you target? ;) – chew socks Jun 6 '18 at 3:31
  • Like @SlimSCSI said, the scores are relative to the source material. There is no specific number to shoot for. If you are tweaking the encoder on a case by case basis, you can compare different settings by score. If you are setting up a "factory" workflow, run several test files through to find the better settings. If you are doing a QC workflow, you will have to experiment with your threshold for your specific set up. – Michael Liebman Jun 6 '18 at 19:12
  • 1
    I found on the mux.com blog that a difference of 6 is barely noticeable. "A 6-point difference is VMAF is considered a Just-Noticeable-Difference." – chew socks Jun 12 '18 at 23:07

In general, the higher the VMAF score, the higher the quality of the video will be perceived by the viewer. Lower VIF component and ADM scores indicate problems caused by intra-frame compression artifacts. A lower motion score indicates problems caused by inter-frame compression artifacts.

| improve this answer | |
  • What scale is VMAF_feature_motion2_score on? I can tell the others are from 0-1, but not what the maximum of VMAF_feature_motion2_score is. – chew socks Jun 5 '18 at 20:49
  • I don't know what the scale is. It doesn't seem to be described in the blog post, but you should be able to determine it from the source code. – Michael Liebman Jun 6 '18 at 19:16
  • 1
    I found it in the README, it varies from 0 to 20. – chew socks Jun 12 '18 at 23:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.