Reference:
Use cases
Exact Match
Comparing encoded results to original media for comparision comparison of RGB 2 YCrCb conversion. For this case we want minimal encoding and want to compare exactly.
...
https://richardssam.github.io/ffmpeg-tests/tests/chip-chart-yuvconvert/compare.html is a example output.
Need: Critical.
These would be used as part of a unit-test framework.
Approximate match to baseline.
Matching encoded results to original media, but results will not be exact. We want to use VMAF to help with approximate comparison.
We would be using this to confirm that known baselines are creating the same result.
Need: Critical.
These would be used as part of a unit-test framework.
Wedging results
Comparison to baseline.
We would like to be able to produce charts like in:
https://codecalamity.com/hardware-encoding-4k-hdr10-videos/
- VMAF vs Bitrate for 4 different encoders – 5 different bitrate settings, for a single piece of media.
https://codecalamity.com/encoding-uhd-4k-hdr10-videos-with-ffmpeg/
- VMAF vs. CRF for 10 settings. (Seemingly testing for a range of CRF calies)
- Duration vs. CRF
Note, these are probably good for one off tests, to create documents, although might be good for re-running tests for new versions of encoders.
The creation of graphs would be nice to be automatic, but definately a bonus, if somebody ended up doing those "by hand" it would be fine.
What we would be using this for is to provide end-users an idea of what certain settings produceCompare results of a test suite against historical results. The goal is to identify cases where ffmpeg may have changed, and encoding scheme may need to change.