GodotSteam VS rav1e

Here I'm already trying to use dll and template from windows prebuild win64-g353-s158-gs3221.zip from https://github.com/CoaguCo-Industries/GodotSteam/releases, same results

get libgodotsteam.so + libsteam_api.so from here: https://github.com/CoaguCo-Industries/GodotSteam/releases/tag/g352-s157-gdn363

That at least gives me hope that the ecosystem will adapt quickly. And I noticed GodotSteam for instance delivered a 4.0 compatible release today already: https://github.com/Gramps/GodotSteam/releases

Wild to me this is being released on the iphone before being mac compatible on steam considering it already runs flawlessly on mac when you import the files from a windows pc and paste two files into the install folder and run it. I just did this and it's perfect, it would literally take him minutes of his time to make this available to OSX users.

You need this Godot build first, it is practically Godot for building games with Steam.

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