NotEnoughAV1Encodes VS rav1e

I think notenoughav1encoders is another one but I had only just remembered that one. Might be worth a check out though

Tools like NEav1e (https://github.com/Alkl58/NotEnoughAV1Encodes/releases) will do a better job with AOMEnc encoding, maintaining a better quality and efficient CPU use. However, it may require a lot of disk space for encoding (depending on your chosen encoding configuration).

Handbrake has AV1 options in the nightly releases. There are lots of encoders that wrap FFmpeg into a GUI such as Fastflix, nmkoder, qencoder, or Not Enough AV1 Encoders.

The answer is in this log which was made by this program for anyone interrested https://github.com/Alkl58/NotEnoughAV1Encodes :

https://www.spiedigitallibrary.org/conference-proceedings-of...

It's good and getting gooder.

Just give it a try using https://github.com/Alkl58/NotEnoughAV1Encodes or whatever, svt-6 is fairly quick.

maybe you can try this https://github.com/Alkl58/NotEnoughAV1Encodes. Discovered when i read about AV1. So dont know it good or not.

Sure. You'll see it very often in codec implementations. From rav1e, a fast AV1 encoder mostly written in Rust: https://github.com/xiph/rav1e/tree/master/src/x86

Large portions of the algorithm have been translated into assembly for ARM and x86. Shaving even a couple percent off something like motion compensation search will add up to meaningful gains.

Or the current reference implementation of JPEG: https://github.com/libjpeg-turbo/libjpeg-turbo/tree/main/sim...

Again, if anything AOM would be the one restricting licenses to AV1 (if they chose to) except AOM has stated and also published AV1 in a way to allow license free access to development (which allows people to make forks of the official build like it's open source) and usage. (1)(2) I don't see why they would suddenly change this.

You can speed up the sampling process with --vmaf n_subsample=5, which in my experience works more accurately than either 2 or 4, possibly due to this bug/feature present in multiple encoders. You might also need to manually set the number of threads used for VMAF calculation with --vmaf n_threads=16, but YMMV.

That remember me of https://github.com/xiph/rav1e which is an AV1 encoder

I put in the request for ffmpeg passthrough mastering-display data a few years ago and haven't heard of any support yet.

It's getting there.. Initial steps for FFmepg: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8444 rav1e: https://github.com/xiph/rav1e/pull/3000

It's entirely possible to re-use bits of other HW encoders for the first pass (motion estimation, etc).