LibreELEC Hades 1.1
New things to see and to choose, and fixes for what was reported after 1.0. The player information is redesigned and a remote reaches its button: O, then OK, changes how a Dolby Vision video goes out while it plays. Any HDR film can be watched as SDR. On a TV with variable refresh rate, a video can start without the screen going black. Upscalers rebuild the detail of videos smaller than the screen, HDR10 can be mapped scene by scene for a projector, and SDR videos made in BT.2020 can keep their wide colours. The start is one picture from the boot menu to the interface, Dolby Vision goes through the USB-C hub of a Chromebook, and on a PC with Windows, Hades and Windows restart into each other without the boot menu key, and a PC that keeps Secure Boot on can start Hades with it, as an option of the installer. It also brings Linux 7.3.5, the latest commits of Kodi 22 and the security fixes of their libraries.
Every change was tested on the host, with the code that the image runs, or in a virtual machine, and on my PC where it has the hardware. The README says what has been seen on which hardware, and what still waits for hardware I do not have. If you try it, please say what you see in the forum thread or the issues.
What's new
The player information
- Redesigned, in one frame: the path of the signal at the top (the film, Hades, your TV), every page the same height, a bar at the bottom with the processor, the graphics, the memory, dropped and skipped pictures and the button for the output; the System page now says how the TV is connected and gives the versions of Hades, the graphics driver and the kernel.
- "Output of this video" works with a remote, a keyboard and Yatse: Down goes to the button, and O, then OK, opens the choice of output at once.
- As SDR, for one film: any HDR video, Dolby Vision included, can go out as SDR from its output choice, and HLG videos get the choice too.
- It opens at once on the first press, and Kodi's own short panel can come first (Advanced).
- The speakers of the Audio page no longer stay "not known" when the sound output is set up again as a video starts, and the Video page has a button for the upscaler of the videos like the one that plays.
Picture
- HDR on a display without HDR is mapped again, as the settings say: a new profile, and every profile of 1.0, had Kodi's tone mapping "Off", which left HDR washed out on an SDR display or projector.
- The menus, the on-screen controls and the subtitles over HDR keep the shadows they have in SDR (the curve of BT.1886, as ITU-R BT.2408 says; Kodi's curve stays in Expert).
- Keep the wide colours of SDR videos (BT.2020) (Advanced, off), with the menus and subtitles converted to match; and the ordinary conversion to BT.709 keeps its greys and its black.
- Upscalers (Expert, off): RAVU, FSRCNNX 8 and FSRCNNX 16 for videos drawn larger than they are, with a choice for animation; measured closer to the original than Kodi's Lanczos 3 by up to 1.3, 3.4 and 4.7 dB.
- HDR10 mapped scene by scene (Expert, off), for projectors and SDR output.
- Video at its own rate with VRR (Expert, off by default): an SDR or HDR10 video, and on the RTX 40 and RTX 50 series HDR10+ and Dolby Vision sent as HDR10, HDR10+ or SDR, plays in the mode of the menus, each picture at its time. Always does it on any display with VRR, so the screen does not go black when a video starts or stops; Where the display has no mode at the video's rate does it only there, for a monitor without a mode of 24, 48 or 72 Hz, whose films otherwise go out at 120 or 360 Hz with a picture held now and then. Hades checks in the first second that VRR came on (on NVIDIA, as the driver says and by when each picture reached the output), and the player information gives the rate that the display gets, measured (a film of 23.976 fps at 47.952 Hz on an LG C5, at 71.928 Hz on a monitor whose VRR starts at 48 Hz). Native Dolby Vision changes the mode as always.
- A film at its own rate on a TV whose menus are in another resolution: without a whitelist of your own, a 1080p film on a TV with its menus at 2560x1440 gets the TV's 3840x2160 at 23.976 Hz, not 120 Hz; and each display keeps the resolution of its menus.
- Adjust display resolution (Player > Videos, off): a video goes out in a mode of its own size at the rate Kodi chooses for it, so the TV scales a 1080p film; with Video at its own rate with VRR on too, it takes the mode of its size with VRR in it; native Dolby Vision stays at 3840x2160.
- A monitor slow to wake as the PC starts gets its fastest modes (360 Hz) without restarting Kodi, and the menus are no longer shown huge and cut for a few seconds at the start next to other lit displays.
- HEVC videos whose parameters say their pictures may be fields, and whose pictures are whole, are shown as progressive: 25p gets 25 Hz, and the whole-number multiples and VRR take them. Hades reads the timing of their first pictures only where it can change the mode.
- HDMI variable refresh rate is off by default on NVIDIA, as on AMD and Intel graphics: some TVs switch to their game mode while it is on. It can be turned on in Expert, and a change of it applies at once.
- Zoom to the active area of Dolby Vision videos (Expert, off), for 2.35:1 and 2.39:1 screens: each scene enlarged to its picture, following films with IMAX scenes, without cutting any of it. The player information says what it does.
Dolby Vision
- HDMI variable refresh rate is left off during native Dolby Vision on every NVIDIA card, RTX 40 and RTX 50 included.
- No active area (level 5) that the video does not have.
- Low-Latency that cannot use the display's values falls back to Standard, or to HDR10 with the enhancement layer (issue #25); colours past BT.2020 (laser projectors) are taken to its edge; and the black that the display gives is used.
- Frames ahead for a graphics card held to a low power limit (issue #4).
- Dolby Vision through the converter of a USB-C hub or adapter (Expert), and no Dolby Vision through a passive adaptor that says DVI, on NVIDIA too.
- Radeon RX 400, RX 500 and Vega: the path without the formatter's expansion, and Check the Dolby Vision output now says where the bytes change; where a card changes them, Hades does not use the path, nor HDR in 4:2:2 at 12 bits (issue #20).
- Low-Latency with the interface over the picture costs the graphics less, with the same bytes.
- An HD video with Dolby Vision metadata of its own gets its whole black bars sent to the TV (level 5), once its pictures show which reading is right; 4K videos are byte for byte as before.
- A profile 8.1 video that also carries HDR10+ keeps its own HDR10+ on a display without Dolby Vision; an RPU without its last byte keeps its metadata where its checksum holds.
- Profile 7 with an enhancement layer that starts late no longer starts the layer over every 64 pictures while it waits.
Sound
- Sound on a display that takes PCM of 16 or 20 bits only (issue #23).
- Intel Alder Lake (N97 and N100 too): HDMI sound no longer goes silent after Dolby Vision with a passthrough track; and the TV no longer drops out of the list of outputs.
- An output kept on keeps its sound, and CEC through an output without the picture leaves the TV's input alone (issue #24).
- CEC turned off takes the PC off the bus at once, and adapters that come back are found again.
- Dolby Digital at 32 kHz passed through, and 6.1 and 6.0 tracks keep their back centre.
- Surround sound through a USB-C adapter or hub (Expert, off).
Streams, discs and files
- Blu-ray images that an add-on streams play as discs even without
.isoin the address; servers of one connection no longer stall each seek; expired addresses are asked again; disc images on the internet open faster. - A change of subtitle track shows at once, and an embedded subtitle changes without interrupting playback.
- The variety of a language: Castilian or Latin American Spanish, European or Brazilian Portuguese, French from France or Canada, simplified or traditional Chinese.
- A video no longer starts behind its clock, and a seek in a file without sound or video no longer waits a second.
- A Blu-ray menu page takes the range of an HDR playlist; three fixes of libbluray; Kodi's latest fixes for ASS subtitles, the guide, add-on demuxers, the information dialog, scripts that kept Kodi from exiting and a stop during a change of refresh rate.
- Subtitles can be moved by a fixed step, for remotes that send single presses.
- Add-ons of LibreELEC's repository get their settings again.
The start and the system
- One picture from the boot menu to the interface on a UEFI PC, and a notice on the screen when Kodi cannot start.
- The hardware clock is read as it was measured to keep: local time or UTC, never written (issue #22).
- Kodi starts sooner where an earlier start found the clock of the PC right: it waits for the network, not for the time from the internet. The diagnostics time the network at the start.
- 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, for the black screen that happened now and then.
- NVIDIA with two or three displays: a change of mode waits three seconds at most, not three for each display.
- Intel and AV receivers: the link set up again once the receiver is ready, and an option for the empty HDMI vendor InfoFrame (issue #28).
- AMD through a passive DP++ adaptor: SDR at 8 bits, and the reason when a 3D display gets no 3D mode (issue #26).
- Chromebooks with Intel graphics: the drivers that give their USB-C port a picture.
- With Windows on the PC: Restart into Windows in the power menu, Restart into LibreELEC Hades, a button of the installer next to a drive with Hades and on its last screen (and a shortcut on the desktop if you tick its box), and Restart LibreELEC Hades, which comes back to Hades even where Windows comes first. Each only sets the next start, once; no boot entry is added, removed or moved. The power menu names its restarts by what they do (Restart the interface restarts only Kodi), and the installer also removes Hades from a USB drive.
- Wi-Fi and Bluetooth firmware for more MediaTek and Qualcomm adapters, and a MediaTek Bluetooth controller without its firmware no longer resets over and over.
- The diagnostics name the driver where a start stops, and keep the kernel's log of a start that hangs before its journal is saved (issue #14).
- A PC whose HPET timer stops (an AMD FX on a 970 board, issue #22) keeps its good clock instead of slowing down and hanging.
- A TV on NVIDIA that comes back without locking to the signal gets the output set up again once (issue #24).
- OpenSSL, Python and Samba built with the compiler's protections.
- Secure Boot, optional and off by default: for a PC that keeps it on, the installer makes a key for that PC alone and signs Hades with it; the PC asks once to enroll it, and the kernel locks itself down. The PC's Secure Boot keys, its boot order and Windows are never touched.
Up to date: Linux 7.3.5, Kodi 22 up to 51b30cf19be9, LibreELEC master up to 3a98afddff5b, glibc, OpenSSL 4.1 and 3.5, BusyBox, FFmpeg (its stable branch and 73 fixes from its development branch), libplacebo, libbluray and dav1d with their security fixes.
The changelog has every change, with its details.
Downloads
LibreELEC-Generic.x86_64-13.0-devel-20261119185838-79f9fb5.img.gz: the image, for a USB drive or a disk. SHA-256a88f42a69cc19205b3962501e9d3f4cb1bf29d658045448d72ca6c2d60c61593LibreELEC-Generic.x86_64-13.0-devel-20261119185838-79f9fb5.tar: for updating a system that runs Hades. SHA-25647f780174c89b4c8d5997ef4139511e3a8ad98ae0c49d3b5c91d4dfd469d40efLibreELEC-Hades-Installer.exe: the Windows installer, which writes, updates and checks the drive. SHA-2565a7a46d2faa41889f809b4fcd950991120a4f5823e4867f6c459c4813d89041f. It is built from the source in tools/hades-installer and is not signed, so Windows may ask whether to run it.- The installer on VirusTotal: 2 of 71 engines flag it, both by heuristics: SecureAge, and Trapmine with a low machine-learning score. The other 69 find nothing. The installer writes whole drives and sets the next start of the PC, which such engines can read as suspicious; both are false positives.
LibreELEC-Hades-1.1-sources.tarandLibreELEC-Hades-1.1-firmware-and-nvidia.tar, withsources-manifest.tsv,sources-SHA256SUMSandREADME-sources.md: the sources of everything in the image. With the repository at this tag they are its complete source;README-sources.mdsays how to build with them.SHA256SUMS: the SHA-256 of every file of this release. Check a download withsha256sum -c SHA256SUMS(Linux) orGet-FileHash(Windows).
How to install and update: README.
Thanks
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 Bin Jin's RAVU and igv's FSRCNNX, shipped unchanged. And thank you to everyone who tried 1.0 and said what they saw, among them wright96d, harment, NTM-3D, SeaMonkey82, SunnySnacks, Khazar321, sat4all1-dev, ht2tweak, astrotrain, louyeh, MrMagic and testmest.