hadesdevls/LibreELEC-Hades v1.0

LibreELEC Hades 1.0

on GitHub

LibreELEC Hades is an unofficial build of LibreELEC for 64-bit PCs (the "Generic x86_64" image). LibreELEC turns a PC into a media centre that runs Kodi and little else. Hades adds what a home cinema asks of it: Dolby Vision sent from the PC to the TV over HDMI in the TV-led way that Dolby Vision players use, including profile 7 with its full enhancement layer, HDR10+, and Dolby Atmos and the other HD sound formats passed to your receiver untouched. Everything else that LibreELEC does is kept.

LibreELEC Hades 1.0 is the first version that is not a release candidate. Native Dolby Vision, including profile 7 with its full enhancement layer, has been seen working on NVIDIA, AMD and Intel graphics, with Dolby Atmos passed through. This version makes Hades easier to set up and to understand: a check of your setup that plays test pictures and sounds and says in plain words what reached the TV, a diagnostic report made with one button, and a player information page that says in one sentence whether a video plays as intended. It fixes what was reported after 1.0 RC8, keeps picture and sound in step, sends Dolby Vision as the composer makes it by default, maps HDR to displays more faithfully, plays DVD films as films, keeps a stream going through a network drop, and brings every part up to date.

These notes start with what Hades is and what you need, for anyone who comes to it for the first time, then list everything that is new since 1.0 RC8. Every change, with the reason for it, is in the changelog. The documentation is rewritten for readers: the README, the extras of Hades, the settings guide and how it works.

What LibreELEC Hades does

• Native Dolby Vision over HDMI. Each picture is rebuilt as the Dolby Vision specification defines it, including the full enhancement layer (FEL) of profile 7, and sent with its metadata for every frame; the TV does its own Dolby Vision processing, as with a certified player. Profiles 5, 7 (FEL and MEL) and 8.1.
• NVIDIA, AMD and Intel graphics, graphics cards and integrated graphics alike (NVIDIA with its open kernel modules, and the GeForce GTX 900 and GTX 10 cards and the TITAN V with NVIDIA's driver 580).
• A safe fallback. Dolby Vision is used only when the video, the TV, the HDMI link and the graphics driver all qualify. Otherwise the video plays the ordinary way, as HDR10 or SDR, and the first page of the player information says why in one sentence.
• A player information page that a person can read, and a check of your setup that says what reached your TV (both new in 1.0, below).
• The refresh rate Kodi would choose, exact for progressive video (25 fps at 25 Hz, 29.97 fps at 29.97 Hz). On NVIDIA, the modes at exactly 24, 30, 60 and 120 Hz that the driver did not offer are added. DVD films stored as interlaced video are put back together picture by picture and shown at their own rate.
• Picture and sound in step: each frame is shown when its sound plays, measured on your display, and passthrough sound (TrueHD, Dolby Digital Plus, DTS) is kept through a pause.
• Made for integrated graphics too. A frame that takes most of a refresh period is prepared one refresh ahead, and the picture under menus and subtitles is redrawn only where they are.
• HDR10+ with the dynamic metadata of each frame, where the graphics driver can send it, and HDR sent more exactly: YCbCr 4:2:2 at 12 bits where the ordinary output would send HDR in RGB at 8 bits or in 4:2:0.
• Zoom, vertical shift and stretching keep native Dolby Vision.
• Dolby Vision shown as HDR10 where native output is not possible, and HDR mapped to SDR with the reference method of ITU-R BT.2390 on a display without HDR.
• Options for every kind of display, off by default: Dolby Vision for TVs in game mode (Low-Latency); the older HDMI 1.4b signalling for the TVs of 2016 that ask for it; HDR10+ or HDR10 sent as Dolby Vision, and Dolby Vision sent as HDR10+; HLG sent as Dolby Vision; settings for projectors.
• 3D Blu-ray video (H.264 MVC): both views are decoded, and a 3D display is switched to 3D over HDMI.
• Blu-ray Java (BD-J) menus with nothing to install, in a service of the system kept apart from Kodi, with no network unless BD-Live is turned on, and then the Internet only.
• PCs with two graphics chips, and laptops: Kodi starts on the TV, whichever chip it is connected to, and moves to a TV connected later.
• Streams that keep going: a network or a streaming service that stops sending for a while no longer ends the film.
• Safer defaults for a PC that also holds your other disks and your Windows: started from USB, the internal disks are hidden; Samba is off until you turn it on, and then has a password; SSH is off; the firewall starts in "home" mode; Hades does not contact LibreELEC's update server, because an official LibreELEC update would remove Dolby Vision. Nothing from LibreELEC is removed, and each of these can be turned back on.
• A Windows installer that writes a USB drive, installs to a secondary internal disk without erasing it, updates and removes.

What you need

• A 64-bit PC with Secure Boot turned off.
• A USB drive of 8 GB or more. A USB SSD runs much more smoothly than a stick.
• For Dolby Vision, a TV that offers Dolby Vision "Standard" on the HDMI input you use (on an LG C5, "Quick Frame Transport" has to be off on that input), supported graphics, and the PC connected by HDMI straight to the TV, or through a sound bar or AV receiver that passes Dolby Vision through. The supported graphics are NVIDIA GeForce GTX 16, RTX 20 or newer (with driver 580, the GeForce GTX 900 and GTX 10 cards and the TITAN V), AMD Radeon graphics with display hardware DCN 1.0 or newer and the Radeon RX 400, RX 500 and Vega cards, and Intel graphics of display version 9 or newer (UHD 6xx and later). The README has the details.
• Your own videos or add-ons: Hades comes with no films, add-ons or media sources.

What's new in 1.0

Easier to set up and to understand

• Check this setup (Settings > LibreELEC > System > Check this setup). It plays short test clips that the build makes itself: a test picture in SDR, HDR10, HLG and Dolby Vision (profiles 8.1 and 5), a soft noise from each speaker in turn, and a chime in Dolby Digital, Dolby Digital Plus and Dolby TrueHD. After each one it says what went out and how, asks what you saw or heard, says what to do if something was wrong, and switches on only the sound formats that you heard; DTS cannot be checked this way and is left as it is.
• A player information page that a person can read. Press O, or the red key of a TV remote that sends keys over HDMI-CEC: the first page says in one sentence whether the video plays as intended and, if not, what is wrong and what to do, then what the file carries, what Hades does with it and what reaches your TV. The details are behind it, with every level of the Dolby Vision metadata, the pictures dropped and skipped, and the decoder in use; the same pages are made for other skins.
• The settings are in groups, with help in plain words. System > Display has four groups with a heading each, most of the settings that Hades adds are now at the Expert level, and their help says what changes on the screen or in the sound, when to want it and what to do if the picture goes wrong.
• Samba tells you how to get in. Turning Samba on shows a window with the address, the user (libreelec) and the generated password, how to open the share from File Explorer, and that the same login copies an update file to the Update share.
• A notice of the playback mode, off by default. System > Display > Show the playback mode when a video starts says what each video plays as, for example "Dolby Vision, FEL, 3840x2160 at 23.976 Hz".
• "Restart LibreELEC Hades" in the power menu, so restarting the application no longer means restarting the PC.
• Clearer wording where Dolby Vision is not sent. The notice about Low-Latency no longer blames the game mode, since some displays offer Dolby Vision only that way whatever the input, and a TV behind a DisplayPort or USB-C converter is told to use an HDMI output of the graphics instead.

Dolby Vision

• Sent as composed by default. Native Dolby Vision of profiles 7 and 8 now goes to the TV as the composer of the specification makes it, in the video's own YCbCr, bit for bit; measured on pictures of two profile 7 films and on test patterns, it was as close to the film as IPT-PQ-c2 or closer. IPT-PQ-c2 stays as an expert choice (Transport, "As licensed players send (IPT)").
• Films whose metadata repeat a pivot play in Dolby Vision. The picture check refused metadata that the specification allows, so such a film dropped to HDR10 after two seconds; this is the cause of the Transformers films dropping to HDR10 in the reports.
• The TV's Dolby Vision block is no longer lost on its way from the TV. On NVIDIA, an EDID whose extra blocks are counted by an HDMI Forum EEODB now reaches Kodi whole, and on AMD and Intel one damaged block no longer takes the others with it; the player information tells a TV input without Dolby Vision from an EDID read in part (issue #7).
• Native Dolby Vision on the newest Ryzen processors (display hardware DCN 4.2 and 4.2B). Each time Dolby Vision starts, the kernel reads the display pipe back from the hardware, and if anything is not as Dolby Vision needs, the same video goes on as HDR10 within about two seconds; the same now holds for the Radeon RX 400, RX 500 and Vega cards.
• Dolby Vision through a passive DisplayPort adaptor (DP++) that identifies itself as HDMI, on Intel and AMD graphics, within the adaptor's own limit (type 1: 1080p; type 2: up to 3840x2160 at 30 Hz).
• The output is given back as it was found, and checked. When native Dolby Vision ends, Hades puts back each property of the output that it changed, reads the output back and sets again what did not take, with the range and colour format that the settings ask for at that moment.
• The Dolby Vision path of the Radeon RX 400 and 500 (Polaris) and Vega cards is off unless you turn it on (issue #20: an RX 550 with an LG G3 showed a black picture with the Dolby Vision logo). Turn on System > Display > Dolby Vision on this Radeon (experimental), shown only on those cards; without it, Dolby Vision plays as HDR10 there.
• HLG sent as Dolby Vision (System > Display > HLG as Dolby Vision). Automatic by default, only where the output cannot send HLG at all but the display takes Dolby Vision, so that the video keeps its HDR; On sends it wherever the display takes Dolby Vision.
• Videos with Dolby Vision and HDR10+ in two video streams play the stream that Videos with both Dolby Vision and HDR10+ chooses, and on a display that takes only one of them, that one.
• Dolby Vision pictures up to 4096x2304 are taken in and scaled down to the 3840x2160 output.
• The menus in Dolby Vision cannot lock you out (issue #20). Turning on Dolby Vision for the menus asks you to confirm, with a 15-second countdown whose default is No.
• Dolby Vision through the DisplayPort-to-HDMI converter of a board (Dolby Vision through a display converter, Expert), for the HDMI socket of many mini PCs and NUCs with Intel graphics of the 11th generation and later. Automatic offers it only on the boards where it was seen working (one today).
• With NVIDIA's driver 620, Dolby Vision always goes out at 8 bits in RGB, whatever another program or Colour format left in the driver's own settings, which are put back after.
• The trims of Dolby Vision where Hades maps the picture, as an expert choice, off by default. Measured against a studio's own version of a film, the only published way to apply them made the shadows much darker than the studio did, so it stays off; native Dolby Vision is not affected.
• The peak of the TV by hand for the automatic tone mapping (v4.0) (Expert), for a TV that declares a wrong peak in its EDID.
• A failure of native output no longer takes Dolby Vision out of the supported HDR types that add-ons are told about (forum post 209039).
• Smaller things: the log says which rule kept a frame from being drawn; what the conversion of a video engaged is released when the video ends; and the file of GPU programs no longer depends on the version of the system, so an update no longer makes the first video compile them all again.

HDR and the signal to the TV

• HDR on a display without HDR keeps its middle tones as mastered. "Reference (BT.2390)" now starts compressing where ITU-R BT.2390 says: on the reference SDR display, 100 nits of a film mastered at 1000 nits now go out at 99 instead of 87. The same fix applies to the mappings to an HDR10 display and to Dolby Vision Low-Latency, and the old look stays available as "BT.2390, libplacebo's knee".
• HDR10+ adapted by its own metadata. Where Hades adapts an HDR10+ video to the display itself, it now follows the HDR10+ data of each scene, and the studio's tone curve where the video carries one.
• Play HDR videos as SDR (System > Display, Expert, Never by default), for a TV that shows HLG badly or a projector whose SDR picture is better; Dolby Vision videos are not affected. The display is now also told the colours that the picture is drawn in.
• HDR to SDR for the display you have: Reference, Bright room, Projector and Custom (a white of 20 to 500 cd/m² and a gamma of 1.8 to 2.8); HLG mapped to a brighter SDR display no longer comes out about half as bright in the middle tones.
• The black of the display (Expert): for projectors, the darkest parts of the film are lifted as ITU-R BT.2390 describes, so that they do not sink into the black of the projector.
• HDR in 4:2:2 at 12 bits over HDMI 2.0 on Intel and AMD graphics (on by default). At 3840x2160 and 50 or 60 Hz, HDR10, HLG and HDR10+ now go out as YCbCr 4:2:2 at 12 bits inside the signal that carries Dolby Vision, where the TV takes it, so the video goes out exactly and the menus and subtitles over it keep twice the colour detail; such a video starts with one more change of mode of the TV.
• HDR above 8 bits on NVIDIA where the card would send RGB at 8, now on by default (issues #4 and #17). HDR goes out as YCbCr 4:2:2 at 12 bits (10 on the GeForce GTX 10 cards and the TITAN V) at the same link speed, and goes back to 8 bits by itself if the TV does not lock onto it. At 10 bits it was seen working on a GeForce GTX 1060 with an LG OLED65C8 (issue #17).
• HDMI variable refresh rate is left off during native Dolby Vision on NVIDIA GeForce GTX 16, RTX 20 and RTX 30 graphics (issue #4).
• What another program left on the output is put back (LibreELEC forum thread 30675): after a Flatpak app with its own Wayland session, HDR10 no longer comes out as RGB at 8 bits.
• Colour format and maximum bit depth (System > Display, Expert, Automatic by default).
• HDR over HDMI on Intel HD and UHD 6xx graphics, as an expert choice, shown only on that graphics, where HDR10 and HLG went to a TV without Dolby Vision as SDR. Off by default.
• HDR10 whose mastering display is written in two ways no longer stutters or makes native Dolby Vision end and begin again in the middle of a video.
• A video whose container calls it SDR but whose stream says HLG or PQ is taken as HDR from the start.
• The check of which video the graphics can show follows the layout of each picture, so Kodi on Intel and AMD graphics is no longer left without its hardware renderer of video, or without 10-bit video in it.

Displays

• A display connected while Hades runs is taken without a restart on the same graphics card: the menu stays where you were and music keeps playing. A display on another graphics card still needs a restart.
• Only the display in use is lit, and the sound stays with it. With several displays on one graphics card, only the display that shows the picture is lit, and the sound goes to its own audio output (and from there to a sound bar or receiver on its eARC); the audio output is remembered by its display, not by its number.
• Monitors on the same graphics card as the TV are no longer left on with a black picture where Hades is not sure which output carries the sound.
• Each output is matched with its own display, so the TV is no longer taken for a monitor with three displays on an NVIDIA card.
• Hades waits for the NVIDIA driver before it starts, 20 seconds at most and not at all on a PC without an NVIDIA card, so it no longer starts on no output, or on other graphics, after an installation.
• A frame that the graphics driver refuses no longer leaves a half-drawn picture.
• Intel HDMI: the check of a TV after it drops its signal for a moment is no longer lost.
• Intel Panther Lake and Wildcat Lake: the fallback for reading the EDID works, with five fixes by Ville Syrjälä from the development tree of Intel's graphics.
• HDMI-CEC over a DisplayPort connector, and HDMI-CEC of SECO boards (UDOO x86 and the like).
• The kernel log says each InfoFrame of i915 and each packet of amdgpu that goes out, when it changes.
• NVIDIA driver 620.70.06, with 580.196.07 kept for the GeForce GTX 900 and GTX 10 cards and the TITAN V; with driver 580, HDR of more than 8 bits is flipped on the graphics chip where the plane cannot reflect it (issue #17).

Picture and sound in step

• Picture in step with its sound (Settings > Player > Videos, on). On every driver the picture left the PC one refresh before its sound (42 ms at 24 Hz, 17 ms at 60 Hz); Hades now measures when each frame really reaches the screen and shows it with its sound. If you had set Audio offset to make up for this, set it back to 0.
• A pause keeps passthrough sound (Dolby TrueHD, Dolby Digital Plus, Dolby Digital, DTS): the sound goes on where it stopped, in sync, and while paused the receiver stays on the stream.
• TrueHD comes back sooner after a start or a seek (at about 320 ms instead of 680 ms), and its corrections end where they should.
• DTS-HD and TrueHD passthrough that could fail or crash. A DTS-HD Master Audio stream at its peak bit rate no longer crashes Kodi, and four more faults of DTS and TrueHD passthrough are fixed; two are fixes still under review for Kodi, by tanio99 (for OSMC) and by heit88, taken with their authors.
• The sound output is closed without playing out its own silence when a video starts and the format changes, and a resampler that cannot be set up no longer crashes Kodi.

Performance

• A lighter interface during native Dolby Vision, HDR10 and HLG. Where no control changed, the interface of the frame before is put over the picture, only where the interface is; the same bytes go to the display.
• Dolby Vision made from HDR10, HDR10+ and profile 8.1 takes about a third less GPU time, with the same bytes: an HDR10+ picture sent as Dolby Vision took 35.0 ms instead of 53.5 on a software renderer.
• Dolby Vision packing takes less GPU time while the interface is over the picture, with the same bytes: 14 to 28 % less with zink and 6 to 11 % less with llvmpipe, measured on the host.
• No pause where a video mapped to the display starts: the colour table that the mapping needs is made ahead, on a thread of its own.
• Frames ahead within seconds where a graphics chip cannot keep up at all (a GT 1030 with a profile 7 film).
• Less memory for the HEVC decoder, meant for graphics cards with 2 GB, and a fix for nvidia-vaapi-driver when a surface of the enhancement layer is taken again.
• Smaller things: a video paused in its last seconds no longer keeps a processor core busy (71 % of a core before, 2.3 % now); the debug information on screen no longer redraws the interface over HDR; thumbnails of HDR videos take 98 MB at most instead of 163 MB.

DVD, Blu-ray, 3D and subtitles

• Films on DVD and in interlaced video play as the film (Settings > Player > Videos > Rebuild films from interlaced video, on). Where Hades is sure that a DVD title or an MPEG-2 file holds a film, each picture is put back together from its own fields and the film plays at its own rate (23.976, 25 or 29.97 Hz); real interlaced video and anything Hades is not sure of play as before.
• Films with soft telecine play at 23.976 Hz, each picture once, from files, DVD images (ISO) and VIDEO_TS folders.
• Blu-ray: the audio or subtitle stream that you choose is the one that plays, with and without the disc's menus, and the subtitles chosen in a menu are on when the film starts (issue #1).
• Blu-ray: a play item that starts between key pictures plays from its first picture, with its Dolby Vision enhancement layer, also after a jump or a seek.
• Blu-ray: chapter marks, joins and subtitles around a jump, with two fixes by matthane taken from Kodi's master with their author.
• Blu-ray menus of an Ultra HD disc whose film is HDR10 or Dolby Vision are drawn as the disc made them, no longer grey and washed out, and Java menus that animate are shown while they move.
• Blu-ray: VC-1 at its own rate, no longer opened at twice its frame rate.
• A disc image over the network opens with its menu, and faster: in 6.7 s instead of 13.0 at 100 ms of network latency, in a virtual machine.
• A seek step is no longer lost when it is pressed while the picture of the step before is still coming.
• Picture subtitles show with their own frame, and two new settings in Settings > Player > Subtitles make their colours paler (Bitmap subtitle saturation) and tell subtitles made for SDR in an HDR video (Bitmap subtitles made for).
• 3D: side by side at 1080p for a 3D display that takes it without listing it; 3D over a passive DisplayPort adaptor (DP++) on AMD and NVIDIA graphics; black lines between the two eyes of frame packing; and the second view of a 3D Blu-ray after a picture that empties the decoder.
• A Matroska seek starts at the earliest key frame of the video tracks, so that Dolby Vision in two video tracks keeps its enhancement layer after a seek.

Streaming, network and the library

• Streaming: a connection that drops no longer ends the film. Hades buffers with the picture and the clock paused together, says "Connection interrupted" after 5 seconds, reconnects and plays on from where it stopped, in sync; after 5 minutes without data, or when the server refuses the link, playback stops with an error and keeps its position.
• A video asked for while another is still opening no longer waits for it, and is no longer lost when the first one fails to open (issue #21).
• A file that stops answering no longer freezes the interface (issue #21: a long wait when opening a film on an NTFS disk, and a film that stopped after two minutes, caused by the new ntfs driver of Linux 7.3, fixed below).
• A folder that cannot be read to its end is reported, not listed short.
• The library knows the Dolby Vision profile and the HDR of what you play, also of a .strm, a disc or a stream: when a video ends, what its playback found goes into its library details, and profile 7 is stored as "7FEL" or "7MEL".
• Nameservers of your own, also with DHCP (Settings > LibreELEC > Connections).
• JSON-RPC serves each connection on its own (Kodi's change by Martin Ellis, with a test by Garrett Brown), so a dialog that one request opens no longer holds up every other remote control app, with five fixes of Hades to that server.
• Samba shares a drive whose label holds %, a backslash or brackets under a safe name.
• For add-ons and skins: Player.Process(video.sidedata) gives the Dolby Vision and HDR payloads of the picture on screen in the format that the CoreELEC builds use, and videooutputhdrtype and the new videooutputeotf say what the graphics driver holds; an animated image plays from its first frame each time it shows; and Window(Home).Property(MousePointerStays) keeps the pointer on screen.

Sound and hardware

• Keeping an NVIDIA card at full speed while HD audio plays through it (Advanced, off by default, issue #8), for the laptop whose TrueHD or DTS-HD sound cut out every few seconds on its charger.
• HDMI-CEC: the keys of the remote work sooner after a start where an amplifier answers slowly, and seven faults of libCEC that could crash Kodi are fixed.
• Infrared remotes that need a decoder of their own get decoders compiled from source in place of objects compiled in 2021; your keymaps and decoders work as before.
• A disk in a USB enclosure is stopped when the system powers off, with its heads parked.
• Ryzen PCs that only sleep to idle reach their deepest sleep; the ALSA loopback card, for a room-correction program such as CamillaDSP; and btproxy, which gives a virtual machine the Bluetooth controller of its host.
• The fast side of an external USB hub may sleep when nothing is on it, and the kernel log says the PCIe link at each stream DMA error of the HD audio core.

System, diagnostics and safety

• A diagnostic report in one file (Settings > LibreELEC > System > Submit Log > Create a diagnostic report). One button makes one zip file with the logs, the graphics and displays, the sound, the network, the USB devices and the journals of this start and the one before; every file goes through the filter of the diagnostics first, nothing is sent anywhere, and it can be copied to a USB drive.
• The diagnostic switch is a setting (Settings > LibreELEC > System > Submit Log > Save diagnostics at every start), on a USB drive and on an internal disk alike.
• Check the Dolby Vision output (Settings > LibreELEC > System > Submit Log): a button that measures, with the card's own check of what leaves it, whether AMD and Intel graphics send the pictures of Dolby Vision exactly as Hades draws them, and says the result in plain words.
• The diagnostics filter more of what is personal (serial numbers of volumes and devices, labels, names of networks, the name of the system), record the video memory of AMD cards too, and keep a start of the Installer entry, so that an installer that hangs leaves a record.
• The share Logfiles gives the log through the filter.
• Devices reach only their own memory in the normal start. Run and Live now start the kernel with DMA translation, so where the PC has an IOMMU a device whose firmware was replaced cannot read the rest of the memory; "Run (internal disks read-only)" starts as before and is the way back if a device misbehaves.
• The boot menu waits 5 seconds, and shows only once after an update. Settings > LibreELEC > System > Boot menu offers 10, 5, 3 and 1 second, and the restart that applies an update now goes straight on.
• Updates hides the entries that have nothing to act on while Hades has no update server, and Available Versions says how to install a new version.

The Windows installer

• The Windows installer has its own look: an icon, a side bar that shows the steps, light and dark following Windows, the serial number of the drive always visible, a window that shows each stage while it works, and a last page that says how to start Hades and what each entry of the boot menu does. An update keeps the wait of the boot menu and the display options that the menus hold.

Updates and the build

• Linux 7.3.4, with 41 fixes to fs/ntfs from mainline and two of its own, the Wi-Fi fixes of mt7921 and mt7925 (Mark Anthony Agarro and Devin Wittmayer), two fixes for Intel Wildcat Lake graphics, and AMD's fix from Linux 7.4 for DCN 4.2B (Gabe Teeger); the patches keep their authors.
• Up to date: LibreELEC master up to 23b6180 (Mesa 26.3.0, zlib 1.4 with its fixes for CVE-2026-85091 and CVE-2026-4738, OpenSSH 10.6p2, BlueZ 5.88, systemd 262.2, OpenVPN 2.7.9, Intel's processor microcode of 2026-11-10 and exfatprogs 1.4.4), Kodi 22.0rc2 of the Piers branch up to 169296d6bd84 (among its last commits, a floating-point framebuffer read as floats for screenshots by Garrett Brown, and a game port that keeps its default controller by Kel Modderman), and libplacebo d9ab3a48a55a.
• Security fixes: OpenSSL 4.1 and OpenSSL 3.5 (kept beside it for the add-ons that ask for libssl.so.3) carry the fixes of the five advisories that OpenSSL published on 2026-11-10, all of low severity; glibc takes the 38 commits of its stable branch and the fix of CVE-2026-84243; FFmpeg 9.0.2 takes its stable branch; lz4 1.11.1 fixes an out-of-bounds write of 1.11.0.
• The same commit builds the same system. Every date of a build now comes from the time of its commit: two assemblies of the image gave the same system, kernel and release tar byte for byte.
• Tests in the tree. tools/regress now carries host tests of the build, among them an independent check of the Dolby Vision composer of ETSI GS CCM 001.

Tested

Every change of 1.0 was tested on the host, with the code that the image runs, or in a virtual machine; the changelog says how for each item.

Works on hardware. I tried the final build of 1.0 on my PC: a GeForce RTX 4080 SUPER connected by HDMI to an LG C5 TV, with a TCL Q85H Pro sound bar (on the TV's eARC, or between the PC and the TV), and a Samsung Odyssey OLED G6 monitor with HDR10+. These work:

• Native Dolby Vision of profile 7 with its full enhancement layer (several films, with Dolby TrueHD and Atmos passed through), profile 5 and profile 8.1, and HDR10 sent as Dolby Vision.
• The three Tron films, which had dropped out of Dolby Vision before, play in Dolby Vision.
• HDR10 with DTS-HD Master Audio passed through to the sound bar.
• The new player information page.
• Moving from the LG C5 to the Odyssey monitor and back from the settings, with the display that is not in use turned off.
• On the Odyssey, which takes HDR10+ and not Dolby Vision: Dolby Vision videos that carry their own HDR10+ go out as HDR10+, and HDR10+ videos go out as HDR10+.

What earlier versions showed working, on my hardware and on the hardware of users (NVIDIA RTX 50, 40 and 30, GTX 16 and GTX 10 cards, AMD Radeon and Ryzen graphics, Intel graphics; LG, Panasonic, Sony and Samsung TVs, projectors and receivers), is in What has been tested.

Not tried on hardware yet. These are new in 1.0 and could behave differently on your hardware than on mine:

• Check this setup.
• Streaming through a network drop: the film waits and goes on from where it stopped.
• Dolby Vision, HDR10 and 3D through a passive DisplayPort adaptor (DP++).
• Dolby Vision on the newest Ryzen processors (DCN 4.2 and 4.2B).
• Version 1.0 on AMD and Intel graphics, integrated graphics included, and HDR in 4:2:2 at 12 bits over HDMI 2.0 there: so far 1.0 has been tried on an NVIDIA card only.
• HDR at 12 bits on NVIDIA GeForce GTX 16, RTX 20 and newer cards where the card would send RGB at 8 bits.
• With several displays on one graphics card, the sound that follows the display in use, and Keep the display of the audio output on for a receiver on its own output.
• DVD films shown at their own rate, and the Blu-ray changes of 1.0: no disc has been tried.

If you try one of these, or anything else, please say what you see in the issues, with the diagnostic switch on.

Before you update

• The boot menu now waits 5 seconds. An update brings a menu that waited the old 10 seconds to 5, once; a wait that you had set to something else is kept. Settings > LibreELEC > System > Boot menu offers 10, 5, 3 and 1 second.
• With several displays on one graphics card, only the display that shows the picture stays on, and the sound goes to that display. For a receiver or sound bar on its own output of the graphics card, turn on System > Audio > Keep the display of the audio output on (Expert).
• If you had set Audio offset to make up for the picture coming one refresh early, set it back to 0.
• Dolby Vision is sent as composed from now on; a transport setting left at the old default takes the new one. IPT-PQ-c2 stays available as an expert choice.
• On Radeon RX 400, RX 500 and Vega cards, Dolby Vision plays as HDR10 unless you turn on System > Display > Dolby Vision on this Radeon (experimental).
• On NVIDIA, HDR above 8 bits where the card would send RGB at 8 is now on by default. If the TV does not lock onto it, that mode goes back to 8 bits by itself for the session.
• On a display without HDR, HDR keeps brighter middle tones. If you preferred the old look, choose "BT.2390, libplacebo's knee" as the tone mapping method or as the Tone mapping curve.
• Run and Live now start with DMA translation. An update in place adds it to the menus once; if a device misbehaves, "Run (internal disks read-only)" starts as before.
• The documentation is in English only; the Windows installer and the menus of Hades keep their Spanish.

Install or update

New install:

1. Write the .img.gz to a USB drive. On Windows, run LibreELEC-Hades-Installer.exe: it lists your drives with their model, size and serial number, asks you to type a word before it touches anything, and checks what it wrote. Any other program that writes disk images works too. The drive is erased.
2. Restart the PC, open the firmware's boot menu (F8, F11, F12 or Esc on most PCs) and choose the USB drive. Secure Boot must be off.
3. Choose "Run" in the boot menu (it starts by itself after 5 seconds). The first start prepares the storage and restarts once; choose "Run" again.
4. Answer the first-run wizard: language, the name of the system, the network and the services.

The installer can also install Hades on a secondary internal disk without erasing it. Started from USB, Hades changes nothing in the PC's boot settings or in Windows: to go back to your usual system, shut Hades down and start the PC normally.

Update: settings, add-ons and the diagnostics are kept whichever way you update.

• With the Windows installer: choose the drive that has Hades and "Update".
• With the .tar: copy it to the Update folder of a drive with Hades and restart. Over the network, turn Samba on in Settings > LibreELEC > Services, open \\<name of the system>\Update (Windows) or smb://<name of the system>/Update (Mac, Linux) with the user and password that the window shows, copy the .tar there and restart.

Hades does not look for updates by itself. Dolby Vision needs an exact HDMI signal: turn off variable refresh rate and the colour adjustments of the graphics driver. If the picture is not Dolby Vision where you expect it, the player information says why, and Check this setup says what reached the TV.

Files

Check your download with sha256sum -c SHA256SUMS (Linux) or Get-FileHash <file> (Windows, in PowerShell), and compare with:

Known limits

• Dolby Vision needs an untouched HDMI signal from an HDMI port of the graphics, or through a passive DP++ adaptor that identifies itself as HDMI. Variable refresh rate, scaling and colour adjustments in the graphics driver are not compatible with it, and an active converter between DisplayPort or USB-C and HDMI does not carry it.
• Native Dolby Vision goes out at 3840x2160, up to 60 Hz; on Intel UHD 6xx graphics, up to 30 Hz and only from an HDMI port of the graphics itself.
• HDR in 4:2:2 at 12 bits over HDMI 2.0 (Intel and AMD) needs one more change of mode at the start of an HDR video at 3840x2160 and 50 or 60 Hz; turn the setting off in System > Display if that bothers you.
• GeForce GTX 900 and GTX 10 cards and the TITAN V use NVIDIA's driver 580. A PC with one of them and a newer NVIDIA card at once gets the newer driver, and the older card gets none. The GTX 900 cards stay at 8 bits over HDMI.
• Dolby Vision Low-Latency is mapped by Hades, not by Dolby's display management, which is not public. HDR10 sent as Dolby Vision carries metadata measured from the picture as it plays, not the studio's.
• HDR10+ goes out only where the graphics driver can send it with each frame, otherwise as HDR10.
• BD-Live reaches the Internet over IPv4 only.
• 3D has not been seen on a 3D display, and no 3D disc has been tried. If a 3D video shows a black or broken picture, turn off System > Display > Switch the display to 3D (HDMI).
• No Secure Boot.
• This is an independent implementation written from public specifications. It has not been tested or certified by Dolby or by HDR10+ Technologies, and it may differ from a certified player.

The full list is in the README, under Known limits.

If something goes wrong

Report problems in the issues of this repository, not to LibreELEC, Kodi, Dolby, HDR10+ Technologies, NVIDIA, AMD or Intel. Please include:

• the build (Settings > System information, or the PRETTY_NAME and BUILD_ID lines of /etc/os-release);
• the graphics, the TV model and how they are connected;
• what you played (container, Dolby Vision profile or HDR format) and what you saw;
• a diagnostic report: Settings > LibreELEC > System > Submit Log > Create a diagnostic report makes one file and can copy it to a USB drive. Look through it first: it is filtered, but it is yours to check. If Kodi does not start at all, turn the diagnostic switch on in the Windows installer and send the hades-diag folder of the drive.

The diagnostics guide says how to get them, also from a system installed on an internal disk. If the same problem happens with an official LibreELEC image, it belongs to LibreELEC or Kodi and can be reported there.

Source code and licences

The complete source of this build is this repository at the tag v1.0, plus the source archives above. LibreELEC's build system is under the GNU General Public License, version 2, and each patch has the licence of the program it changes. Kodi is GPL-2.0-or-later, and so is the code that this build adds to it, among it the Dolby Vision module (tools/dvbridge); as LibreELEC builds it, the Kodi built here is distributed under GPL-3.0-or-later. The NVIDIA user-space libraries and firmware, and the closed core of the kernel module of driver 580, are proprietary and come under the NVIDIA Driver License Agreement. Every source is checked against the SHA-256 written in its recipe, and builds of the same commit can be compared byte for byte. Licences and source code and NOTICE.md have the details.

Thanks

What is new in this version is written for Hades, apart from the updates of LibreELEC, Kodi and Linux and the fixes taken with their authors, which keep them; each is named on its item above and in the changelog.

This work began in CroqueMr's Dolby Vision fork of LibreELEC, and its contributors: its Dolby Vision module for Kodi (dvbridge), from which the Dolby Vision output of Hades grew, its Dolby Vision output for Intel graphics, and its changes to FFmpeg and libplacebo. Several features of 1.0 follow ideas from CroqueMr's build, YBLOD, CorentinB, cinemaONE, SamuriHL, pannal, avdvplus, matthane, malard, damnms and Pro-me3us, written again here; the settings for the colour format and the depth of the link follow Kodi pull requests 30099 and 30192, by smp79, as CroqueMr's fork carries them; the format and the name of Player.Process(video.sidedata) are Team CoreELEC's. Thanks also to Dom Cobley (popcornmix) for the decoding of 3D Blu-ray video, to cinemaONE, quietvoid, CoreELEC, big-fella and harment, whose work the README credits one by one, and to the LibreELEC and Kodi teams.

Thank you to everyone whose reports, requests and tests shaped this version, in the issues of this repository and on the LibreELEC and Kodi forums, among them roronoazoro-blip, RaphS8, SunnySnacks, Levi741i, wright96d, sat4all1-dev, Khazar321, testmest, ht2tweak, lfemperor, nissel, doppingkoala and vertox, and to everyone who tried the release candidates and said what they saw, among them BigRedJim, cinema-ONE, sultan917, Iftuga, andrei-er, vinc-lab-creator, harment, bevigilant, pulento and SeaMonkey82.

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