+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin transcodes as AV1 even though it's not allowed (/t-jellyfin-transcodes-as-av1-even-though-it-s-not-allowed)
Jellyfin transcodes as AV1 even though it's not allowed - pitfallfritz - 2024-11-14
Hi,
so I just migrated my Jellyfin server from Linux/amd64 to a Mac with an M1. I've enabled hardware acceleration in the transcoding settings. Everything works, except that incompatible videos (say, an AVI with a H263 track) will be transcoded to AV1. That's a problem because the M1 doesn't support AV1 encoding yet and software encoding is slower than 1x, even on the ridiculously low resolution of the source.
Transcoding settings enable hardware decoding for everything. Hardware encoding is enabled. Under Encoding format options, I have only selected "Allow encoding in HEVC format". Still, in Chromium, playback will start after a short delay and then constantly stutter. Playback Info reveals that it's transcoding to VP9 and OPUS, for some reason, at 0.79x.
I have checked the client's playback settings in Chromium, and manually set "Preferred transcode video codec" to HEVC, as well as "preferred transcode audio codec in video playback" to AAC. Even still, I always get VP9/OPUS.
In Firefox, it will transcode to H264 instead, which is not preferred, but at least it's fast enough.
I just tested it with the old instance on Linux/amd64, and it behaves the same, with the same settings, only it takes almost longer to even start. So it's not a problem with the Mac version or AppleVideoToolbox.
Is there any way to just disable VP9 transcoding? And is this a bug (it seems like it) or am I missing something? Ideally, it should also prefer HEVC if I want to and if the client is capable (and the client settings even prefer HEVC) – but that's another story.
RE: Jellyfin transcodes as AV1 even though it's not allowed - TheDreadPirate - 2024-11-14
Can you share your logs via pastebin? I'm not able to reproduce on my system.
Regarding Firefox, it does not support HEVC, period.
RE: Jellyfin transcodes as AV1 even though it's not allowed - gnattu - 2024-11-14
What you said does not really make sense:
- The VP9 encoder is removed from the server entirely in 10.10
- Even with software encoding, M1 can do more than 1x on at least "ridiculously low resolution of the source."
We need your server and ffmpeg log, and how you did the "migration"
RE: Jellyfin transcodes as AV1 even though it's not allowed - Fate - 2024-11-14
(5 hours ago)TheDreadPirate Wrote: Can you share your logs via pastebin? I'm not able to reproduce on my system.
Regarding Firefox, it does not support HEVC, period.
Tech technically firefox can decode hevc when:
- media.wmf.hevc.enabled is set to 1
- a h265 decoder is available in windows (like ffmpeg or h265 from microsoft store)
- on windows only
- video is not 10bit
But i think even when that is the case jellyfin-web does not allow it and forces transcoding...