Skip to content

Detect HDR10+ and follow Jellyfin's Dolby Vision detection - #321

Open
zotabee wants to merge 1 commit into
jellyfin:masterfrom
zotabee:hdr10plus
Open

zotabee wants to merge 1 commit into
jellyfin:masterfrom
zotabee:hdr10plus

Conversation

@zotabee

@zotabee zotabee commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

HDR10+ files get no HDR value, because the switch has no HDR10+ case. Dolby Vision is reported whenever DvProfile is set, even when Jellyfin itself doesn't treat the file as Dolby Vision (metadata marked DOVIInvalid, or a profile Jellyfin doesn't support).

The plugin now maps Jellyfin's own VideoRangeType: every DOVI variant except DOVIInvalid to dolby_vision, HDR10Plus to hdr10_plus, then HDR10 and HLG. For DOVIInvalid it reports the base layer from the colour transfer, as Jellyfin's GetVideoColorRange() does (MediaStream.cs).

Tested on my Jellyfin 12.1 server since 2026-10-18, with test films because my library has no HDR (the master column comes from master's code):

Film Video (VideoRangeType) master This PR
Apollo 13 (1995) HDR10+ (HDR10Plus) no value hdr10_plus
Greyhound (2020) Dolby Vision 5 (DOVI) dolby_vision dolby_vision
Jaws (1975) Dolby Vision 8.1 + HDR10 (DOVIWithHDR10) dolby_vision dolby_vision
Kin (2018) HDR10 (HDR10) hdr10 hdr10
The Fix (2026) HLG (HLG) hlg hlg

trakt.tv's data export shows the values in the last column. The DOVIInvalid case hasn't run on a real file yet, and neither have Dolby Vision profile 7 or Dolby Vision with HDR10+ in one file.

Builds with no warnings on its own and merges cleanly with #320, #322, #323, #329 and #342, which change the same file.

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.

1 participant