Repository navigation
Conversation
On Jellyfin 10.11+ the server tags out-of-spec Dolby Vision streams (e.g. Profile 8 with compatibility ID 0 or 6) as DOVIInvalid, and the device profile always lists that range type as unsupported, so these files are transcoded even on devices that play them fine. The new experimental switch, off by default, stops listing DOVIInvalid as unsupported for HEVC and AV1 when the device has a Dolby Vision decoder for that codec. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SergeiAK
force-pushed
the
dovi-invalid-direct-play
branch
from
October 14, 2026 05:58
970ae2b to
2ea09a7
Compare
Contributor
Author
|
Tested after the rebase on a second device: a Homatics Box R 4K Plus (Amlogic, Android 14) with an LG OLED, built together with #2017 on top of A Profile 8 file with compatibility ID 6 ( So the toggle now works the same way on Nvidia (Shield) and Amlogic decoders. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
On Jellyfin 10.11+ servers, Dolby Vision files the server tags
DOVIInvalidare always transcoded, even on devices that play them fine. In practice these are mostly Profile 8 files with compatibility ID 6 (Blu-ray rips converted from Profile 7) or 0 (web releases), all with a PQ base layer. Details and measurements are in #2021.This PR adds an experimental switch, off by default: Direct play out-of-spec Dolby Vision. When it is on and the device has a Dolby Vision decoder for the codec,
DOVIInvalidis no longer put in the unsupported range types for HEVC and AV1, so the server can direct play these files. Nothing changes when the switch is off, when experimental settings are off, on servers older than 10.11, or on devices without a Dolby Vision decoder.The Jellyfin team left this to clients when they declined to change the tag in jellyfin/jellyfin#18097, with the warning that they cannot guarantee such files will play. That is why it is an opt-in experimental option and not a removed line.
Changes:
WholphinDataStore.proto— newdirect_play_invalid_dolby_visionfield inExperimentalPreferences;ExperimentalPreference.kt— the switch, added to the experimental settings list; default inAppPreferencesSerializer.kt;DeviceProfileService.kt/DeviceProfileUtils.kt— the value is passed tocreateDeviceProfilelikepreferAc3ForSurround, and the twoDOVIInvalidlines check it together withsupportsHevcDolbyVision/supportsAV1DolbyVision. Since the experimental preferences are part ofDeviceProfileConfiguration, toggling the switch rebuilds the profile.If you would rather have this in the HDR formats screen from #1644, it maps to one more entry there; I kept it separate so the two PRs don't depend on each other.
Related issues
Closes #2021 (option agreed in the issue discussion).
Testing
Server side, Jellyfin 12.1.0,
/PlaybackInfoon three files that differ only in the compatibility ID (6 / 1 / 0): with the device profile Wholphin sends today, compat 6 and 0 getTranscodewithVideoRangeTypeNotSupported; withDOVIInvalidadvertised, all three direct play (table in #2021).On a device — NVIDIA Shield TV Pro 2019, Android 11, a debug build of this branch:
VideoRangeTypeNotSupported, SDR on screen (same as today)OMX.Nvidia.DOVI.decode, Dolby Vision on the TVOMX.Nvidia.DOVI.decode, Dolby Vision on the TVktlint1.8.0 passes.testDefaultDebugUnitTestpasses locally except 4 tests inServerRepositoryTest(Unable to rename …test_datastore.pb.tmp); the same 4 fail on currentmainon my Windows machine, so they are not related to this change.Screenshots
The only UI change is one switch in the experimental settings (the new string is not translated yet, the rest of the screen is in Russian):

AI or LLM usage
The idea and the plan are mine: the measurements behind #2021, the upstream report, and the decision to make this an opt-in experimental switch rather than remove the line. The code was written with Claude (Claude Code): the preference, the parameter and the two conditions. I reviewed every line and can explain it. This description was written by me in Russian and translated into English with the same assistant.
🤖 Generated with Claude Code