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

  • Normaly last settings is saved and will be applied to your next playback.

    Yes, but I don't think I am explaining myself properly. There currently are four HDR standards: HDR10, HDR10+, Dolby Vision, HLG.
    In CoreELEC builds, for each format you decide how to handle it. And all videos follow those rules, without any need for further manual intervention by the user. It's nice to have the option to switch on the fly (through the O shortcut) but that should not be substituting proper settings for everyday use.

    I hope now my explanation is clearer. Thanks for listening and for your patience with the multitude of users...

  • Yes, but I don't think I am explaining myself properly. There currently are four HDR standards: HDR10, HDR10+, Dolby Vision, HLG.
    In CoreELEC builds, for each format you decide how to handle it. And all videos follow those rules, without any need for further manual intervention by the user. It's nice to have the option to switch on the fly (through the O shortcut) but that should not be substituting proper settings for everyday use.

    I hope now my explanation is clearer. Thanks for listening and for your patience with the multitude of users...

    I agree with this, there should be 4 separate conversion options configure once in the player settings. FOr me I would do this:

    HDR10 -> HDR10
    HDR10+ -> DV
    HLG -> HLG
    DV -> DV

    So only my HDR10+ without DV files gets HDR10+ to DV conversion while being played back and all the other 3 will be played directly native.

  • Hello,

    Has anyone tested The Last Jedi 4k Blu-ray? I tested it today from a full BDMV rip and in the player information I get FEL reconstructed = No FEL and I believe this Blu-ray has it.

    Anyone getting the same result? Is this normal?

  • FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.

    The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview

    Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.

    Changes since R1.0.0-RC2

    Dolby Vision

    • Added GPU bilinear FEL upscaling, replacing the nearest-neighbor fallback when VAAPI scaling is unavailable.
    • Added the Reference GPU FEL filter as a selectable option for other conversion modes. Master Reference retains its reference filter.

    Playback and stability

    • Fixed cases where stopping playback during a resolution change could leave HDR signaling active instead of returning to SDR.
    • Fixed stale HDR10 session reuse after a rejected output activation, ensuring subsequent playback prepares the required output surface.

    Settings

    • Separate remembered rendering preferences for Dolby Vision, HDR10 and HDR10+ inputs.
    • Automatic fallback no longer replaces the preferred rendering mode.
    • Fixed rendering options incorrectly remaining unavailable after stopping a different source format.

    HDR10+

    • Fixed source-specific preference selection during continued HDR10+ playback, preventing accidental use of the plain-HDR10 preference.

    Player information

    • Corrected misleading "Unused blocks" reporting: metadata forwarded to the TV is no longer marked unused.
    • Displays whether CM2.9-to-CM4 conversion is actually active, including live updates for Auto and Auto 2.

    Blu-ray menus

    • Updated BD-J Java add-on packaging with matching libbluray 1.5.0 support files.
    • Prevented stale or incomplete Java support files from being packaged. Requires the updated JRE add-on attached to this release.
  • FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.

    The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview

    Great work, CroqueMr! 👏

    Thank you for releasing RC3 Preview and for all the effort you're putting into this project. It's great to see the continued improvements, especially with Dolby Vision FEL and Blu-ray menu support.

    I'm looking forward to testing this release on my Intel Arc NUC and will share my feedback after trying it with different movies and Blu-ray ISOs.

    I also found the updated JRE add-on in the release assets.

    Thanks again for your dedication and hard work. Really appreciate it! 👍

  • Thanks for the update, sadly the HDR10+ to DV playback now just gets stuck at pending for me and never starts or fails.

  • FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.

    The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview

    Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.

    Changes since R1.0.0-RC2

    Dolby Vision

    • Added GPU bilinear FEL upscaling, replacing the nearest-neighbor fallback when VAAPI scaling is unavailable.
    • Added the Reference GPU FEL filter as a selectable option for other conversion modes. Master Reference retains its reference filter.

    Playback and stability

    • Fixed cases where stopping playback during a resolution change could leave HDR signaling active instead of returning to SDR.
    • Fixed stale HDR10 session reuse after a rejected output activation, ensuring subsequent playback prepares the required output surface.

    Settings

    • Separate remembered rendering preferences for Dolby Vision, HDR10 and HDR10+ inputs.
    • Automatic fallback no longer replaces the preferred rendering mode.
    • Fixed rendering options incorrectly remaining unavailable after stopping a different source format.

    HDR10+

    • Fixed source-specific preference selection during continued HDR10+ playback, preventing accidental use of the plain-HDR10 preference.

    Player information

    • Corrected misleading "Unused blocks" reporting: metadata forwarded to the TV is no longer marked unused.
    • Displays whether CM2.9-to-CM4 conversion is actually active, including live updates for Auto and Auto 2.

    Blu-ray menus

    • Updated BD-J Java add-on packaging with matching libbluray 1.5.0 support files.
    • Prevented stale or incomplete Java support files from being packaged. Requires the updated JRE add-on attached to this release.

    Bro ABSOLUTELY WOW you are obsessed on building all the best ever features into this HATS OFF 🔥 as I said once I am back will test it on my PC & will confirm

  • Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.

    I report from my NUC11TNKI3 (i3-1115G4) installation.

    HDR10+ conversion setting works and it's saved. HDR10+ conversion itself does not even start playback. Tried with multiple files.

    Dolby Vision seems to work fine, I have activated the CM 4.0 "Always" setting. I've yet to investigate if that's the best setting to use (but that's for another discussion). It works.

    HDR10 conversion to Dolby Vision seems to work fine, although once (and only once), while seeking to the next chapter of a UHD remux it reverted back to HDR10 native, with a message saying that conversion was not available. No amount of selecting different conversions with the O menu made a difference. I had to stop playback and restart. At that point seeking went fine and I was not able to replicate.

    While we'll have probably a private conversation about this, I tested my HDR10 "screen intermittently blanking" situation and I've discovered that with 12.2.1 stable HDR10 playback is rock solid. No screen blanking. With 13.0-nightly-20261101-f59641e (latest available when I downloaded), instead, HDR10 "screen intermittently blanking" happened exactly like in your builds.

    Another thing that I tested and that, at this point, falls outside the scope of your builds I suppose, is the video levels situation. On my machine the Settings/System/Display video levels setting is basically broken. If I selected limited video levels (the correct setting for my OLED TV connected system, calibrated to 16-235), black levels are raised. BUT, and here's why I choose to report it here, they are not raised (they are displayed correctly) when going through a Dolby Vision conversion process. So I have Mehanik HDR10 test files and if I play them with native Kodi HDR10 playback, blacks are raised. But if I select Dolby Vision conversion for HDR10, black levels are correct.

  • Hi guys,

    My RAM sticks have RGB (they were the only ones I could find at the time), and I hate RGB. I don't want the lights on, but turning them off usually requires software running in the background. Whenever the PC reboots, the lights turn back on during boot, then turn off in Windows once the software starts. Now, when I boot into LibreELEC without that background software, the lights stay on. Any idea how to solve this?

  • FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.

    The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview

    Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.

    Changes since R1.0.0-RC2

    Dolby Vision

    • Added GPU bilinear FEL upscaling, replacing the nearest-neighbor fallback when VAAPI scaling is unavailable.
    • Added the Reference GPU FEL filter as a selectable option for other conversion modes. Master Reference retains its reference filter.

    Playback and stability

    • Fixed cases where stopping playback during a resolution change could leave HDR signaling active instead of returning to SDR.
    • Fixed stale HDR10 session reuse after a rejected output activation, ensuring subsequent playback prepares the required output surface.

    Settings

    • Separate remembered rendering preferences for Dolby Vision, HDR10 and HDR10+ inputs.
    • Automatic fallback no longer replaces the preferred rendering mode.
    • Fixed rendering options incorrectly remaining unavailable after stopping a different source format.

    HDR10+

    • Fixed source-specific preference selection during continued HDR10+ playback, preventing accidental use of the plain-HDR10 preference.

    Player information

    • Corrected misleading "Unused blocks" reporting: metadata forwarded to the TV is no longer marked unused.
    • Displays whether CM2.9-to-CM4 conversion is actually active, including live updates for Auto and Auto 2.

    Blu-ray menus

    • Updated BD-J Java add-on packaging with matching libbluray 1.5.0 support files.
    • Prevented stale or incomplete Java support files from being packaged. Requires the updated JRE add-on attached to this release.

    Thank you so much for your work. Ive tried RC2 on a rtx 3080 and it works pretty well except that the player freezes when i bring up the dv mode screen (double pressing O). That is on a fel movie, mel doesnt have it. Also black screen after closing a video but i think it can be my hdmi cable.

  • chewitt since part of the above applies to current nightlies (HDR10 intermittent screen blanking and video levels being output incorrectly), could you point me to the correct way to report these? I am used to report stuff in Kodi but I'm new to LE. Thanks.

  • Depends on what kind of bug report you are submitting. If you have triaged the issue and have a strong idea on the problem open a ticket on GitHub with all the information. Otherwise (and esp. if the issue was diagnosed with AI tools, start a thread in here first to avoid the noise.

  • If you have triaged the issue and have a strong idea on the problem open a ticket on GitHub with all the information. Otherwise (and esp. if the issue was diagnosed with AI tools, start a thread in here first to avoid the noise.

    No AI to diagnose anything. It's clearly visible to the naked eye. Screen blanking with HDR10 and wrong levels checked with test patterns. I'll open a thread here, hoping to find the right section.