FastFlix VS rav1e

Oh, I've used QSVEnc by Rigaya for fastflix. That's good that Rigaya had done that then.

Yeah I’ll for sure check out fastflix I think they have Nvidia AV1 although you need to add this to the settings so it can be used. Though I don’t know enough about the dual Nvenc encoders unfortunately. Though it’s worth a try to use.

I've been ripping my 4K movies again (to transcode them again using FastFlix, which I heard actually supports 10-bit HDR, unlike HandBrake), and I've noticed MakeMKV failed to rip a few of my 4K discs at some point, even though I had tried to clean the bottom of the disc several times. "2001: A Space Odyssey", "Back to the Future Part 3", and "Star Trek: The Motion Picture Director's Edition" started to rip but then failed. With Back to the Future 3, I remember MakeMKV saying it was a hash check failure or something similar (it was enough to make MakeMKV stop ripping it and fail).

If you have something reproducible and know it's an issues with FastFlix would love an issue on github https://github.com/cdgriffith/FastFlix/issues !

For GUI (shameless self plug) FastFlix wraps around it to make life easier https://github.com/cdgriffith/FastFlix

Well i have to recommend FastFlix as I literally coded it lol. It wraps around ffmpeg as well as Rigaya's hardware encoders (have to download and link them in settings panel).

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).