ffmpeg-quality-metrics VS Av1an

Have you seen ffmpeg-quality-metrics? I went with the docker option. I figured that would keep it simple with ffmpeg versions/whatever.

I'm not good at computers, so I love ffmpeg-quality-metrics. I use the docker version because I didn't want to fight with dependencies.

There are even tools that can compare the quality for us, like ffmpeg-quality-metrics can give a VMAF score as used by Netflix for the visual quality difference.

You can at least test the quality difference between two encodes with something like ffmpeg-quality-metrics. If it has a high VMAF score and saved a bunch of space for something that doesn't need to be perfect, then I consider it fine.

ffmpeg-quality-metrics is nice for comparing quality between copies. Better than squinting at pixels IMO.

If you're re-encoding video then ffmpeg-quality-metrics is a great tool IMO. Can give you a scale from 0-100 of how similar it appears based on SSIM or VMAF. If I get a VMAF in the high 90's, like 95+, then I know the encode is decent and if it saved significant space (if that's the goal?) then it's a keeper.

It's working. I found this [model](https://github.com/slhck/ffmpeg-quality-metrics/blob/master/ffmpeg_quality_metrics/vmaf_models/vmaf_v0.6.1neg.json) with the help of u/Felixkruemel and I specified the vmaf path in av1an using `--vmaf-path=path to the/vmaf/model.json"`

Then, after the encode, if you want to compare original vs encoded quality there's ffmpeg-quality-metrics which makes it easy to get VMAF & SSIM scores between the two.

ffmpeg-quality-metrics is a good tool to compare before & after encodes. It can easily calculate VMAF & SSIM scores. If I understand it correctly (I might not), then anything in the high 90s for VMAF is considered hard-pressed to be able to tell. Sometimes it hits 100, which makes me fairly confident about those encodes.

idk. When I did a re-encode with CRF 23 and preset 'veryslow' it went down to 2,236 kb/s. When I do a VMAF and SSIM test with ffmpeg-quality-metrics I was getting decent scores. It takes the file size down to 2.1GB. So my guess is they either set a significantly lower CRF or set a manual bitrate and aimed for the moon.

The hardware encoders are very fast and generally better than x264 (but not by as much as you'd think with the x264 slow preset).

In addition, there are threaded AV1 encoders you may be overlooking, like SVT-AV1. For non-realtime, my favorite is av1an, which also yields better quality than is possible from aomenc: https://github.com/master-of-zen/Av1an

I specifically used https://github.com/master-of-zen/Av1an with --target-quality 100 to keep the compression as close to lossless as possible (you could probably shave even more size off if you didn’t use near-lossless compression)

There's also Av1an as suggested by someone else. It's going to produce more efficient encodes because it uses chunk-based encoding to reach the required VMAF for every single chunk, but this is also slower because every chunk will be re-encoded until the VMAF target is reached. It's also a PITA to compile, has a long list of bugs, and isn't very actively developed. One of the long-standing issues is that frames have a tendency to go missing during splitting, which IME is going to keep happening when the input files aren't standardized. And thus the recommendation is to transcode the input to lossless first, which is just completely unsustainable.

i'm still trying to figure out if av1an is the breakthrough to using large CPU counts without losing quality. but it's a ridiculously poorly documented program. i haven't gotten it to run effectively yet. https://github.com/master-of-zen/Av1an

I don't know about VVC, but I've never seen a recommendation of preset 0 for SVT-AV1. The docs say "presets 1-3 represent extremely high efficiency, for use when encode time is not important and quality/size of the resulting video file is critical". It seems like 0 is the equivalent placebo preset. But if you want AV1 with coding efficiency over all else, IIRC the typical approach is to use av1an to detect scene transitions and farm out parallel encodes with aomenc.

That might be because it doesn't work.

Have you seen Av1an? It's supposed to encode to a target VMAF.

Are you using the current version, 0.4.0, from https://github.com/master-of-zen/Av1an/releases