Title seems to be have been changed now:
The (successful) end of the kernel Rust experiment
Title seems to be have been changed now:
The (successful) end of the kernel Rust experiment


This stream at least looks to be h264 only, which is more likely to be hardware decodable with older hardware than the vp9/av1 that Youtube usually uses.


SVT-AV1 has also had some pretty major improvements in recent months and years. It’s possible if tested even a year ago it will be significantly faster for the same quality today.


Most of this is auto-generated header files to be clear. Still, goes to show how many GPU variants they have support for in the kernel, going back 15+ years.


I go even further and set the proportion to 100%, since ZSTD compresses so well (and the % is based on uncompressed usage).
There are theoretically some cases where zram can be harmful, but in general I find it works reliably.
Beets for cleaning up the tags and self-hosted navidrome appears to support multiple artist tags. The web interface of navidrome definitely supports filtering by both albumartist and artist (the latter will include albums and tracks with multiple artists). I assume this is what you are trying to achieve by using a visual artist tag? If you just want to rename an artist but keep the underlying artist tag, that can probably also be achieved with beets.
This link shows the details of how navidrome handles tagging: https://www.navidrome.org/docs/usage/library/tagging/ The issue if you don’t want to use the navidrome web interface is that not all clients support browsing by artist I suspect (and often use albumartist, which I personally prefer). I use supersonic which I doesn’t appear to support it, but there’s also Feishin and a bunch of mobile clients you could use (or open a feature request on supersonic github).
Replaygain will be supported by most clients (not sure about the navidrome web interface).