luminance-rs VS rav1e

gives me same vibes as https://github.com/phaazon/luminance-rs

Potentially it is due to this layout optimization and a missing repr(C) somewhere in your code or a dependency. For example, here is an is a related issue in luminance.

luminance is a graphics ecosystem focusing on type-safe and type-level API. This is part of a blog article series describing the process of redesign the API to update it to how I see things today, trying to fix several flaws of the previous design, and bring more simplicity to developers.

The WebGL API might be what you are looking for if you are building a game. It supports textures, vertex buffers, and shaders. luminance-rs has a backend: https://github.com/phaazon/luminance-rs/tree/master/examples/web

There is no GUI framework used -- it is built on GLFW and Luminance. This is after using winit and wgpu for some time.

This list is really cool! I've had a lot of success with luminance - which is a mid-level graphics library (vertex buffers, shaders, etc). It has OpenGL and WebGL backends.

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