[x86-64][CroqueMr Builds] Dolby Vision w/FEL, HDR10+, and 3D

  • CroqueMr , I assume you already saw this, but here's a picture of the player process infos and there are words that are cutted with the "..." following it because of not enough space to show it all.

    Do you think you can fix this by shortening the names or changing the column length?

    Also, I tested the DV DT file again and this time I can see the text "yous hould not see this text except on TV apps" but there's also a kodi gui interface on top with the name of the file and the 5 star to rate i think? It is better than before because before I could not see the image correctly at all. Am I suppose to see "This device can decode FEL" like with the other two test files that works?

  • Thread Title:

    Intel Battlemage / Lunar Lake (xe driver) – Black screen on HDR10 playback and modeswitch freeze on DV-R1.0.0-RC1

    System & Hardware Details

    • Platform: x86_64 Mini-PC (Intel Lunar Lake / Battlemage graphics)
    • Kernel Driver: Intel xe DRM driver (bmg_guc, bmg_huc, fbcon: xedrmfb)
    • OS / Build: LibreELEC-Generic.x86_64-13.0-DV-R1.0.0-RC1 (CroqueMr build)
    • AV Chain: PC \rightarrow Denon AVR (HDMI Enhanced / Video Bypass) \rightarrow Sony OLED TV (HDMI Enhanced)
    • GUI Resolution: 3840x2160 @ 60Hz (EGL render method, Whitelist empty)

    Issues Encountered

    1. Dolby Vision Works, but Standard HDR10 Drops to Black Screen:
      • Dolby Vision Profile 7/8 content plays without issues via the DV RGB tunneling pipeline.
      • Attempting to start standard HDR10 content immediately drops the display to a blank/black screen.
      • Audio continues to play in the background, and SSH remains fully accessible.
    2. Handshake Lockup Tied to Dynamic Refresh Rate Switching:
      • When Adjust display refresh rate is set to On start / stop, initiating HDR10 playback results in an atomic DRM modeswitch failure.
      • If Adjust display refresh rate is set to Off, HDR10 video will start, but playback suffers from persistent 3:2 pulldown judder at 60Hz.
      • Even when playback starts with refresh rate matching enabled (using a 2.0s–2.5s pause delay), stopping the video drops the screen back to black because the driver fails to cleanly renegotiate from 24Hz HDR10 back to 60Hz SDR desktop.
    3. GBM / Atomic DRM Initialization Failures:
      • When switching display states, Kodi reports windowing failures:bool KODI::WINDOWING::GBM::CDRMUtils::OpenDrm(bool): No drm devices found
      • CWinSystemGbm::InitWindowSystem - failed to initialize Atomic DRM
      • critical <general>: CApplication::CreateGUI - unable to init windowing system

      • The kernel log indicates forced connector bindings:[drm] forcing HDMI-A-3 connector on

      • This setup appears to block dynamic atomic color-depth renegotiation (switching between 8-bit RGB and 10-bit YCbCr).
    4. Incompatibility with Generic Kernel Builds:
      • Attempting to update to standard mainline/generic builds (such as generic YBLOD 0.3.0) leads to total display loss on boot (/sys/class/drm does not register any card nodes) due to missing xe driver modules/patches for this generation of Intel silicon.
      • The system currently relies on the custom kernel patches present in DV-R1.0.0-RC1 just to expose the display output.

    Troubleshooting Steps Already Attempted

    • Confirmed Sony TV HDMI input is set to standard Enhanced format (not the Dolby Vision override mode).
    • Confirmed Denon AVR 4K/8K signal format is set to Enhanced with Video Mode: Bypass.
    • Cleaned out <resolutions> and <whitelist> blocks from guisettings.xml.
    • Tested with Render method set to 0 (EGL) and Pause after refresh change set to 2.5s.
    • Verified that stopping Kodi (systemctl restart kodi) immediately recovers the GUI over SSH.

    Questions / Request for Help

    1. Is there a stable kernel parameter or patch for the xe driver to allow atomic color-depth switching to 10-bit HDR without crashing the connector?
    2. Has anyone found a working combination of DRM plane settings or EDID overrides on Battlemage/Lunar Lake that prevents the display from dropping sync when exiting 24p HDR playback back to 60Hz SDR?
  • It was fun promoting this project and trying to get more people to come on this thread. I started looking at people who were asking about best Dolby Vision hardware, and then post directly to them in a post (reddit), sent out like 20 copy past messages, reddit flagged me and banned my account, along with all my posts. dammit, kind of sad now. had plans to create new posts when CroqueMr updated with fixes. damn they just get you of the platform so easily

  • damn they just get you of the platform so easily

    I guess the moderators there are kind of jaded. Imagine the volume of people trying to promote things for profit every single day unfortunately, legitimate open-source projects end up getting caught in the crossfire.

    Anyway, maybe it's for the best. Slow influx of people is usually better anyway. The people who genuinely care about the project will find it eventually

  • DMDreview Your investigation of 12-bit handling is excellent. Could you explain in more detail what you did? What does the test video consist of (ie what is in the BL and what in the EL). Presumably, both layers are 10-bit 4:2:0 YUV. Can you make those videos public, perhaps?

    You say DaVinci can't generate the necessary test file. Can you expand on that? It's what professionals use to make DV films with 12-bit precision so what can't it do?

    I suppose you are capturing the HDMI as IPT and feeding that into your custom software. Then for the colour gradient test converting that back to RGB for display?

    The files were created by djnice77. EL was designed specifically to add additional bits to the original 10-bit signal.
    Everything is freely available at https://github.com/djnice/fel12bit/releases/tag/set2
    DaVinci can create and open 12-bit video, but I haven’t found any tools there that can display 12-bit data in graphs and code—only 10-bit data is available. Plus, there are no other tools for convenient comparison and analysis.
    As for capturing the source, I capture the input via HDMI RGB 8-bit and save it after repackaging it into the original 422 12-bit IPT format. I also decode the DM from the RG(B) channel, which contains RPU information, to verify whether the RPU is being transmitted correctly to the TV.

    As for comparing different LE versions: We’ll see—I have a lot of testing plans, but not enough time for everything, especially since I have my day job. For now, I’m interested in comparing the accuracy of DM transmission to the TV and the gradation near black in 12-bit.

  • The files were created by djnice77.

    Wait, so the pattern was created using some random RPU, with the x265.exe encoding BL/EL done separately? That seems odd when he could have simply created the pattern in Resolve, delivered it as 12-bit ProRes or JPEG 2000, and then used Dolby's own tools (the Dolby Encoding Engine) to generate a proper Profile 7 BL, EL, and RPU.

  • The files were created by djnice77. EL was designed specifically to add additional bits to the original 10-bit signal.
    Everything is freely available at https://github.com/djnice/fel12bit/releases/tag/set2
    DaVinci can create and open 12-bit video, but I haven’t found any tools there that can display 12-bit data in graphs and code—only 10-bit data is available. Plus, there are no other tools for convenient comparison and analysis.
    As for capturing the source, I capture the input via HDMI RGB 8-bit and save it after repackaging it into the original 422 12-bit IPT format. I also decode the DM from the RG(B) channel, which contains RPU information, to verify whether the RPU is being transmitted correctly to the TV.

    As for comparing different LE versions: We’ll see—I have a lot of testing plans, but not enough time for everything, especially since I have my day job. For now, I’m interested in comparing the accuracy of DM transmission to the TV and the gradation near black in 12-bit.

    Your tool is amazing, it impresses me more than the DV release we did.

  • CroqueMr, had started doing my full suite of test clips for YT video, but stopped as I've found two issues already (using AMD 5800H):

    Debug log here.

  • One thing I forgot to mention is that the Player Information overlay does not show source material vs output material. If one opts to convert HDR10 to Dolby Vision, the overlay shows the source as Dolby Vision. I think somewhere there should be info about the actual source.

    Is this happening only to me?

  • Same. Pressing 'O' a second time brings up ability to toggle to different mode, but when playing HDR10, option to display as DV showed unsupported for me. Could be I'm doing something wrong.

  • Same. Pressing 'O' a second time brings up ability to toggle to different mode, but when playing HDR10, option to display as DV showed unsupported for me. Could be I'm doing something wrong.

    On NUC 11 i3 I'm getting a different scenario.

    HDR10 gets converted to Dolby Vision. Subtitles are not shown, menu is not shown, pressing O does not bring up the Player Information overlay. Instead all of that is transferred to a very small thumbnail on the bottom left, that shows a miniature of the menu or the subtitles or the Player Information overlay. If I pause the video, menu/subs/overlay are shown. As soon as I unpause it, they go back in the small thumbnail on the bottom left. I posted a picture of this some posts ago.

    HDR10+ is played as HDR10 but, for me at least, it leads to frequent screen blankings, as if the TV was losing the signal and then catching it once more. Several times a minute. I sent a debug log about this, hopefully it'll help.

  • i want to share my experience with amd 3400g cpu (picasso, radeon vega 11) with CroqueMr build....dv fel works as it should be. tried mkv files.

    not tested with other formats (e.g. hdr10+ etc etc etc)

    the device is asrock deskmini a300 (chipset amd a300), with 16gb ram at 2666mhz speed

  • CroqueMr, had started doing my full suite of test clips for YT video, but stopped as I've found two issues already (using AMD 5800H):

    Debug log here.

    Thanks for the log, yes HDR10+ is not perfect yet, but DV normaly is perfect, I will check your P7 issue I think it's not linked to DV

    I have a release about to go out that includes fixes, I will try to add fixes based on your logs.

    Here’s what’s currently in development and coming soon and knonw limitation:
    - Bug fixes for a wide range of hardware (AMD RX9000 / GTX1000)
    - HDR10+ fixes
    - Support for Blu-ray ISO menus, regardless of the menu type

  • One thing I forgot to mention is that the Player Information overlay does not show source material vs output material. If one opts to convert HDR10 to Dolby Vision, the overlay shows the source as Dolby Vision. I think somewhere there should be info about the actual source.

    Is this happening only to me?

    I can add a video input/video output for a better understanding when a conversion is ongoing.

    On NUC 11 i3 I'm getting a different scenario.

    HDR10 gets converted to Dolby Vision. Subtitles are not shown, menu is not shown, pressing O does not bring up the Player Information overlay. Instead all of that is transferred to a very small thumbnail on the bottom left, that shows a miniature of the menu or the subtitles or the Player Information overlay. If I pause the video, menu/subs/overlay are shown. As soon as I unpause it, they go back in the small thumbnail on the bottom left. I posted a picture of this some posts ago.

    HDR10+ is played as HDR10 but, for me at least, it leads to frequent screen blankings, as if the TV was losing the signal and then catching it once more. Several times a minute. I sent a debug log about this, hopefully it'll help.

    I will try to reproduce thanks for the description.

  • Hello! Got a small issue with RC1 and 1.1 while Beta5 worked well

    Setup is my pc(rtx 4070) - denon x1700h - sony a80l.

    When playing an HDR10 movie, pressing O shows the right format(hdr10) but sony doesnt seem to get the hdr signal which is weird because dolby vision works fine

  • CroqueMr, had started doing my full suite of test clips for YT video, but stopped as I've found two issues already (using AMD 5800H):

    Debug log here.

    CroqueMr I cannot play any of the first 5 Transformers movies. It just returns to the GUI without playing anything.

    I get this:
    error <general>: Dolby Vision playback unavailable: stream=325 source_revision=325 profile=7 reason=4

    I attach the log.

    The more recent Transformers movies and Bumblebee works fine.

    Pretty sure all Transformers movies are FEL.

    P.S. I tried countless other DV movies and everything plays fine, I don't know what these files have that the others do not. They play ok on the am6b+.

  • Hello all. I recently discovered and installed this amazing release on my PC (9800x3d and RTX 4090 connected to an Onkyo TX-RZ70 and LG OLED C8). All is going well but I noticed that all hdr playback (both HDR10 and Dolby Vision) the output of the signal is RGB 8-bit, both Kodi and my receiver report this. Shouldn't it change to at least RGB 10-bit? When playing HDR content on windows with Madvr the output is RGB 10-bit. Is this a known limitation?


    Sorry of this has been asked before but I used the search function and couldn't find any mention of this.