mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-03-01 03:16:51 +03:00
Videos with DV and HDR10+ are still reported as DOVIWithHDR10 #7724
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RyuzakiKK on GitHub (Nov 9, 2025).
Description of the bug
MKV files that have both Dolby Vision 8.1 (non EL) and HDR10+, are still reported as
DOVIWithHDR10instead of the expectedDOVIWithHDR10Plus.Having a reliable information about the availability of HDR10+ is vital to the correct playback on the Fire Stick 4K, because that device can't reproduce files when both DV and HDR10+ are present.
Reproduction steps
What is the current bug behavior?
In the Media Info we get
Video range type DOVIWithHDR10What is the expected correct behavior?
That file should be reported as
DOVIWithHDR10Plus.Jellyfin Server version
10.11.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.11.2
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
The mediainfo of the mkv file is:
And Jellyfin checks for HDR10+ by looking at the type
HDR Dynamic Metadata SMPTE2094-40 (HDR10+)0598c6eaf6/MediaBrowser.MediaEncoding/Probing/ProbeResultNormalizer.cs (L945-L950)Which seems to be present in the sample mkv though:
@nyanmisaka commented on GitHub (Nov 9, 2025):
@RyuzakiKK commented on GitHub (Nov 9, 2025):
Actually, this seems to be an issue with stale metadata that doesn't get refreshed with the "Scan all libraries" button.
Sorry about the noise. It seems I need to flush the cache and force a metadata refresh of all files.
@RyuzakiKK commented on GitHub (Nov 9, 2025):
For future reference, to fix this I had to: