Skip to content

v0.1.62 — force Emby/Jellyfin transcoding

Choose a tag to compare

@NebulaSleuth NebulaSleuth released this 24 May 00:44
· 198 commits to main since this release

Fix: Emby/Jellyfin quality / audio / subtitle swaps now actually take effect

Symptom

On the web player against an Emby (or Jellyfin) source, changing quality, audio track, or subtitle track produced no visible change. Toggling subtitles on/off sometimes looked inverted because the displayed text was actually a hardsub/source artifact, not anything we were burning in.

Root cause

When the source file already matched our device profile (most common case: h264 video / aac audio in an mpeg-ts container), Emby's PlaybackInfo response selected DirectStream — i.e. serve the original bytes unmodified. Our MaxStreamingBitrate, AudioStreamIndex, and SubtitleStreamIndex params were silently ignored, because no transcoder was running.

Diagnostic give-away from v0.1.61 logging:

[hls] levels: 0:1420x1080@3649k

Every swap showed the same 3649k bitrate no matter what MaxStreamingBitrate we asked for. That's the source's bitrate, not the transcoder's.

Fix

Set EnableDirectPlay=false, EnableDirectStream=false, EnableTranscoding=true on every Emby/Jellyfin PlaybackInfo request. Forces a fresh transcoder for every session, which honors all our params — including SubtitleMethod=Encode burn-in.

Trade-off: server-side transcoding CPU on every swap, even when the source could've played natively. Acceptable for now — without it the swap controls don't work.