I have some inside it's promising
this might be the missing piece for LLDV on x86 on iGPU and Dolby vision on ARM port
See? I told you it will all work out in the end. 
Good job and hopefully it will be nice and smooth implementation.
Posts by Khazar
-
-
Khazar thanks! You won't need to know any Linux for it: once it starts, all you see is Kodi. The easy way is the installer for Windows: on the release page, download LibreELEC-Hades-Installer.exe and the .img.gz (with its .sha256) into the same folder and double-click the installer. Windows warns twice because the installer has no paid signature: "More info" and "Run anyway", then allow it to make changes. Pick your USB SSD, type the word it asks for, and it writes the image and reads it back to check it. If you'd rather prepare the drive on a Mac or another system, any program that writes disk images takes the .img.gz as it is (balenaEtcher, for example).
Then restart the PC, open the boot menu (F8 on ASUS, F11 on MSI and ASRock, F12 on Gigabyte and most laptops) and choose the UEFI entry of the SSD. The first start prepares the drive and restarts once by itself. Secure Boot has to be off. If anything looks wrong, tick "Save diagnostics" in the installer and the logs stay on the drive, ready to attach to an issue. Have fun on Friday.
hcliec001 thanks, much appreciated! If you give RC4 a try, I'd like to hear how it goes on your setup.
Oh nice that sounds pretty straightforward, thanks for info!
Even as an USB OS it should have no problem reading another external NVME SSD on an USB-C port for the video files right?
-
Display More
LibreELEC Hades 1.0 RC4 is out:
https://github.com/hadesdevls/Lib…es/tag/v1.0-rc4DOLBY VISION
- Native Dolby Vision on GeForce GTX 900, GTX 10 and TITAN V. NVIDIA's driver 615 doesn't support them, so Hades now also carries driver 580, patched to give Kodi native Dolby Vision, Low-Latency, HDR10+ and 3D frame packing. It's chosen at boot. Nobody has run it on one of these cards yet.
- Zoom, vertical shift and stretch keep native Dolby Vision, scaled the way a certified player scales them. A 1080p video on a 4K screen is now scaled the same way, which brings it closer to the 4K master (average ΔE ITP 0.349 to 0.266 on profile 5 film, measured in software).
- New: Dolby Vision sent as HDR10+, for HDR10+ displays without Dolby Vision such as many Samsung TVs. The film is rebuilt and sent with HDR10+ metadata that Hades measures from the picture, scene by scene (Hades' measurements, not the studio's). Seen working with a profile 7 FEL film on a Samsung Odyssey OLED G6. Off by default.
- Profile 8.4 (the HLG Dolby Vision that iPhones record) goes out natively where its metadata declare PQ, profile 8.2 is composed as the specification describes, and profile 5 is always rebuilt where it can't go natively.
- The 2016 Dolby Vision TVs that need the older HDMI 1.4b signalling, LG's OLEDs of that year among them, get it as an option on Intel, AMD and NVIDIA.
- Discs with flat Dolby Vision metadata can play, per video, with metadata measured from their HDR10 picture.
- Fewer ways to lose native Dolby Vision: an unusable v4.0 metadata block is skipped, NVIDIA's driver now hands Kodi the whole EDID, and the output is set again after a wake from suspend.HDR10+, HDR10 AND THE DISPLAY
- HDR10+ seen working on a Samsung Odyssey OLED G6 from an RTX 4080 SUPER, with the values sent shown in the player info.
- A bug in NVIDIA's own driver fixed: its InfoFrames lost their last byte, which cut HDR10 MaxFALL values of 256 and above and signalled top-and-bottom 3D as frame packing.
- HDR10 on NVIDIA to TVs that declare HDMI 3D (NVIDIA's driver sent the 2016 LG OLEDs none), and at 4K 24, 25 and 30 Hz to TVs that take those modes by HDMI VIC.
- SDR at 8 bits on NVIDIA and Intel, as Windows sends it, and an option to hold HDR10 and HLG at 8 bits for TVs with 8-bit panels.
- New TV modes, such as Deep Colour turned on at the TV, are picked up without a restart.
- On NVIDIA laptops whose HDMI port is dual-mode DisplayPort, Dolby Vision starts once the video's mode is set, with the link brought up from scratch.FASTER, SAME BYTES
Each of these leaves the output identical, checked with the Dolby Vision bridge running in software: fewer row reads and half floats in the enhancement layer's resampling (24.9 to 12.4 MB per 4K FEL picture), 16-bit composed planes, both 4:2:2 rows of each 4:2:0 row from one shader invocation, repeated pictures recommitted instead of redrawn on NVIDIA, Dolby Vision as HDR10 kept at 10 bits, and the windows over a video loaded ahead while the menus are idle.
SMOOTHER ON MODEST GPUS
Frames that keep missing their refresh are presented a frame ahead, frames with menus over profile 7 FEL step down only on GPUs that can't keep up and only while the menus are up, and the enhancement layer's decoder waits for a free surface instead of restarting the layer. On the 7950X3D's integrated Radeon, profile 5 with the player info up went from 32, 31, 58 and 6 late frames per 10 s in RC3 to 26, 8 and 0.
DISKS, SOUND, GRAPHICS
- A USB start now keeps every internal disk away. Disks on controllers other than NVMe and AHCI (SATA in IDE mode, RAID, UFS, virtio, eMMC) used to be mounted read-only.
- You choose which internal disks and partitions are shown. An unticked disk is released before anything else runs, with the kernel locked down.
- Until you choose an audio output, Kodi uses the HDMI output of the display it's showing on.
- Blu-ray Java (BD-J) menus can run with the "JRE for BD-J menus" add-on.
- Intel Arc B and Core Ultra 200V get the xe firmware they need for a picture.UP TO DATE AND SAFER
Linux 7.3, LibreELEC and Kodi 22 "Piers" at their latest commits, OpenSSL 4.1.0 and Python 3.14.10. Known security issues fixed in avahi (17 CVEs), expat, OpenSSL, glibc, BlueZ, BusyBox, FFmpeg and MariaDB Connector/C, plus two that upstream hasn't fixed yet, fixed in Hades: connman (CVE-2026-115863) and avahi (CVE-2025-59529).
TESTED
With this image on my Ryzen 9 7950X3D: Dolby Vision 5, 7 FEL and 8.1, HDR10 and TrueHD Atmos with an LG C5 on both the RTX 4080 SUPER and the integrated Radeon, and HDR10+ plus a profile 7 FEL film sent as HDR10+ on a Samsung Odyssey OLED G6 from the 4080. Everything not tried yet is listed in the release notes.
If you have a GTX 900 or GTX 10 card, a 2016 LG OLED, an HDR10+ TV or Intel Arc B graphics, I'd especially like to hear how it goes.
Very nice release, can't wait to test it this Friday when my SSD USB-stick arrives.
Hopefully I can follow the installation instructions, haven't dealt with Linux in a decade.
-
I understand your need but it's clearly not my priority in term of dev.
I'd rather focus on offering a viable alternative to Amlogic based devices, delivering perfect Dolby Vision playback at a lower cost and/or much better responsiveness for a similar price.I wouldn't spend time implementing LLDV if it could only run on NVIDIA or dedicated GPUs. I just don't see the point compared to a $300 Amlogic box that already does LLDV. We'd end up with a much more expensive solution.
If I ever implement LLDV, it'll only be if we can make it work on hardware priced similarly to Amlogic devices, and finding new optimization lever to manage to fit LLDV on small iGPU it's not my top priority. Maybe in the futur after my stable release.
Oh of course you taking care of the timeline and what makes it into the build, is your prerogative after all as the dev. I respect that fully.
But as you said, so far we don't know the cost for LLDV with your solution right? So that means for now we don't know if it can run on an iGPU or not. There is still a chance for it to not need anything too heavyweight, even if it can't reach a specialized chip in economy.
Also to bring in a point or perspective:
- Not having to import a 300€ box
- Not having to import in a more and more hostile and expensive import environment
- Not having to worry about spending 300€ on something with shaky if not non existent warranty
- Not having to buy and setup another HDMI cable
- Already owning a PC anyway
- Not already owning those boxes
Again not trying to force it, just wanted to help to see the perspective of someone already with a PC and no box.
If you ever implement it, after the stable build is released, I will still be a happy camper.
-
By any objective measure, I doubt a SDR-->DV conversion would bring a better experience to your projector. In any case, CroqueMr has spoken, so any discussion about this is kinda useless anyway.
Yeah I don't know what discussion you're reading, but you're way out of line.
-
Very complicated. I already have a DV-to-HDR10 mode that works somewhat like LLDV, but outputs HDR10. Of course this mode is not a real DV output but it manages the more important DV adjustment.
However, doing true LLDV would require significantly more processing power on the PC side. It would only be feasible on much more powerful hardware, or with some massive optimizations that I honestly have no idea how to pull off without impacting image quality.Well you and Hades opened the box for Gaming and Workstation PCs now, so why not see where it goes?
We might not have the super specific chips of the small boxes, but some of us have raw power 600W GPUs and high core 3D Cache CPUs.
PC users are used to not being able to run the latest and heaviest graphic settings all the time, sometimes a hardware update needs to happen first, so as long as those heavy modes get declared correctly, I wouldn't see the issue with it.
If it means my heavy weight PC can deliver an even better experience to my projector, then I'll gladly take it.
