hadesdevls/LibreELEC-Hades v1.0-rc4

LibreELEC Hades 1.0 RC4

on GitHub

LibreELEC Hades is LibreELEC for 64-bit PCs with native Dolby Vision over HDMI (the TV-led "Standard" mode that Dolby Vision TVs expect), profile 7 with its full enhancement layer included, from NVIDIA, AMD and Intel graphics, with Dolby Atmos passed through untouched.

1.0 RC4 brings native Dolby Vision to the GeForce GTX 900 and GTX 10 series and the TITAN V, keeps it through zoom and stretching, sends Dolby Vision as HDR10+ to displays that only take HDR10+, and adds iPhone profile 8.4 and the Dolby Vision TVs of 2016. It runs on Linux 7.3 and closes a long list of security issues.

Dolby Vision

GeForce GTX 900, GTX 10 and TITAN V

NVIDIA's driver 615 does not support these cards. Hades now also carries driver 580, with its own patches to the driver's open part so that Kodi gets what it uses on newer cards: native Dolby Vision, Low-Latency, HDR10+ and 3D frame packing. The driver is chosen at boot from the card's PCI ID. Nobody has run it on one of these cards yet. Its kernel module holds NVIDIA's closed core as NVIDIA ships it, and the image is about 120 MB larger.

Zoom, vertical shift and stretch

They no longer drop native Dolby Vision. The visible part of the picture is scaled as a certified player scales it, in the video's own colour representation, and the metadata describe that part. A 1080p video on a 4K screen is now scaled the same way, which brings it closer to the 4K master: average ΔE ITP from 0.349 to 0.266 and from 0.382 to 0.312 on two profile 5 film pictures, measured in software.

Dolby Vision sent as HDR10+ (new)

For displays that take HDR10+ and not Dolby Vision, as many Samsung TVs. The film is rebuilt and goes out with HDR10+ dynamic metadata that Hades measures from the rebuilt picture, one scene at a time, using the scene cuts of the Dolby Vision metadata. These are Hades' measurements, not the studio's. Off by default: Send it as HDR10+ where the display takes it, under "Dolby Vision as HDR10 when needed".

More files and TVs

• Profile 8.4, the HLG Dolby Vision that iPhones record: native where its metadata declare a PQ picture, HLG otherwise.
• Profile 8.2 (SDR base layer): composed as clause 5.5 of the specification describes.
• Profile 5 is rebuilt wherever it cannot go out natively, even with "Dolby Vision as HDR10 when needed" off, because its base layer alone has the wrong colours (issue #2).
• TVs of 2016 that ask for the older HDMI 1.4b signalling, the LG OLEDs of that year among them: "Dolby Vision with the older signalling (HDMI 1.4b)", on Intel, AMD and NVIDIA. Off by default and offered only to a display that asks for it.
• Flat Dolby Vision on older discs (issue #6): in the player's video settings, "Dolby Vision output (this video)" can be set to "Dolby Vision measured from the HDR10 picture", for profiles 7 and 8.1. The file is not touched.
• Blu-ray Java (BD-J) menus (issue #1): the image now carries libbluray's Java part. Install "JRE for BD-J menus" from the LibreELEC repository and restart Kodi; where a menu still cannot run, Kodi says what is missing.

Fewer ways to lose Dolby Vision

• A content mapping v4.0 block that cannot be carried is dropped instead of ending native output.
• NVIDIA's driver passed Kodi only the EDID blocks of the base count, cutting off those that an HF-EEODB adds, where a TV's Dolby Vision block can sit (issue #7). Kodi now gets them all.
• If Kodi stops during Dolby Vision, the console gets the display back without the Dolby Vision signal.
• After a wake from suspend the output is set again, even when Kodi learns of the wake late.

HDR10+, HDR10 and the display

• HDR10+ seen on a display: HDR10+ films with their dynamic metadata on a Samsung Odyssey OLED G6 from an RTX 4080 SUPER. The player information now shows "HDR10+" and the values sent.
• A bug in NVIDIA's own driver: the InfoFrames it writes on Turing, Ampere and Ada cards, and in driver 580, lost their last byte. HDR10 MaxFALL values of 256 and above were cut, and Kodi's top-and-bottom 3D was signalled as frame packing. Both are fixed, and so is a leftover bit in the InfoFrame that the driver builds for 3D frame packing.
• HDR10 on NVIDIA reaches TVs that declare HDMI 3D (NVIDIA's driver sent the 2016 LG OLEDs no HDR10 at all), and 3840x2160 at 24, 25 and 30 Hz on TVs that take those modes by their HDMI VIC.
• SDR at 8 bits over HDMI on NVIDIA and Intel, as Windows sends it: 2160p60 menus go over TMDS instead of FRL. On NVIDIA, "HDR output depth (NVIDIA)" can hold HDR10 and HLG at 8 bits for TVs with 8-bit panels that band less that way (issue #4).
• New TV modes without a restart: turn on Deep Colour at the TV and Kodi picks up the new modes a few seconds later, while nothing plays.
• Dual-mode DisplayPort ports on NVIDIA laptops (an HDMI socket wired that way): Dolby Vision starts only once the video's mode is on the output, with the link brought up from scratch (issue #4), and Low-Latency is offered there too.

Faster, with the same bytes

Each change below leaves the output identical, checked with the Dolby Vision bridge running in software.

• The vertical passes of the enhancement layer's resampling read 4 rows instead of 5 for luma and 2 instead of 3 for chroma, and hold their results in half floats where that is exact, halving their memory (24.9 to 12.4 MB per 4K FEL picture).
• The planes composed for the transport are 16-bit, and both 4:2:2 rows of each 4:2:0 row come from one shader invocation.
• On NVIDIA, a repeated picture is committed again instead of being redrawn every refresh.
• Dolby Vision shown as HDR10 in a 10-bit window stays at 10 bits, saving GPU memory and bandwidth.
• The windows that open over a video are loaded in advance while the menus are idle, so their first appearance costs no refresh (issue #3).

Smoother on modest graphics

• Frames that keep missing their refresh are presented a frame ahead (issue #4).
• With menus over a profile 7 FEL picture, frames step down on their own while the menus are up, and only on graphics that cannot keep up. Graphics that keep up stay on the exact path.
• The enhancement layer's decoder waits for a free surface instead of restarting the layer.
• On the integrated Radeon of a Ryzen 9 7950X3D, profile 5 with the player information on screen had 26, 8 and 0 late frames per 10 s, against 32, 31, 58 and 6 in 1.0 RC3 with the same video.

Disks, sound and new graphics

• A start from a USB drive keeps every internal disk away. The entries that hide internal disks covered NVMe and AHCI; disks on other internal controllers (SATA in IDE mode, RAID, UFS, virtio, eMMC) were still mounted read-only. They are now let go of before the system starts, and the kernel attaches none until the next start. Card readers, SD cards and USB drives stay.
• You choose which internal disks and partitions are shown (issue #9), in LibreELEC settings > System > Internal disks. An unticked disk is released before anything else runs, with the kernel locked down, so not even a program with full rights can reach it.
• The sound goes to the TV (issue #6): until you pick an audio output, Kodi uses the HDMI output of the display it shows its picture on. An output you pick is never changed.
• Intel Arc B-series and Core Ultra 200V: the firmware of their xe driver is now in the system. Without it they gave no picture.
• libdvdcss reads CPXM DVDs that have no decryption set up, and the diagnostics also replace Bluetooth device names with markers.

Up to date and safer

Linux 7.3, LibreELEC and Kodi 22 "Piers" at their latest commits (68 from Kodi, one of which stops DTS-HD Master Audio from being taken for DTS-HD mid-playback), libplacebo 7.387.0, OpenSSL 4.1.0 and Python 3.14.10. Known security issues are fixed in avahi (17 CVEs), expat, OpenSSL, glibc, BlueZ, BusyBox, FFmpeg and MariaDB Connector/C, and Hades fixes two that upstream has not fixed yet: connman (CVE-2026-115863) and avahi (CVE-2025-59529). Every change, with its technical detail, is in the changelog.

Tested

By the author on 2026-10-28 with this image, on a Ryzen 9 7950X3D PC with a GeForce RTX 4080 SUPER:

• LG C5 TV, on the RTX 4080 SUPER and on the integrated Radeon: native Dolby Vision profiles 7 FEL, 8.1 and 5, HDR10, and Dolby TrueHD with Atmos passed through. On the NVIDIA card, 238 to 242 frames every 10 s at 23.976 Hz with none dropped, and each return from Dolby Vision to the menus in a single mode change.
• Samsung Odyssey OLED G6 monitor (LS27DG600SLXPE) on the RTX 4080 SUPER: HDR10+ films, and a profile 7 FEL film sent as HDR10+.

Results of earlier versions on other hardware (RTX 50, 40 and 30 cards, Radeon RX 7600, Ryzen and Intel integrated graphics; LG, Panasonic, Sony and Samsung TVs) are in the README.

Not tried on hardware yet: driver 580 on GTX 900, GTX 10 and TITAN V cards; Intel xe graphics; zoom, shift and stretch with native Dolby Vision; profiles 8.4 and 8.2; HDR10 on NVIDIA to TVs that declare HDMI 3D, or by HDMI VIC at 24, 25 and 30 Hz; SDR at 8 bits and the 8-bit HDR option; BD-J menus; the automatic audio output; Dolby Vision measured from the HDR10 picture; the HDMI 1.4b signalling; Low-Latency on NVIDIA dual-mode ports; the choice of internal disks and partitions; and a USB start on a PC with disks on controllers other than NVMe and AHCI.

If you have a GTX 900 or GTX 10 card, a 2016 LG OLED, an HDR10+ TV or Intel Arc B graphics, a report in the issues helps most. "Save diagnostics" in the installer keeps the logs, already filtered.

Before you update

• Profile 5 with "Dolby Vision as HDR10 when needed" off is now rebuilt and sent as HDR10 anyway; the setting covers the other profiles only.
• NVIDIA and Intel over HDMI: with SDR at 8 bits, the TV may resync once more when Kodi starts.
• The first Dolby Vision video after the update rebuilds the GPU programs Kodi keeps, since libplacebo changed.
• Certificates with the server name only in the common name (CN) are refused by OpenSSL 4.1, as web browsers refuse them. This affects a MySQL or MariaDB library on a non-local server with a certificate authority set, and HTTPS streams that FFmpeg opens itself (HLS, for example). Certificates from public authorities carry the name where OpenSSL looks for it.

Install or update

• New install: write the .img.gz to a USB drive with LibreELEC-Hades-Installer.exe (Windows) or any disk image writer, and boot from it. The installer can also install to a secondary internal disk without erasing it. Secure Boot must be off.
• Update: use "Update" in the installer, or copy the .tar to the Update folder of a drive with Hades and restart. Settings, add-ons and diagnostics are kept.

Dolby Vision needs an exact HDMI signal: turn off variable refresh rate and the colour adjustments of the graphics driver.

Files

Thanks

To CroqueMr, whose build started Dolby Vision on PCs; to the YBLOD build, some of whose ideas Hades rewrote its own way; to Dom Cobley, cinema-ONE, quietvoid and everyone who reported and tested; and to the LibreELEC and Kodi teams. The README credits each of them for what Hades took.

This is not LibreELEC and it is not official: report problems here, not to LibreELEC or Kodi. There is no warranty.

Español

LibreELEC Hades 1.0 RC4 lleva el Dolby Vision nativo a las GeForce GTX 900 y GTX 10 y a la TITAN V, lo mantiene con el zoom y el estiramiento, envía Dolby Vision como HDR10+ a las pantallas que solo admiten HDR10+ y añade el perfil 8.4 de los iPhone y las teles Dolby Vision de 2016. Funciona sobre Linux 7.3 y cierra una larga lista de fallos de seguridad.

• GeForce GTX 900, GTX 10 y TITAN V: el controlador 615 de NVIDIA no las admite. Hades trae también el controlador 580, con parches propios a su parte abierta, para que Kodi tenga Dolby Vision nativo, Low-Latency, HDR10+ y 3D frame packing. Se elige al arrancar por el identificador PCI de la tarjeta. Nadie lo ha probado todavía en una de ellas. Su módulo del kernel lleva el núcleo cerrado de NVIDIA tal como lo entrega NVIDIA, y la imagen pesa unos 120 MB más.
• Zoom, desplazamiento vertical y estiramiento ya no quitan el Dolby Vision nativo: la parte visible se escala como la escala un reproductor certificado y los metadatos la describen. Un vídeo de 1080p en una pantalla 4K se escala ahora igual y queda más cerca del máster 4K (ΔE ITP medio de 0,349 a 0,266 y de 0,382 a 0,312 en dos imágenes de perfil 5, medido por software).
• Dolby Vision enviado como HDR10+ (nuevo): para pantallas que admiten HDR10+ y no Dolby Vision, como muchas teles Samsung. La película se reconstruye y sale con metadatos HDR10+ que Hades mide de la imagen, escena a escena; son medidas de Hades, no los metadatos del estudio. Apagado por defecto: Enviarlo como HDR10+ donde la pantalla lo admite.
• Más archivos y teles: el perfil 8.4 (el HLG de los iPhone) sale en nativo donde sus metadatos declaran PQ; el 8.2 se compone como dice la especificación; el 5 se reconstruye siempre que no puede ir nativo (issue #2). Las teles de 2016 que piden la señalización HDMI 1.4b la tienen como opción. Un disco con metadatos Dolby Vision planos puede reproducirse con metadatos medidos de su imagen HDR10, para ese vídeo (issue #6). Los menús Java de Blu-ray pueden funcionar con el complemento "JRE for BD-J menus" (issue #1).
• Menos formas de perder el Dolby Vision: un bloque v4.0 que no se puede llevar se descarta en vez de cortar la salida nativa; el controlador de NVIDIA le da a Kodi el EDID entero, también los bloques que añade un HF-EEODB (issue #7); y la salida se repone al despertar de la suspensión.
• HDR10+, HDR10 y la pantalla: HDR10+ visto en un Samsung Odyssey OLED G6 desde una RTX 4080 SUPER. Arreglado un fallo del propio controlador de NVIDIA: sus InfoFrames perdían el último byte, lo que recortaba los MaxFALL de 256 o más y señalaba el 3D arriba y abajo como frame packing. HDR10 en NVIDIA a teles que declaran 3D por HDMI y a 4K a 24, 25 y 30 Hz por VIC. SDR a 8 bits en NVIDIA e Intel, como lo envía Windows, y la opción de HDR a 8 bits en NVIDIA (issue #4). Modos nuevos de la tele sin reiniciar. En los puertos HDMI de doble modo de los portátiles NVIDIA, Dolby Vision empieza con el modo del vídeo ya puesto y el enlace levantado desde cero.
• Más rápido, con los mismos bytes (comprobado con el puente funcionando por software): menos lecturas y coma flotante de 16 bits en el remuestreo de la capa de mejora (de 24,9 a 12,4 MB por imagen FEL 4K), planos compuestos de 16 bits, las dos filas 4:2:2 de cada fila 4:2:0 en una sola invocación del sombreador, imágenes repetidas reenviadas en NVIDIA en vez de redibujadas, Dolby Vision como HDR10 guardado en 10 bits y ventanas sobre el vídeo cargadas de antemano (issue #3).
• Más fluido en gráficas modestas: adelanto de un fotograma donde se pierden refrescos una y otra vez, y reducción automática con menús sobre perfil 7 FEL solo donde la gráfica no llega. En la Radeon integrada de un 7950X3D, el perfil 5 con la información encima pasó de 32, 31, 58 y 6 fotogramas tardíos cada 10 s en RC3 a 26, 8 y 0.
• Discos, sonido y gráficas: un arranque desde USB aparta ahora todos los discos internos, también los de controladoras SATA en modo IDE, RAID, UFS, virtio y eMMC, que antes se montaban en solo lectura. Tú eliges qué discos y particiones internas se muestran (issue #9). El sonido va a la tele mientras no elijas una salida (issue #6). Las gráficas Intel Arc B y Core Ultra 200V tienen el firmware de xe sin el que no daban imagen.
• Al día y más seguro: Linux 7.3, LibreELEC y Kodi 22 "Piers", libplacebo 7.387.0, OpenSSL 4.1.0 y Python 3.14.10. Arreglos de seguridad en avahi (17 CVE), expat, OpenSSL, glibc, BlueZ, BusyBox, FFmpeg y MariaDB Connector/C, y dos que Hades arregla antes que su proyecto original: connman (CVE-2026-115863) y avahi (CVE-2025-59529). Todo, en el registro de cambios.

Probado por el autor el 2026-10-28 con esta imagen, en un Ryzen 9 7950X3D con una RTX 4080 SUPER. Con una LG C5, en la RTX y en la Radeon integrada: Dolby Vision nativo de perfiles 7 FEL, 8.1 y 5, HDR10 y TrueHD con Atmos; en la NVIDIA, de 238 a 242 fotogramas cada 10 s a 23,976 Hz sin perder ninguno. Con un monitor Samsung Odyssey OLED G6 en la RTX: HDR10+ y una película de perfil 7 FEL enviada como HDR10+.

Sin probar todavía: el controlador 580 en GTX 900, GTX 10 y TITAN V; las gráficas Intel con xe; el zoom con Dolby Vision nativo; los perfiles 8.4 y 8.2; HDR10 en NVIDIA a teles con 3D por HDMI o por VIC; SDR a 8 bits y la opción de HDR a 8 bits; los menús BD-J; la salida de audio automática; Dolby Vision medido de la imagen HDR10; la señalización HDMI 1.4b; Low-Latency en los puertos de doble modo de NVIDIA; la elección de discos y particiones; y el arranque desde USB en un PC con discos en controladoras que no son NVMe ni AHCI. La tabla entera está en el README.

Antes de actualizar: el perfil 5 se reconstruye ahora aunque "Dolby Vision como HDR10 cuando hace falta" esté apagado; en NVIDIA e Intel por HDMI la tele puede resincronizar una vez más al arrancar Kodi; el primer vídeo Dolby Vision vuelve a preparar los programas de GPU; y OpenSSL 4.1 rechaza los certificados que solo llevan el nombre del servidor en el CN.

Instalar o actualizar: escribe la imagen .img.gz en una unidad USB con LibreELEC-Hades-Installer.exe o con cualquier programa de imágenes de disco y arranca desde ella; Secure Boot tiene que estar apagado. Para actualizar, usa "Actualizar" en el instalador o copia el .tar en la carpeta Update y reinicia; se conservan los ajustes, los complementos y el diagnóstico.

Esto no es LibreELEC ni es oficial: informa de los problemas aquí, no a LibreELEC ni a Kodi. No hay ninguna garantía.