ConverterNOW VS rav1e

Converter NOW: Unit Converter (version 4.2.0): A simple, immediate and fast unit converter!

Or build it from source code!

Progressive web app (link)

I wrote and mantain Converter NOW (https://github.com/ferraridamiano/ConverterNOW). It is a multiplatform (Android, Linux, Windows and Web) unit and currency converter. It is built to be easy to use, it doesn't require any special permission (just internet to update the exchange rates) and it doesn't contain any form of tracking. The android version is available to both play store and f-droid.

Few days ago I released the first stable relase of units_converter. It is a unit converter package written in dart that has 100% test coverage (this is very important with this kind of libraries, it does one thing and it has to do it well). It also has a permissive license. This package is used in Converter NOW, a multiplatform (android, web, windows, linux) unit converter app written in Flutter.

Converter NOW: Unit & Currency Converter (version 3.0.1): A simple, immediate and fast converter! ⚡

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