2024-11-15, 03:54 PM
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.
Maybe Jellyfin's implementation doesn't support this on AppleVideoToolbox, even if AppleVideoTOolbox supports hardware HEVC encoding.
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.
Maybe Jellyfin's implementation doesn't support this on AppleVideoToolbox, even if AppleVideoTOolbox supports hardware HEVC encoding.
Jellyfin 10.10.1
Apple M1/Mac mini 2020 — previously Intel Atom x5-Z8350
macOS Sequoia 15.1 — previously Debian 12
Storage: 4x4TB in RAID 5, shared via SMB
Apple M1/Mac mini 2020 — previously Intel Atom x5-Z8350
macOS Sequoia 15.1 — previously Debian 12
Storage: 4x4TB in RAID 5, shared via SMB