Dolby Vision w/FEL + 3D for PC (AMD/Intel/nVidia)

    Quote from CroqueMr

    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.

    Quote from chewitt

    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.

    Quote from Silver11211

    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.

    Please send me the log, and could you try the RC3 preview and tel me if you have the issue?

    Quote from siriusbox

    ashlar how that NUC performs?

    It's fine. Were it not for the problems I describe, from what I've seen it would work great to watch a movie at top quality. Due to the problems, I'm not using it as a daily driver (yet?). But, performance wise, it looks to be up to the task (it's a more powerful than the baseline N100 that's been targeted).

    hadesdevls  CroqueMr

    I think I might know the culprit now that makes the start-ups sporadic (not impossible, but sporadic)

    It seems like LibreELEC get hung up on my dedicated PCI soundcard. I have disconnected it and now the start-ups are consistent.

    Both versions show now zero problems with starting, since I removed the PCI soundcard.


    CroqueMr the problem with the Wifi mouse and keyboard extend to your version too sadly.

    For some reason with LibreELEC the distance to where they both work away from their USB-dongles is severely reduced compared to Windows 11. I have to put the mouse like 1-2 meters close to the dongle for it to work fine in LE, any idea why that could be?

    One is for the Keychron M5 8K
    and the other is for a generic cheap Rii keyboard
    Both are used with their Wifi signal.

    P.S. Oh and also the mouse worked pretty fine(not great but fine) in the setup menu in the beginning of the very first start, but as soon as it's in the main menu the outages begin.

    Edit: could it be that the USB dongle or devices in general are being run in some low powered mode to save energy or something?

    Edited once, last by Khazar (November 2, 2026 at 5:31 PM).

    absolutely incredible work.. the only thing missing now would be an equalizer apo method to implement better filters and not be limited by audio systems, or if someone as talented as you could pitch in to implement something similar it would probably be the most breaking thing ever.

    keep up the amazing work, absolutely stellar work

    Quote from theonepugna

    the only thing missing now would be an equalizer apo method to implement better filters and not be limited by audio systems

    We already had that equalizer discussion. In short, an A/V stream is like a heavy train. If you want to change something inside of a wagon, you have to stop the whole train. Not a good idea (buffer size, CPU/GPU speed etc.).

    I've been testing HDR10 Expert on a Samsung S95H (TV peak set to 2600, static tone mapping) with the CroqueMr RC3 build on a 780M box, and a few DV titles look wrong:
    - The Shining: washed out, especially the opening aerial shots.
    - Ocean's Eleven: black crush in darker scenes.

    Switching to HDR10 Basic (or native Kodi) fixes both. Can anyone else reproduce this?

    I had Claude Code go at it with a private build and some additional debug logging, don't know if it's on to something or not:

    Expert applies the CM2.9 L2 slope/offset/power in linear nits normalised to the TV peak: T * clamp(in/T * slope + offset)^power. Because the offset is multiplied by T, a tiny trim becomes a big black-level shift at high peaks:

    ┌────────────────┬───────────┬─────────────────────────────────────────────┐
    │ title │ L2 offset │ effect at T = 2600 │
    ├────────────────┼───────────┼─────────────────────────────────────────────┤
    │ The Shining │ +0.0033 │ +8.6-nit black floor (washed out) │
    ├────────────────┼───────────┼─────────────────────────────────────────────┤
    │ Ocean's Eleven │ −0.0006 │ everything below ~1.6 nits crushed to black │
    └────────────────┴───────────┴─────────────────────────────────────────────┘

    (Offsets are the values CB1 resolved for a 2600-nit target, offset = code/4096 − 0.5; e.g. code 2061.5 → +0.0033.)

    With nothing changed except skipping the L2 trim step, both titles looked normal. With trims applied they were washed out or crushed.

    Greetings, everyone. Could someone share a working setup for running Windows 11 in a virtual machine—one that allows for full project functionality while enabling the use of the AMD 9950’s integrated graphics core, even when the system is running on a discrete graphics card? I would be very grateful. I’m sure this topic is of interest to many others here on the forum. And a huge thank you to the developer for all their hard work!!!

    Thanks for the feedbacks, I am working on a more precise conversion a real LLDV over HDR10, it will replace HDR expert conversion at target.

    Khazar I've been experimenting similar issues with Nvidia SHIELD Remote, connected by bluetooth with an excellent range in my case, since my Asrock B660 ITX/AC uses antennas for both wifi and bluetooth. In my particular case, the remote pairs but then, it disconnet and connect continously, without any pattern, it's imposible is a problem with any kind of suspend mode y continuosly click buttons on the remote.

    I also tried with a ASUS dongle to discard a incompatibility of the Asrock mother board Intel controller. No luck, same problem.

    NVIDIA SHIELD Remote is particulary interesting since it integrates a IR too, so I can make volume on my a/v receptor works at the same time bluetooth works for the rest, you need SHIELD also to first programm that.

    I'm desesperante with theee disconnetions.

    Hi CroqueMr

    Just a quick heads-up: I've opened a bug report on GitHub about Dolby Vision Master Reference (IPT-PQc2) failing to start playback on my Intel Arc NUC with RC3 Update 5.

    The same movie plays fine when I switch to Dolby Vision Reference. I've included logs from both the failed and successful attempts so you can compare them.

    Thanks again for all your work! Really appreciate it.