[x86-64][hadesdevls Builds] LibreELEC Hades - native Dolby Vision, HDR10+ and 3D

  • Quote from ht2tweak

    Post #1 updated. hadesdevls , LMK if anything else should be added, also w/new users in mind.


    ht2tweak Looks good to me, thanks for keeping it up to date. Just one row in the settings table: Hades doesn't have "Asynchronous Frame Preparation", that one is from CroqueMr's build. The setting that does that job in Hades is "Present frames a frame ahead", which is already on When needed by default, so that row can go or be renamed.

    For new users, two short additions you could paste:

    Installing
    For an easy install from Windows, you can use the installer made for Hades (LibreELEC-Hades-Installer.exe, from the release page, with the .img.gz and .sha256 next to it). Any other image writer like Rufus or balenaEtcher works too with the .img.gz.

    Reporting problems
    Please report problems in the GitHub issues, not to LibreELEC or Kodi. Say which graphics card and TV you have, how they're connected, and what you were playing, and attach a diagnostic report from Settings > LibreELEC > System > Submit Log > Create a diagnostic report.

  • LibreELEC Hades 1.1 is out

    Download LibreELEC Hades 1.1: the image, the update file and the Windows installer.

    New things to see and to choose, and fixes for what you reported after 1.0. Thank you to everyone who tried 1.0 and wrote here and in the issues: much of this version comes from your reports.

    The highlights

    • The player information, redesigned and reachable with a remote. Press O: one frame with the path of the signal at the top (the film, Hades, your TV) and a bar with the processor, the graphics, dropped pictures and the output button. O, then OK, changes how a Dolby Vision video goes out while it plays, from a remote, a keyboard or Yatse. The System page now says how the TV is connected.
    • Any HDR film as SDR, Dolby Vision included, from the output choice of that video. HLG videos get the choice too.
    • HDR on a display without HDR is mapped again. Every profile of 1.0 had the tone mapping of Kodi set to "Off", which left HDR washed out on an SDR display or projector. It is switched to "Reference (BT.2390)" once.
    • Menus and subtitles over HDR keep the shadows they have in SDR (the curve of BT.1886, as ITU-R BT.2408 says).
    • For those who like to tune (Expert, off by default): the upscalers RAVU, FSRCNNX 8 and FSRCNNX 16, measured closer to the original than Lanczos 3; HDR10 mapped scene by scene for projectors and SDR; SDR videos made in BT.2020 in their wide colours (Advanced); zoom to the active area of Dolby Vision films for 2.35:1 and 2.39:1 screens; and video at its own rate with VRR, either always, so that the screen does not go black when a video starts or stops, or only where the display has no mode at the rate of the film (PC monitors without 24, 48 or 72 Hz).
    • Adjust display resolution (Player > Videos, off by default), next to Adjust display refresh rate: a 1080p video goes out at 1920x1080 at its own rate, so that the TV scales it. Native Dolby Vision stays at 3840x2160.
    • The right refresh rate in more cases: a 1080p film gets 3840x2160 at 23.976 Hz on a TV whose menus are at 2560x1440, each display keeps the resolution of its own menus, and HEVC videos whose pictures are whole are shown as progressive (25p at 25 Hz).
    • Dolby Vision: Low-Latency that cannot use the values of the display falls back to Standard, or to HDR10 with the enhancement layer; colours past BT.2020 (laser projectors) are taken to its edge; no active area (level 5) that the video does not have; frames ahead for a graphics card held to a low power limit; the whole black bars of an HD encode with an RPU of its own; and Dolby Vision through the converter of a USB-C hub or adapter (Expert).
    • Sound: a display that takes PCM of 16 or 20 bits only gets sound; Intel Alder Lake (N97 and N100 too) no longer goes silent after Dolby Vision with a passthrough track; an output kept on for an AV receiver keeps its sound; Dolby Digital at 32 kHz passes through; 6.1 and 6.0 tracks keep their back centre.
    • Files and network: seeks no longer stall on a server that allows one connection per file, a change of subtitle track shows at once, and you choose which variety of a language goes first (Castilian or Latin American Spanish, European or Brazilian Portuguese, French from France or Canada, simplified or traditional Chinese).
    • The start: one picture from the boot menu to the interface on a UEFI PC, a notice on the screen when Kodi cannot start, and the hardware clock read as local time or UTC, as it was measured to keep.
    • NVIDIA: the return to 3840x2160 at 120 Hz after a video keeps the HDMI 2.1 link, with a way back at 60 Hz if the picture does not come back. HDMI variable refresh rate is off by default, as on AMD and Intel graphics, because some TVs switch to their game mode with it (Expert turns it on). With two or three displays, a change of mode waits three seconds at most.
    • Windows and Hades on one PC: Restart into Windows in the power menu, and Restart into LibreELEC Hades in the installer (and on the desktop, if you tick its box), without the boot menu key. Each only sets the next start, once; no boot entry is added, removed or moved.
    • Secure Boot, optional and off by default: for a PC that keeps it on, tick Start with Secure Boot in the installer. It makes a key for that PC alone, and the PC asks once to enroll it. The Secure Boot keys of the PC, its boot order and Windows are never touched.
    • Up to date: Linux 7.3.5, the latest commits of Kodi 22 and LibreELEC master, and the security fixes of glibc, OpenSSL, BusyBox, FFmpeg and dav1d.


    Every change, with its details, is in the release notes and the changelog.

    Updating from 1.0
    Your settings and add-ons are kept either way.

    • With the Windows installer: choose the drive that has Hades, then "Update".
    • Or copy the .tar file to the Update folder (the Update share over Samba, or /storage/.update) and restart.


    Two things you may notice afterwards: tone mapping now reads "Reference (BT.2390)" if your profile had "Off", and on NVIDIA, HDMI variable refresh rate stays off unless you turn it on in System > Display (Expert). The installer is not signed, so Windows may ask whether to run it.

    What I would most like to hear about
    These need hardware that I do not have:

    • Chromebooks, and USB-C hubs or adapters, for Dolby Vision and surround sound
    • Secure Boot on a laptop
    • Radeon RX 400, RX 500 and Vega cards with the Dolby Vision path on, and what Check the Dolby Vision output says
    • Video at its own rate with VRR on an RTX 50 card and on AMD graphics
    • Projectors and LCD TVs with Dolby Vision Low-Latency
    • 3D displays, and AV receivers that switch inputs on Intel graphics


    The README lists what has been tested and on what.

    Reporting a problem
    Post here, or open an issue with a diagnostic report: Settings > LibreELEC > System > Submit Log > Create a diagnostic report makes one file and can copy it to a USB drive. A photo of the player information (O) helps a lot.

    Thanks to Felix Oghină, whose pull request for Chromebooks is in this version, done again with his findings; to mephis, for ideas for streams, subtitles and languages; to CroqueMr, whose build pointed to several fixes of this version; and to corgeone, for the measurements with an AV receiver. The upscalers are RAVU by Bin Jin and FSRCNNX by igv, shipped unchanged.

  • Excellent work on Hades v1.1! Thank you for your dedication, hard work, and continuous improvements. The new features and enhancements are greatly appreciated, especially the Dolby Vision, FEL, and Blu-ray improvements. Keep up the fantastic work! 👏

    Thank you, Vertox! When you try it, watch for the short line that appears as a Dolby Vision film starts (for example "Dolby Vision, FEL, 3840x2160 at 23.976 Hz"), and press O for the details: the Dolby Vision page shows every level of the metadata and which of them are used and sent. If you play Blu-ray menus, I'd be glad to hear how they behave on your setup.

  • Hi hadesdevls can you please tell me any technical differences between Hades version and CB1 version because currently I am using CB1 which is giving outstanding picture and sound especially with DOLBY VISION FEL., just need some technical differences.

  • Hi hadesdevls can you please tell me any technical differences between Hades version and CB1 version because currently I am using CB1 which is giving outstanding picture and sound especially with DOLBY VISION FEL., just need some technical differences.

    Hi Ivasan, good question. Right now both builds cover the essentials well, each with its own implementation: native Dolby Vision with the full FEL, Low-Latency and HDR10+ (both added to CB1 in its recent versions), conversions for HDR10 and SDR displays, Blu-ray menus and 3D. Beyond that, each has its own personal touches: separate settings for the picture and how it is shown, and even its own player information panel on O, with different information and a different style. Hades owes its start to CroqueMr, whose Dolby Vision module for Kodi is where it began; where it differs is in a few choices of its own.

    Picture: Hades leans towards sending what the film carries exactly as it is. It does not add creative mapping or metadata the film does not have, and conversions such as HDR10 to Dolby Vision are there as choices, off by default. It can also check, on your own PC, that the bytes leaving it are the ones Dolby Vision needs, and the first page of its panel says in plain words why a video is not playing as intended.

    Hardware: Hades runs on NVIDIA, AMD and Intel graphics, each through its own path in the kernel, and I test on all three (an RTX 4080 SUPER, the integrated graphics of a Ryzen 9 7950X3D and a Core i5-12450H). That covers Radeon cards and Ryzen graphics from Raven and Navi to the RX 9000 series, Intel integrated graphics from UHD 6xx on (N100 included), and NVIDIA from the GTX 900 series on, through its open kernel modules or driver 580 for the older cards. Dolby Vision also goes out through a passive adaptor that identifies itself as HDMI, through the DisplayPort to HDMI converter of a mini PC's board, and, as an expert choice, through a USB-C hub. On TVs and monitors with VRR, a film can play at its own rate without a mode change.

    Security: a media PC often shares its disks with your personal files, and add-ons run with full rights, so Hades starts locked down. When it runs from USB, the PC's internal disks stay hidden (an entry of the boot menu shows them read-only when you want them), devices are kept to their own memory where the PC allows it, and the kernel is locked down. Samba is off until you turn it on, and then it has a password; nothing contacts LibreELEC's update server, since an official update would remove Dolby Vision. Each release is also brought up to date: Linux 7.3.5, the latest commits of Kodi 22 and of LibreELEC, FFmpeg 9.0 with all the fixes of its stable branch and more from its development, OpenSSL 4.1, and the security fixes of glibc, BusyBox, libbluray and dav1d. Hades is compiled offline from verified sources, and every release publishes the sources of everything in it.

    Windows: for a PC that also runs Windows, there is a Windows installer that writes Hades to a USB drive or a second disk and keeps your settings on updates, a restart into Hades and back into Windows without the boot menu key, and Secure Boot as an option that never touches the PC's own keys or Windows.

    Honestly, I'm just glad so many of us are working on Dolby Vision on PC, something that looked out of reach only a few months ago. That started with CroqueMr's initiative, and other developers such as dangerouslaser have pushed it further. A lot of what exists today came from each build steadily improving in its own way, and some of those improvements have travelled between builds, with credit to whoever did them. That is the nice part of open source. There is still more to do, but things are already far more mature than I expected this soon.

    If you are curious, the easiest way is to put Hades on a USB drive and play the same films on both: your current setup stays as it is. I'd be glad to hear what you think.

  • Thank you so much for the detailed technical explanation! That really clears everything up—especially how Hades keeps the signal pure and untouched, along with the hardware and security improvements.

    I'm definitely going to grab a spare USB drive and try a fresh USB installation of Hades 1.1 to test it side-by-side on my setup. Will report back and share my feedback once I've tested a few Dolby Vision FEL titles!

  • Thank you, Vertox! When you try it, watch for the short line that appears as a Dolby Vision film starts (for example "Dolby Vision, FEL, 3840x2160 at 23.976 Hz"), and press O for the details: the Dolby Vision page shows every level of the metadata and which of them are used and sent. If you play Blu-ray menus, I'd be glad to hear how they behave on your setup.

    Thanks! I'll test this on my ASUS NUC 15 Pro AI with the LG OLED G6. I'll check the Dolby Vision information using the O key, verify the FEL metadata levels being used and sent, and thoroughly test Blu-ray menus, including BD-J navigation and playback. I'll share my feedback and any relevant logs. Looking forward to testing Hades v1.1!

  • *Waves*

    Just built a Gmtek Nuc K12, 256gb ssd and 8GB ddr5 ram after rooting a Firetv Cube3 via H2tweak and fell down a rabbit hole and here I am. Initially dropped CB on it earlier tonight and then switched to Hades because 3D, though i'm struggling to get frame packed working there from Bluray rips though (2D and off!)

    I cheated and used the Librelec update folder route, first for CB and then Hades over, I had the Librelec install stick if things failed, but nope, all appears good

    Running on an LG CX5 in the living room and an older Denon Atmos reciever (not showing the atmos speakers) but in the cinema i've got a silly HTP1, Lumagen and JVC X9900 to play with :D

    HLG doesn't check on my LG, showing a dark version of artic skin settings menu. So far all of my test files seem to work fine. Mapping the O key to my Amazon fire remote took way more hassle than expected

    HA....Just checked the specs and the TV doesn't do 3D, must have been my last one, Damn them dropping it. The PJ does and i don't think on my last TV i ever bothered. Far more impact on 120" wides screen there!

  • Hi hadesdevls,

    Thanks for all your work on LibreELEC Hades 1.1. I tested Hades 1.1 side-by-side against CroqueMr's LibreELEC × CB1 build on the exact same hardware chain and test files, and there is a noticeable brightness and contrast difference between the two during native TV-led Dolby Vision playback:

    - Display & AVR Chain: PC (Intel iGPU via VAAPI) -> Denon AVR-X2800H -> Sony A80K OLED (HDMI-A-3, 600 MHz TMDS, Dolby Vision Bright picture mode, ambient light sensor off).
    - Test Files & Overlay Status: Tested both 4,000-nit Profile 7 FEL (CM2.9) and 1,000-nit Profile 7 MEL (CM2.9) titles. The Hades O -> Dolby Vision overlay confirms Native, TV-led (RGB 8 bits, no dithering (DV 4:2:2 12 bits)) with BL + EL (FEL) decoded properly.
    - What I Tested in Hades:
    1. Default (As in the video / CM 2.9 passthrough)
    2. Injecting CM v4.0 (Mapping sent: v2.9 + v4.0 added)
    3. Disabling studio trims (Trims: left out / L2 excluded)
    - Observation: Even with CM v4.0 metadata added and L2 trims excluded, Hades's native TV-led output on the Sony A80K looks noticeably dimmer with lower perceived contrast/midtone punch compared to CB1 on the same TV and AVR input. Is this strictly down to CB1's Adaptive HDR Mapping / dynamic metadata handling versus Hades's unadjusted reference output, or is there any difference in how the IPT tunnel / HDMI InfoFrame or L1/L2 metadata is packaged for Sony TVs?

    Happy to upload a debug log or test a specific sample/setting if you'd like to compare the exact outgoing packets.

  • hadesdevls
    Say that you wanted hear about 3D. I have access to basically every type of 3D display there is. I have computers with Intel integrated, Nvidia 1000, 2000, 4000 and 5000 series, AMD APUs one older and one 780M.

    Anything specific you want me to test/do?

  • The default modes in my build are the "purest" ones, their goal is to remain as faithful as possible to the film without altering it. (Dolby Vision Master reference / HDR10 Native)

    Adaptive HDR mapping mode in my build affects the director's original intent, it expands the brightness range to fill the dynamic range that your display can reproduce. I don't believe there is an equivalent mode in Hades, you can not compare this rendering mode with a an unaltered rendering path.

    In any case, regarding the differences: there aren't that many. Hades continuously incorporates my additions and ideas, so the builds have converged quite a bit, mains differences will on hardware supported I believe Hades' build runs a bit better on Nvidia, whereas in my own, things feel more efficient on small Intel or AMD iGPUs. That’s what I observed when I ran a comparison a while back and measure the performances. Things may have evolved since then, and can, of course, continue to evolve.

  • Quote from Alaric

    HLG doesn't check on my LG, showing a dark version of artic skin settings menu.


    Welcome, and what a cinema room! That card plays a 15 s HLG clip at 3840x2160 50 Hz (the others are 23.976). The dimmed settings menu is what sits behind the question that comes after the clip, so the clip either never showed or got cut short. Could you paste the HLG part of Settings > LibreELEC > System > Check this setup > Show the last result? It keeps what went out for each card. Was the Denon in the chain for that run?

    Quote from Alaric

    older Denon Atmos reciever (not showing the atmos speakers)


    The speaker plan in the player info shows the channels the track itself carries. Most Atmos tracks carry the heights as objects, so you'll see 7.1 or 5.1 lit while the Denon places the objects. Its front display is the real check: it should say Dolby Atmos.

    Quote from Alaric

    Mapping the O key to my Amazon fire remote took way more hassle than expected


    Sorry about that. Over Bluetooth its menu key (three lines) arrives as a keyboard Menu key. This in /storage/.kodi/userdata/keymaps/firetv.xml makes it open the player info, and the same key closes it:


    And when Hades gets to the JVC, I'd love to hear how 3D looks on 120".

    Quote from lvasan

    Is this strictly down to CB1's Adaptive HDR Mapping / dynamic metadata handling versus Hades's unadjusted reference output, or is there any difference in how the IPT tunnel / HDMI InfoFrame or L1/L2 metadata is packaged for Sony TVs


    CroqueMr has answered the first half: Adaptive HDR Mapping widens the range on purpose, and Master Reference is the faithful mode of CB1, so that's the one to compare with.

    On the second half, this is how Hades packs it. The picture goes as the RPU composer outputs it, BL plus FEL, bit for bit in the 12-bit 4:2:2 tunnel, as YCbCr with the matrices of the RPU (IPT only if you choose it under Transport). Per frame: L1, L2, L4 and L5, and the CM 4.0 blocks when the TV declares DM4 or when you add them. The Dolby InfoFrame carries only the DV bit, and the AVI is RGB full range. Nothing in it is specific to Sony. As far as I can tell from the CB1 source, Master Reference sends the same form, the same levels and the same InfoFrame, so I'd expect the two to look very close.

    If they still don't, I'd like to compare what each one sends, byte for byte. On Hades: Settings > LibreELEC > System > Submit Log > Save diagnostics at every start, restart, play a minute of the FEL title, then Create a diagnostic report. That keeps what went out to the TV during the film, next to kodi.log.

    Quote from CroqueMr

    The default modes in my build are the "purest" ones, their goal is to remain as faithful as possible to the film without altering it.


    Thanks for jumping in and explaining your modes, that answers the main question better than I could.

    Your work is what got Dolby Vision on PC going in the first place, and your build has pointed me to several fixes. When two builds aim at the same thing, the picture as the studio made it, they're bound to end up close, and I take that as a good sign for both. As you say, each has its strengths and both keep evolving, which is good news for anyone with a PC under the TV.

    Quote from NTM-3D

    Anything specific you want me to test/do


    Yes please, and thanks again for the tests on the Philips and on the A10 laptop, 3D through a 1$ adaptor was a nice one to see. What would help most now:

    • An RTX 20, 40 or 50 card, in frame packing: on NVIDIA it comes from a patch of mine to the driver, and it's the part I'd most like a report on.
    • The 780M, in frame packing.


    A 3D Blu-ray (disc, ISO or folder) or an MVC MKV is enough, with Player > Videos > Adjust display refresh rate on. Does the display switch to 3D by itself, in which format, and does each eye look right? A photo of the player info (O) helps, and a diagnostic report if something looks off.

  • Thanks CroqueMr and hadesdevls for the detailed explanation!

    CroqueMr bro, you know very well how much I am obsessed with your build 😊 — I've been using it daily and love it.

    Just to clarify my comparison: even when I switch CB1 to its faithful Dolby Vision Master Reference mode (not Adaptive HDR Mapping), CB1 still looks noticeably brighter and punchier on my Sony A80K OLED than Hades 1.1's Native TV-led output on the exact same HDMI port, AVR (Denon AVR-X2800H), and Profile 7 FEL test files.

    So there does seem to be a difference in how the Sony A80K interprets the outgoing signal or metadata between CB1 Master Reference and Hades 1.1. I will capture the diagnostic report in Hades (Settings > LibreELEC > System > Submit Log > Save diagnostics at every start) during a 1-minute FEL playback and share it here so you can compare what goes out to the TV.

  • Thanks CroqueMr and hadesdevls for the detailed explanation!

    CroqueMr bro, you know very well how much I am obsessed with your build 😊 — I've been using it daily and love it.

    Just to clarify my comparison: even when I switch CB1 to its faithful Dolby Vision Master Reference mode (not Adaptive HDR Mapping), CB1 still looks noticeably brighter and punchier on my Sony A80K OLED than Hades 1.1's Native TV-led output on the exact same HDMI port, AVR (Denon AVR-X2800H), and Profile 7 FEL test files.

    So there does seem to be a difference in how the Sony A80K interprets the outgoing signal or metadata between CB1 Master Reference and Hades 1.1. I will capture the diagnostic report in Hades (Settings > LibreELEC > System > Submit Log > Save diagnostics at every start) during a 1-minute FEL playback and share it here so you can compare what goes out to the TV.

    Ah ok, I think hadesdevls it may come from that https://github.com/CroqueMr/libreelec-CB1/pull/212

    My build has been thoroughly examined and compared to ensure that the implementation is right, https://github.com/fandangos pointed out a few minor discrepancies between my build and a licensied DV. He found one small issue, fixed since 1.0.1 RC1.

    Or maybe lvasan you are on an old build before 1.0.1 RC1 and the issue is from my build.

  • Ah ok, I think hadesdevls it may come from that https://github.com/CroqueMr/libreelec-CB1/pull/212

    My build has been thoroughly examined and compared to ensure that the implementation is right, https://github.com/fandangos pointed out a few minor discrepancies between my build and a licensied DV. He found one small issue, fixed since 1.0.1 RC1.

    Or maybe lvasan you are on an old build before 1.0.1 RC1 and the issue is from my build.

    Thanks CroqueMr! I just checked my System Information screen and I am actually running the latest build (newer than 1.0.1 RC1):

    - OS: LibreELEC (community): DV-R1.0.1-RC2 13.0 (kernel: Linux 7.2.6)
    - Build: 22.0-RC1 (21.90.901)
    - Git: 28ea2eac1eb7af8fdcbd2672d933ce87f594be79 (Compiled: 2026-11-19)

    So PR #212 is already in my build, and even in Dolby Vision Master Reference mode, DV-R1.0.1-RC2 still looks noticeably brighter and punchier on my Sony A80K OLED than Hades 1.1.

    hadesdevls — when I get a chance, I'll capture the diagnostic report from Hades during a 1-minute FEL playback and upload it here so you can compare the outgoing packets byte-for-byte.

  • hadesdevls - Thank you for putting these builds together. I love the Player Info details. Great layout.


    I’ve installed your latest build on a Lenovo M75q with a 4650GE. So far, works quite well with both a JVC NZ800 and Xgimi Titan Noir Max running through an Anthem 1140. GPU usage sits between 46-50%.

    Also, going to try your build with a M75q with a 3400GE and Aura 3. The 3400GE units are very inexpensive locally on the used market.

    Is there any specific testing scenarios you’d like confirmed? Be happy to help.