Skip to content

Add an experimental option to direct play DOVIInvalid Dolby Vision files - #2065

Open
SergeiAK wants to merge 1 commit into
damontecres:mainfrom
SergeiAK:dovi-invalid-direct-play
Open

SergeiAK wants to merge 1 commit into
damontecres:mainfrom
SergeiAK:dovi-invalid-direct-play

Conversation

@SergeiAK

@SergeiAK SergeiAK commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Description

On Jellyfin 10.11+ servers, Dolby Vision files the server tags DOVIInvalid are 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, DOVIInvalid is 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 — new direct_play_invalid_dolby_vision field in ExperimentalPreferences;
  • ExperimentalPreference.kt — the switch, added to the experimental settings list; default in AppPreferencesSerializer.kt;
  • DeviceProfileService.kt / DeviceProfileUtils.kt — the value is passed to createDeviceProfile like preferAc3ForSurround, and the two DOVIInvalid lines check it together with supportsHevcDolbyVision / supportsAV1DolbyVision. Since the experimental preferences are part of DeviceProfileConfiguration, toggling the switch rebuilds the profile.
  • two strings.

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, /PlaybackInfo on three files that differ only in the compatibility ID (6 / 1 / 0): with the device profile Wholphin sends today, compat 6 and 0 get Transcode with VideoRangeTypeNotSupported; with DOVIInvalid advertised, all three direct play (table in #2021).

On a device — NVIDIA Shield TV Pro 2019, Android 11, a debug build of this branch:

File Switch Result
Profile 8, compat 6 off Transcode, VideoRangeTypeNotSupported, SDR on screen (same as today)
Profile 8, compat 6 on Direct play, OMX.Nvidia.DOVI.decode, Dolby Vision on the TV
Profile 8, compat 0 on Direct play, OMX.Nvidia.DOVI.decode, Dolby Vision on the TV

ktlint 1.8.0 passes. testDefaultDebugUnitTest passes locally except 4 tests in ServerRepositoryTest (Unable to rename …test_datastore.pb.tmp); the same 4 fail on current main on 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):
pr-dovi-invalid-experimental-settings

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

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
SergeiAK force-pushed the dovi-invalid-direct-play branch from 970ae2b to 2ea09a7 Compare October 14, 2026 05:58
@SergeiAK

Copy link
Copy Markdown
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 main at 9f55741.

A Profile 8 file with compatibility ID 6 (DOVIInvalid on Jellyfin 10.11), toggle on: direct play, c2.amlogic.dolby-vision.dvhe.decoder, Dolby Vision on the TV. I did not re-test with the toggle off on this device; on the Shield that case transcodes (table in the PR description).

So the toggle now works the same way on Nvidia (Shield) and Amlogic decoders.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dolby Vision files tagged DOVIInvalid are always transcoded on Jellyfin 10.11+, even on devices that play them fine

1 participant