ffmpeg-quality-metrics VS ab-av1

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.

Calculate vmaf before you encode the whole file. -> https://github.com/alexheretic/ab-av1 has a search mode with samples, the estimation of time and filesize is very good and does everything in one step

ab-av1 auto-encode with a VMAF quality target of 97-98 + a script for the deletion of files sounds like what you need.

ab-av1

My case is ab-av1, a cli for encoding videos. The local db stores cached vmaf analysis.

If the goal is space saving and a consistent visual quality rather than just having a library as AV1 for its own sake, I'd use ab-av1. Not sure how (or if) it'll handle the Opus audio channels cases, but bugs can be filed.

Try this https://github.com/alexheretic/ab-av1

Use this tool and you will get excellent results https://github.com/alexheretic/ab-av1 calculates and converts automatically calculates the vmaf and crf properly

Check this, might help you optimize the process.