[x86-64][LibreELEC x CB1 Builds] Dolby Vision FEL, HDR10+ and Full 3D

  • Thanks a lot :)

  • Thanks CroqueMr for the release. It's fantastic.
    My setup is TV LG G6, Denon AVR, ASUS NUC Ultra 7 225H.
    I have one issue with the NUC connected trought the Denon HDMI. When i start the NUC, i see the BIOS screen and then the video output don't switch to the TV. I can't see the setup screen. I need to switch off and on several time the Denon to view the setup screen. The same with LiibreELEC installed on the system. I see the home screen only if I turn off and on the Denon many times.
    But, if i connect the NUC directly to the TV, it's all fine.
    My Denon is the avr 110 anniversary edition.

    I have try with a Windows 11 USB Stick, and works.
    It's a generic problem of LibreElec?

    Thanks

    I had the same issue with a Denon receiver and a B2 OLED. Try disabling 'Deep Color' on the HDMI input on the TV. That disables HDMI 2.1 features.

  • hadesdevls  CroqueMr Found it in CB1 (under Settings > Player > Videos > CB1 - Dolby Vision engine > Master Reference output), and my CB1 build (DV-R1.0.1-RC2/RC3) is actually set to "YCbCr" (not IPT-PQc2)—yet CB1 still looks noticeably brighter and punchier on my Sony A80K OLED than Hades 1.1.

    In Hades 1.1, I tested both transport modes on the exact same 4K Dolby Vision scene on my Sony A80K (Dolby Vision Bright):
    - Transport = "As composed" (YCbCr): Noticeably dimmer and flatter than CB1.
    - Transport = "As licensed players send (IPT)": Still the exact same dimmer/flatter brightness as YCbCr—switching to IPT did not bring it up to CB1.

    Here is my CB1 log from the test:
    https://paste.libreelec.tv/nonpharmaceutic-ettie.log

    I've also attached my Hades diagnostic report (hades-report-2026-11-21-09.30.21.zip) from the test.hades-report-2026-11-21-09.30.21.zip


    hadesdevls  CroqueMr Found it in CB1 (under Settings > Player > Videos > CB1 - Dolby Vision engine > Master Reference output), and my CB1 build (DV-R1.0.1-RC2/RC3) is actually set to "YCbCr" (not IPT-PQc2)—yet CB1 still looks noticeably brighter and punchier on my Sony A80K OLED than Hades 1.1.

    In Hades 1.1, I tested both transport modes on the exact same 4K Dolby Vision scene on my Sony A80K (Dolby Vision Bright):
    - Transport = "As composed" (YCbCr): Noticeably dimmer and flatter than CB1.
    - Transport = "As licensed players send (IPT)": Still the exact same dimmer/flatter brightness as YCbCr—switching to IPT did not bring it up to CB1.

    Here is my CB1 log from the test:
    https://paste.libreelec.tv/nonpharmaceutic-ettie.log

    I've also attached my Hades diagnostic report (hades-report-2026-11-21-09.30.21.zip) from the test.hades-report-2026-11-21-09.30.21.zip

    hadesdevls  CroqueMr Comparing both logs on my Intel Arc B570 + Sony A80K OLED (Dolby Vision Bright) shows three concrete differences in how CB1 (DV-R1.0.1-RC3) and Hades 1.1 drive the Dolby Vision output:

    1. Target Peak Luminance:
    - CB1 honors my Sony A80K's exact Dolby Vision EDID block ("CB1 LLDV: ... peak=896.539 black=0.000000").
    - Hades overrides CMv4.0 to 1000 nits ("content mapping v4.0 is decided against a peak of 1000 cd/m2 set by hand (videoscreen.hadesdvcm40peak), not the 897 cd/m2 that the Dolby block of the TV declares"), compressing mid-tones and highlights downward.

    2. Connector Colorspace & Link Signaling:
    - CB1 sets the DRM connector colorspace to BT2020_RGB ("setting connector colorspace to BT2020_RGB (source BT2020_YCC, RGB output)") with forced_422_10=true and clock_khz=296703.
    - Hades leaves Colorspace at Default (0) ("Colorspace Default (0) -> Default (0)"), sets Broadcast RGB to Full (1), and caps max_bpc at 8 ("max bpc 8 -> 8").

    3. Tone Mapping / PQ LUT:
    - Even in "Master Reference" mode (with YCbCr), CB1 loads its internal 256-entry PQ LUT ("CGuiCompositeShaderGLES::CreateLUTs - created PQ LUT (256 entries)") and maps directly to the TV's 896.539-nit peak, resulting in noticeably brighter and punchier highlights than Hades in either YCbCr or IPT-PQ-c2 transport.


    hadesdevls  CroqueMr Here is my CB1 overlay during playback of a Dolby Vision Profile 8.1 (CMv4.0) stream while set to "Dolby Vision : Master Reference" (no Adaptive HDR boost active):

    - Input: 3840x2160p @ 24.000 fps, 10-bit BT.2020 PQ Limited, Profile 8.1 (CMv4.0, HDR10 BL + RPU, Mastering 1000/0.0001 nits, MaxCLL 1341 / MaxFALL 183 nits)
    - Processing: Dolby Vision : Master Reference (forwarding L1 / L2 / L8 / L9 metadata directly to TV)
    - Output: Dolby Vision TV-Led, 8-bit RGB 4:4:4 @ 24.000 Hz

    This confirms CB1 outputs a noticeably brighter, punchier image than Hades 1.1 across both Profile 7 (CMv2.9) and Profile 8.1 (CMv4.0) content even in pure Master Reference mode over the same 8-bit RGB TV-Led tunnel.

  • I had the same issue with a Denon receiver and a B2 OLED. Try disabling 'Deep Color' on the HDMI input on the TV. That disables HDMI 2.1 features.

    Thanks

    If i setup the GUI of Kodi in 30Hz, the problem is solved. This is my workaround.
    For setup and upgrade the release, i will connect the NUC directly to the HDMI TV.

  • Same HDMI negotiation issues here, in my case I've my HTPC connected to a Sony HT-A9. The same chain but with my Vero V doesn't have this problem, and it's also Linux based.

    In my case is not only fails sometimes when switching from BIOS prompt to LibreELEC is also happening when playing HDR10 movies, (not happening with Dolby Vision ones), my guess is some kind of bad negotiation when switching resolutions and bit depth modes, DV is tunneled through a RGB444 8bit, HDR10 sends 10bits, also in 444 (I think), which should be no problem for a 23.976 or 24 hz in terms of bandwidth, but something happens in the middle, I don't know. As others also commented, turn off and turn on, the deco make the image appear again, it's like at this moment the negotiation is correct.

    I didn't have the time to put any logs or open an issue, sorry, I will try during this weekend it that helps.

  • I've been also testing Hades 1.1 release and it has the same problem, I strongly thinks that the problems comes for the little margin the HDMI 18 gbps bandwidth has on those scenarios, Sony HT-A9 has a full 2.1 HDMI (FLR?), but the HTPC and, specially, the Hisense Projector (at the end of the chain) are both TMDS, in practice, the moment anything in the chain try to pass from 3840x2160/60hz/8bit (from the Kodi UI) to anything with a higher depth, the negotiation fails, maybe it tries first the depth change and then the frequency one, so the moment it changes to 10bit it doesn't matter how low the frequency is, even with the needed bandwidth the negotiation says no :D

    The way I solve the problem, not ideally, is by setting Kodi UI to 1920x1080/60Hz and forcing "compatiblity" mode for the HDMI port in the projector, which actually limits the signal to a maximum ok 4K/30Hz, not a problem in my case, since I don't have movie above that. And the only one that comes to my mind "Gemini Man" is not in my collection.

    But as I said, something different it has been done in OSMC since I never have that kind of problems with Vero V.

    A little offtopic CroqueMr now that I've tested latest Hades 1.1 release, I've found a couple of surprises for my particular needs:

    • Nvidia Shield TV Remote bluetooth connection problems are solved.
    • Is incredible useful to have Restart to LibreELEC and Restart to Windows in the LibreELEC shuthdown menu, for those, like me that make dualboot.

    Thanks as always for your work.

  • I've been also testing Hades 1.1 release and it has the same problem, I strongly thinks that the problems comes for the little margin the HDMI 18 gbps bandwidth has on those scenarios, Sony HT-A9 has a full 2.1 HDMI (FLR?), but the HTPC and, specially, the Hisense Projector (at the end of the chain) are both TMDS, in practice, the moment anything in the chain try to pass from 3840x2160/60hz/8bit (from the Kodi UI) to anything with a higher depth, the negotiation fails, maybe it tries first the depth change and then the frequency one, so the moment it changes to 10bit it doesn't matter how low the frequency is, even with the needed bandwidth the negotiation says no :D

    The way I solve the problem, not ideally, is by setting Kodi UI to 1920x1080/60Hz and forcing "compatiblity" mode for the HDMI port in the projector, which actually limits the signal to a maximum ok 4K/30Hz, not a problem in my case, since I don't have movie above that. And the only one that comes to my mind "Gemini Man" is not in my collection.

    But as I said, something different it has been done in OSMC since I never have that kind of problems with Vero V.

    A little offtopic CroqueMr now that I've tested latest Hades 1.1 release, I've found a couple of surprises for my particular needs:

    • Nvidia Shield TV Remote bluetooth connection problems are solved.
    • Is incredible useful to have Restart to LibreELEC and Restart to Windows in the LibreELEC shuthdown menu, for those, like me that make dualboot.

    Thanks as always for your work.

    The fix for remote came from Linux update I think, my ongoing 1.1 build linked to upstream repo should fix that ;)
    I do not planned to add a dual boot feature, maybe in the future if the need is important, I prefer to focus on other features

    for 60hz connexion, IMO you likely have an issue with the 12 bit setting. With a HDMI 2.0 connexion, a 60Hz signal is generally transmitted via a 4:2:2 12 bit stream, into which 10-bit content is embedded, that might be where the problem lies.

  • Just run your daily tests and report anything if you have issues. ;)

    1.1 build is incoming it will focus on some upstream update, LLDV better support, improvement of BD-J menu navigation

  • CroqueMr it seems you haven’t seen my post 🙄

    It’s a bit complicated to understand your issue since it is not my build, I’ll let Hades debug his own build. I pointed him toward an important PR I recently added, which fixes a rendering error in my engine. Since Hades’ engine is derived from mine, it’s possible he has that same error, though I don’t think that’s what you’re encountering.

    Check if you don't have a build with different settings let every parameter "vanilla" :

    - Do not disable L2
    - Do not add CM4 metadata (let the paramter to off)

  • It’s a bit complicated to understand your issue since it is not my build, I’ll let Hades debug his own build. I pointed him toward an important PR I recently added, which fixes a rendering error in my engine. Since Hades’ engine is derived from mine, it’s possible he has that same error, though I don’t think that’s what you’re encountering.

    Check if you don't have a build with different settings let every parameter "vanilla" :

    - Do not disable L2
    - Do not add CM4 metadata (let the paramter to off)

    Thanks for clarifying, CroqueMr! That actually makes complete sense—on CB1, my settings are vanilla ("Master Reference", L2 forwarded directly to the TV, no CMv4 injection), and everything looks bright and accurate on my Sony A80K.

    In Hades 1.1, my log showed it applying CMv4.0 content mapping against a 1000-nit peak even on a CMv2.9 Profile 7 stream. I'll check the vanilla L2 / CM4 parameters in Hades and follow up with hadesdevls in his thread. Appreciate the help!

  • Thanks for clarifying, CroqueMr! That actually makes complete sense—on CB1, my settings are vanilla ("Master Reference", L2 forwarded directly to the TV, no CMv4 injection), and everything looks bright and accurate on my Sony A80K.

    In Hades 1.1, my log showed it applying CMv4.0 content mapping against a 1000-nit peak even on a CMv2.9 Profile 7 stream. I'll check the vanilla L2 / CM4 parameters in Hades and follow up with hadesdevls in his thread. Appreciate the help!

    I think there’s a misunderstanding.

    The peak brightness values read from the EDID are only used for Dolby Vision LLDV. In the "classic dolby vision mode" (TV-led) which is used for all my other modes, it is your TV that performs the tone mapping based on its own peak brightness of approximately 900 nits not my engine. I am pretty sure Hades do the same, if it is not the case it's a major issue.