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

    Quote from nissel

    Thanks for all the fixes in RC3.

    Super minor thing, the currently selected "Dolby Vision playback" option in the settings is always displayed as blank even though the option is actually selected and working.

    I have a RC3 hot fix I saw a small issue on one merging branch, i will includ that

    Does anybody know how I can access my LibreELEC OS USB Device? With the Hades fork i could access it without problems in windows to get to the log files, but the Croque main repo for some reason blocks the device with some "no permission to access" prompt.

    Quote from Khazar

    Does anybody know how I can access my LibreELEC OS USB Device? With the Hades fork i could access it without problems in windows to get to the log files, but the Croque main repo for some reason blocks the device with some "no permission to access" prompt.

    Hades build has some security features. You need to do a clean wipe and install if you move to another build.

    So yeah, I did the standard Rufus reformat again, device shows up nicely in the explorer afterwards.

    Install Croq OS unto it, then the explorer says nope. I have to force a drive letter, but then denied access.


    Edit:

    E is the LibreELEC OS USB device, F is the installer for Croq on a USB Stick, F can be opened just fine

    Edited once, last by Khazar (November 4, 2026 at 4:28 PM).

    LibreELEC Hades 1.0 RC6 is out

    Download and release notes: v1.0-rc6 on GitHub

    Dolby Vision and HDR

    • "Dolby Vision output (this video)" applies while the video plays, for HDR10 and HDR10+ videos too, and is kept for each file.
    • For a video that has both Dolby Vision and HDR10+, a setting chooses which one is sent.
    • The content mapping v4.0 as a setting, with "Version 2.9 only" for a TV that shows a wrong picture with v4.0.
    • For projectors: Low-Latency mapped to a peak, colours and black set by hand, a limit on the luminance that HDR10 tells the display, and HDR10 and HDR10+ mapped to the display in the player.
    • Dolby Vision sent as HDR10+ version 1 carries DistributionY99 and DistributionY100nit as they are defined, and HDR10+ sent as Dolby Vision measures the scenes that come without statistics.
    • HDR10 through the HDMI port of Intel HD and UHD 6xx graphics goes out as Dolby Vision where the TV takes it.
    • Menus over Dolby Vision cost less GPU time on light graphics, with the same bytes sent.
    • Dolby Vision also with a long "Delay after change of refresh rate", Dolby Vision in two tracks a constant apart, and a more exact IPT tunnel.

    Display and HDMI

    • A TV switched off and on in a 4K mode at 50 or 60 Hz, or one that goes by FRL, gets its picture back on NVIDIA and AMD.
    • Limited colour range is compressed once, by the driver, on Intel, AMD and NVIDIA.
    • The HDMI patches of big-fella from YBLOD for Intel and AMD: short drops of the hot-plug signal held, the TV told that the source is a player, and a black background on Ryzen with Vega graphics.
    • On NVIDIA: Dolby Vision in the 4K modes that the driver names by their HDMI VIC (also with driver 580), three buffers for the window, and a change of resolution on an HDMI port driven through DisplayPort.
    • A change of mode that the driver refused is asked for again, and whole-number multiples of the frame rate can be kept under the whitelist.
    • An EDID extension block that is not valid is skipped, the same in Kodi and in the kernel.

    Subtitles, files and sound

    • Picture subtitles (PGS and VobSub) can be resized, moved and dimmed, from the pull request of cinemaONE to Kodi.
    • Text subtitles come back after a seek, also when the line started before the place the player reads from.
    • Editions of Matroska files, as an option.
    • Dialogue normalisation at 0 dB in passthrough, the compression of Dolby Digital in the audio settings, the centre level and the LFE up to 300 % for a downmix, and audio settings that apply during playback.
    • The player information says more of the sound (the bed and objects of Atmos, the dialogue level), and kodi.log says why a stream is not passed through.
    • CEC fixes for Pulse-Eight adapters.

    Interface
    A dialog that does not finish closing no longer leaves Kodi ignoring the remote and the keyboard, the settings window no longer saves the mode of a video as the resolution of the interface, and only what changes is drawn again when the focus moves in a list.

    A new boot menu
    Drawn for LibreELEC Hades: the eclipse of its mark on black, and the four entries, each with a line that says what it does: Run (recommended, first, starts by itself after 10 s), Run (internal disks read-only), Live and Installer. With several displays connected, the notice that Kodi uses one of them is now a picture on the start screen.

    Blu-ray
    Blu-ray playlists played directly keep one timeline across their seamless joins, so a film with several cuts no longer freezes or skips at each join. Menus are kept apart from subtitles, a 3D display can be simulated for discs that need one, 3D subtitles keep their depth, and movies on discs are kept right in the library.
    Blu-ray Java menus now play with nothing to install, in a service of the system, never inside Kodi: one process for each disc, with the Java runtime that comes with the image, a user of its own without privileges, a filter of system calls and no network, reading the disc only through Kodi. The idea of Java menus with nothing to install comes from the build of CroqueMr; the service that isolates them is written for Hades. BD-Live is there as an option, off by default, and with it the menus reach the Internet and nothing else: never this machine or your home network.

    Also: a diagnostic that keeps the log of a start that hung and filters the names of your drives and folders, a firewall that no longer stays open on a damaged setting, the Dolby Vision module of Kodi now under GPL-2.0-or-later, Linux 7.3.1, the latest of the Piers branch of Kodi, and many fixes from upstream.

    What is new in RC6 has not been tried on hardware yet, so reports in the issues are very welcome.

    What is new in this version is written for Hades, apart from the code of others that it takes, which keeps its author. Several features follow ideas seen in other builds, written anew here: from the build of CroqueMr, the CoreELEC builds of pannal (p3i), avdvplus and SamuriHL, matthane, YBLOD and Sebastiii. Thanks to them, to quietvoid and cinemaONE for definitions and measurements, to everyone who reported in the issues and here, and to the LibreELEC and Kodi teams.

    Quote from CroqueMr

    Release R1.0.0 RC3 · CroqueMr/libreelec-x86-DV

    I've already upgraded to RC3, but I just saw your note about the FEL seeking regression and that RC3 has been withdrawn.

    To be honest, I'm a bit confused now, especially with the R1.0.0-RC3 Preview release. I'm not sure which version I should be installing anymore.

    Would you recommend going back to RC2 for now, staying on my current RC3 build, or installing the RC3 Preview instead?

    Just want to make sure I'm using the right version until the fixes are ready. Thanks again for all your hard work.

    Quote from CroqueMr

    The issue come from your file, the FEL layer is broken, but I’m still going to incorporate more robust reading methods for imperfect files

    I´`´ m sorry for the false alarm. :cry:

    I ripped it again with makemkv -> no problems.

    and I paid for the ape :cursing:


    I used the R1.0.0-RC3 Preview since 2 days, just now you released

    R1.0.0-RC3

    @CroqueMr CroqueMr tagged this 5 hours ago

    Code
    release: finish R1.0.0 RC3 fixes

    is this another version as my 2 days old preview:?:

    hadesdevls

    Thanks to 1.0 RC6, the GTX 1060 issue is resolved, and DV works as expected at all refresh rates. The only issue remaining is that the HDR output signal is 8-bit rather than 10-bit.


    Really appreciate your fantastic work!

    Quote from Vertox

    I've already upgraded to RC3, but I just saw your note about the FEL seeking regression and that RC3 has been withdrawn.

    To be honest, I'm a bit confused now, especially with the R1.0.0-RC3 Preview release. I'm not sure which version I should be installing anymore.

    Would you recommend going back to RC2 for now, staying on my current RC3 build, or installing the RC3 Preview instead?

    Just want to make sure I'm using the right version until the fixes are ready. Thanks again for all your hard work.

    No it is very small keep using it, it concerns some niche FEL DT, RC3 with the fix will be push tomorrow.

    Quote from sat4all

    hadesdevls

    Thanks to 1.0 RC6, the GTX 1060 issue is resolved, and DV works as expected at all refresh rates. The only issue remaining is that the HDR output signal is 8-bit rather than 10-bit.


    Really appreciate your fantastic work!

    sat4all Thanks for testing and for the photo, good to hear that Dolby Vision works at every refresh rate on the GTX 1060 now.

    About HDR at 8 bits: your card and its driver can show a 10-bit picture (your RC5 log lists 10-bit and floating point formats for the display plane), but the 580 driver gives Kodi only 8-bit windows to draw in, and the driver sends HDR10 at the depth of that window. On the GTX 16 and later, with the 615 driver, Kodi draws in a floating point window and HDR10 goes out at 10 bits. So it is a limit of the way Kodi draws with the 580 driver, not of the card, and I'm looking at a way around it: drawing into a 10-bit buffer directly instead of a window. I can't promise it yet. What you see now is still HDR10 (PQ, BT.2020), with 8 bits per colour on the cable.

    Quote from hadesdevls

    sat4all Thanks for testing and for the photo, good to hear that Dolby Vision works at every refresh rate on the GTX 1060 now.

    About HDR at 8 bits: your card and its driver can show a 10-bit picture (your RC5 log lists 10-bit and floating point formats for the display plane), but the 580 driver gives Kodi only 8-bit windows to draw in, and the driver sends HDR10 at the depth of that window. On the GTX 16 and later, with the 615 driver, Kodi draws in a floating point window and HDR10 goes out at 10 bits. So it is a limit of the way Kodi draws with the 580 driver, not of the card, and I'm looking at a way around it: drawing into a 10-bit buffer directly instead of a window. I can't promise it yet. What you see now is still HDR10 (PQ, BT.2020), with 8 bits per colour on the cable.

    Thank you for the detailed explanation! Hopefully, you're able to find a workaround in a future build. Fingers crossed!

    hadesdevls can you explain what each option in CMv4 means?

    english is not my native language, so my reading speed is not that fast so i keep up reading of explanations in LE on tv.


    maybe an idea to put CMv4 explanation for each option on the release page on Github?


    and....thanks for everyone for hard work getting rhis done 👍👍

    testmest Sure. The Dolby Vision metadata of a film come with a "content mapping" in one of two versions: 2.9, the older one, and 4.0, the newer one, which many recent TVs can use to fit the picture to their own brightness in a more refined way. Many films carry only 2.9. The setting Dolby Vision content mapping v4.0 (shown at the Expert settings level) decides what Hades sends to the TV:

    As in the video (the default): exactly what the file carries, nothing added or removed.

    Add v4.0 where the video has none: a film with only 2.9 gets a neutral 4.0 part added, the same one that dovi_tool adds by default, so the TV can use its 4.0 mapping. The picture itself is not changed, only the metadata.

    Automatic: adds that part only where the film was mastered brighter than the peak your TV declares, which is where the mapping matters most.

    Automatic 2: no trims in the video: adds it only where the film carries no trims from the colourist, so nothing the colourist set is put aside.

    Version 2.9 only: sends only the 2.9 part, also for films that carry 4.0. It is for a TV that shows a black or wrong picture with 4.0.

    The choice is made once per video, from its first metadata, and the player information shows what is being sent. If the picture looks right with the default, there is no need to change it.

    Every setting is explained in the documentation too: https://github.com/hadesdevls/Lib…ocs/settings.md

    I just tried this out on my GTX1030 and performance was sadly the same with the struggling playback. I did an upgrade install of the image. Do you want me to try a clean fresh image and test again with diagnostics? Maybe I got some other setting I fiddled with that is causing heartburn now, so maybe clean usb drive is the way to go?

    hadesdevls, I'm working on a video for your build. Testing RC6 on N150, because if it functions reasonably well on this machine, it should on better Intel and AMD mini-PC's (my 5800H I'm sure would be better).

    So, RC6 has played everything I've thrown at it, except the 'Transformers' and 'Tron' DV FEL samples (download here). No matter which options I select for DV in settings, they only play in HDR. Only these settings work for 'Saving Private Ryan' and a couple of random DV FEL movies I tested (but not those samples):

    BTW, love the initial installer; it'll be easier for new users (nicer than default LE):

    Edited once, last by ht2tweak (November 5, 2026 at 1:37 AM).

    LibreELEC Hades 1.0 RC7 is out

    Download and release notes: v1.0-rc7 on GitHub

    An update that fixes faults found since 1.0 RC6, which came out earlier the same day, and adds a few smaller things.

    Fixes

    • A film no longer ends when its drive stops answering for a while: the picture waits while the drive is reset and goes on when it answers, also with Blu-ray and DVD images and folders.
    • Limited colour range on NVIDIA is right from the start of Kodi and when the setting changes: no more crushed blacks.
    • The output that carries the sound stays on, found by itself, so a receiver or sound bar on another output keeps its sound. A file can name more outputs to keep on, from the patch of harment.
    • Each UEFI boot entry starts the kernel of its own drive, so a second drive with another build no longer gets in the way. An update in place fixes the menu too.
    • A Blu-ray played with its menus no longer pauses at the seamless joins of a film with several cuts.
    • Dolby Vision whose level 5 metadata do not fit the picture keeps native Dolby Vision, and an open-matte film with the metadata of its letterboxed master shows whole.

    Smaller things

    • "Dolby Vision as HDR10+" for one video in the player, next to "Dolby Vision as HDR10", to compare the two. On Intel, HDR10+ chosen while a video plays now goes out.
    • During native Dolby Vision, the output depth says "8 bits: Dolby Vision carries its 12 bits in them".
    • HDR10 at 10 bits with NVIDIA driver 580 (GTX 900, GTX 10, TITAN V), through buffers that Kodi allocates itself, where the driver takes them.
    • Dolby Vision decoded by the processor (single layer, AV1 included) goes out natively, with the same bytes as from a hardware decoder.
    • An empty /opt for Entware, and diagnostics that record the USB controllers and every disk.
    • Up to date: the Piers branch of Kodi (HEIF and AVIF photos made of tiles, as most iPhone photos are, shown whole) and LibreELEC.

    Every change was tested on the host with the code that the image runs, and the changelog says how for each item. Reports with the diagnostic switch on confirm them on more hardware.

    What is new in this version is written for Hades, apart from the updates of LibreELEC and Kodi and the code of others that it takes, which keeps its author. Two features follow ideas seen in the build of CroqueMr, written anew here: Dolby Vision decoded by the processor, and level 5 metadata that do not fit the picture. Thanks to everyone who reported and tested 1.0 RC6.

    Quote from ApexAftermath

    I just tried this out on my GTX1030 and performance was sadly the same with the struggling playback. I did an upgrade install of the image. Do you want me to try a clean fresh image and test again with diagnostics?


    Thanks for trying it. A clean install should not be needed: an update keeps your settings, and the diagnostic shows them. With RC7, turn the diagnostic on (rename DIAG-OFF.TXT to DIAG-ON.TXT on the boot partition of the drive, or tick the diagnostic box in the installer), play a file that struggles for about a minute, then zip the hades-diag folder from that partition and attach it here or in an issue, with what the file is (Dolby Vision profile or HDR type, and resolution). The log says whether the decoder or the GPU of the card falls behind, and what Hades did about it.

    Quote from ht2tweak

    So, RC6 has played everything I've thrown at it, except the 'Transformers' and 'Tron' DV FEL samples. No matter which options I select for DV in settings, they only play in HDR.


    Thanks, glad you like the installer, and thanks for making a video: RC7 is the one to use for it. When a Dolby Vision video does not go out as native Dolby Vision, the Dolby Vision page of the player information says why. Could you play one of those samples on RC7 and post a photo of that page? With that I can tell whether it is something about how those files are made or about the N150, and fix it.