SOLVED: Jellyfin transcodes as AV1 even though it's not allowed

[gnattu]

I started it again and get this log output:
https://pastebin.com/bxvVF8vY

The Chromium is Version 130.0.6716.0 (Developer Build) (arm64) on macOS.
This doesn't happen in other browsers, so I guess I can live with Chromium being funky. Still very odd since VPN9 support is supposedly gone from Jellyfin, as you say.

I still wonder why it's not transcoding to HEVC when I play such a video on capable browsers such as Chrome (not Chromium), Edge or Safari. Is there a way to definitively prefer H265? Other than changing the client's playback settings to HEVC, which is ignored.

It should transcode to HEVC with a compatible browser. Are you really sure it is transcoding to h264 even using safari on your Mac?

BTW, it looks like your build of chromium is not built with hevc and h264 support. I recommend this build on macOS if you hate google and still want decent chromium experience: https://formulae.brew.sh/cask/eloston-chromium

This one does support hardware accelerated HEVC.

Maybe Jellyfin's implementation doesn't support this on AppleVideoToolbox, even if AppleVideoTOolbox supports hardware HEVC encoding.

Please don’t say something like this because I am the exact person who implemented this in Jellyfin.