MediaElch icon indicating copy to clipboard operation
MediaElch copied to clipboard

Dolby Vision not displayed

Open nkatsidis opened this issue 10 months ago • 7 comments

Latest Medialech Nightly Windows 10.

When a movie is Dolby Vision only HDR 10 displayed (in stream details).

can you please fix it so Dolby Vision is displayed.

nkatsidis avatar May 07 '25 17:05 nkatsidis

if its dolby vision just add in streamdetails

<hdrtype>dolbyvision</hdrtype>

thank you :)

nkatsidis avatar May 07 '25 20:05 nkatsidis

Hi,

thanks for reporting this issue. Please note that, due to limited time, I can't say when or if I get to work on this. See https://github.com/Komet/MediaElch/issues/1710 for details.

Regards, Andre

bugwelle avatar May 29 '25 10:05 bugwelle

I think this might be because the app is inspecting the value of HDR_Format_Compatibility, which for Dolby Vision is usually HDR10 (the fallback for devices that don't support DV). https://github.com/bugwelle/MediaElch/blob/master/src/media/MediaInfoFile.cpp#L125

Looking at the output from mediainfo locally, the correct value (confusingly) seems to come from HDR_Format_Commercial for HDR10 and HDR10+ (which aren't distinct in Kodi's NFO format anyway) and HDR_Format for DV. I'll need to do some more testing over my media library to see how reliable this is. For the one HLG file I have handy, the HDR_* fields don't seem to be returned at all, but transfer_characteristics has HLG / BT.2020 (10-bit).

That said, I don't see the field populated at all in the latest build - I can select a value manually and it will be saved in the .NFO, but it's left blank after hitting Load stream details.

Quppa avatar Jun 19 '25 06:06 Quppa

Thanks @Quppa

The mediainfo fields are always a bit confusing. 😄

How did you install MediaElch? What version of mediainfo do you use? :)

bugwelle avatar Jun 26 '25 18:06 bugwelle

The mediainfo fields are always a bit confusing. 😄

I went through my media library and checked the values for the various HDR fields. I think the logic should be something like:

if video["HDR_Format"].lower().contains("dolby vision") {
  return "dolbyvision";
} else if video["HDR_Format"].lower().contains("smpte st") {
  return "hdr10";
} else if video["transfer_characteristics"].lower().contains("hlg") {
  return "hlg";
}

In practice, the values I see are:

Type Mediainfo HDR_Format
Dolby Vision (no HDR10 fallback) Dolby Vision
Dolby Vision + HDR10 fallback Dolby Vision / SMPTE ST 2086 or Dolby Vision / SMPTE ST 2086 / SMPTE ST 2086
Dolby Vision + HDR10+ + HDR10 Dolby Vision / SMPTE ST 2086 / SMPTE ST 2094 App 4
Dolby Vision + HDR10+ Dolby Vision / SMPTE ST 2094 App 4
HDR10 SMPTE ST 2086
HDR10+ SMPTE ST 2094 App 4
HDR10 + HDR10+ SMPTE ST 2086 / SMPTE ST 2094 App 4

How did you install MediaElch? What version of mediainfo do you use? :)

I've tested with the latest AppImage (MediaElch_linux_2.12.1-dev_2025-06-27_03-14_git-master-365a666.AppImage). Mediainfo is version 25.04 (the Fedora package). I can see the HDR info for files if I call Mediainfo outside MediaElch.

Quppa avatar Jun 27 '25 11:06 Quppa

Thanks for all the work, @Quppa !

I've prepared a PR at https://github.com/Komet/MediaElch/pull/1899

I didn't look into MediaInfoLib again, yet. I was confused about Dolby Vision vs HDR10, only to discover that I switched them up. I thought HDR10 was "better"/"newer" than HDR10, but it's the opposite. Only HDR10+ is more recent.

bugwelle avatar Jul 07 '25 17:07 bugwelle

HDR formats are a confusing mess in naming and compatibility. The Kodi NFO enum doesn't really capture the complexity - it should at least have an option for HDR10+, and arguably there should be different values for the various Dolby Vision profiles. Given its constraints I think MediaElch is behaving correctly.

I'll try to debug the MediaInfo issue later to figure out why I don't see any values.

Quppa avatar Jul 07 '25 23:07 Quppa