rav1e VS broot

There should be some major rav1e improvements in the not-so-distant future that should benefit high fidelity encoding very nicely (https://github.com/xiph/rav1e/pull/2921). And I hope someday someone gets 10/12 bit tune butteraugli working in aomenc, should provide a massive efficiency boost in pretty much all scenarios.

There's 3 that I know of,

libaom https://aomedia.googlesource.com/aom, the reference implementation.

https://gitlab.com/AOMediaCodec/SVT-AV1 - from the Alliance for Open Media, which Intel is deeply involved with and is spending a lot of time optimising.

https://github.com/xiph/rav1e - written in rust, also subject to a lot of optimising. It's not complete coverage of all features, intended to be used for places where libaom is too slow.

AV1 currently gets used by Netflix, YouTube (right click on any big popular video "stats for nerds) and so on. It's open source and currently has 3 different encoders. AOM as it's reference encoder available here: https://aomedia.googlesource.com/ as well as SVT-AV1 as the production encoder (like x265 for H265) available here: https://gitlab.com/AOMediaCodec/SVT-AV1 and Rav1e as community project which I personally don't have a use for at all: https://github.com/xiph/rav1e

Not AFAIK. The only relevant effort I'm aware of is rav1e, and it has more assembly in it than Rust.

No. There are hardware encoders. For software encoding while AV1's reference encoder is very slow; both rav1e and SVT-AV1 are usable on a higher end PC built in the last few years.

I'm going to promote rav1e, an AV1 encoder written in Rust+ASM. Unlike the reference encoder, rav1e seeks to focus on psychovisual quality rather than pure metrics, and so to many people it is a promising alternative. However, it has some catching up to do in the speed department.

You might want to chek out broot.

Broot gives you a tree view of your directories for a better visualization

I use scripts for all my multiplatform apps. Here's an example: https://github.com/Canop/broot/blob/master/compile-all-targets.sh

cargo-cross works well for me. A big upside is that I use the same tool to build for all the targets except the native one* . This lets me have consistent scripts to build all targets, like this one.

That’s what I do most of the time as well. I’ve been meaning to learn to use Broot better for this purpose too.

I recently started using broot and love how one invokes "verbs" with the spacebar. Much easier to type " q" rather than ":q."

Here's the changelog of one of my projects: https://github.com/Canop/broot/blob/master/CHANGELOG.md