rpi-rgb-led-matrix VS rav1e

Hzeller - https://github.com/hzeller/rpi-rgb-led-matrix/blob/a93acf26990ad6794184ed8c9487ab2a5c39cd28/bindings/python/README.md

I installed https://github.com/hzeller/rpi-rgb-led-matrix

Anyway I used this library on a Raspberry Pi Zero https://github.com/hzeller/rpi-rgb-led-matrix I only displayed static images but the "image-example" shows how to handle animated gifs.

Adafruit makes a hat that you can plug right onto the GPIO port. I'm using rpi-rgb-led-matrix, I also have a guide you can watch on YT here https://www.youtube.com/watch?v=ssyTWpVEl0E

Use a rgb matrix hat, a raspberry pi, and this library.

To control the matrix, a loop is ran and inside things are displayed to the matrix. (I'm using this library https://github.com/hzeller/rpi-rgb-led-matrix)

I found this https://github.com/hzeller/rpi-rgb-led-matrix, this provides python scripts. Please read through them, and then ask specific questions at each step. If python just looks like gobldegock, I suggest you go through some basic python tutorials docs.python.org has a tutorial page, and no you don't have to complete the whole think just read everything about built-ins and basic syntax (for, if, def, else, etc).

If you then follow this forward to the code they originally forked theirs from from (here) and scroll down a fair way you find the entry Improving Flicker that states (in part):

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