Posts by chewitt

  • HDR Support

    Assuming you have a recent Intel GPU with HDR support, then in current Kodi full = HDR, HDR10, and HLG. Dynamic HDR10+ is not supported but almost all media using HDR10+ has HDR10 fall-back so you still see somehing nice. DV is a mixed bag: some media has HDR10 fall-back so you'll see something fine, but other content (mostly from online streaming services) does not and then you'll see weird colours. There's some background progress on solving that with tonemapping, but these things take time. There is also limited HDR > SDR conversion through tonemapping. If you want 'full' HDR support you need to use an Android device that has full support (nVidia shield is the default recommendation).

    The installer for the Generic image needs to create two partitions: one for boot files, one to be used as persistent storage, so it does not support installation into an existing partition. It only installs to the entire disk so if you have Windows and Ubuntu on the same physical disk it will nuke both. It's possible to manually remove the Windows partition and create the required two partitions in its place, copy files over to the boot partition, then create a grub2 (the Ubuntu bootloader) entry for LibreELEC, but you'll need to go figure that out on your own (there are some threads here if you Google for them). It's also possible to just boot LE from a USB key when you need it, or to install the Kodi snap in Ubuntu and use that instead.

  • Kodi 21 Latest Version

    The board was added after LE12 shipped so it only exists in the kernel used with LE13 nightlies. The Alpha tag represents Team Kodi dragging it's arse on the release cycle more than anything else. In reality K22 is more like a late-cycle beta than alpha and it's been like that for a year already. In short, don't sweat the label and use the nightly.

  • Change advancedsettings.xml

    It's not an LE concept, Kodi supports this on all platforms. The final settings used are always a composite of default (which in our case are embedded in the SYSTEM file which make them read-only) + userdata (advancedsettings.xml) settings. Userdata settings only overwrite default if they exist in both places, i.e. you don't need to clone the entire default file.

  • Connection error when building

    Quote from Thursty24

    --2025-03-20 21:25:12-- https://curl.haxx.se/download/curl-8.6.0.tar.xz
    Resolving curl.haxx.se (curl.haxx.se)... 127.0.0.1

    The build device is resolving the download location to 127.0.0.1 (localhost) instead of resolving to a CNAME which has 4x public A records (which are all available). That suggests a DNS issue at your end as the URL resolves fine from here (UAE).

    Quote from Thursty24

    --2025-03-20 21:25:13-- http://sources.libreelec.tv/mirror/curl/curl-8.6.0.tar.xz
    Resolving sources.libreelec.tv (sources.libreelec.tv)... 65.109.172.87
    Connecting to sources.libreelec.tv (sources.libreelec.tv)|65.109.172.87|:80... connected.
    HTTP request sent, awaiting response... 404 Not Found

    It then falls back to our sources mirror, which appears to be down/offline or missing some config at the moment, so that fails too. I'll ping someone internally about that, but it might take time before it's restored.

    It's possible to manually download the file to your local sources folder, but to fool the buildsystem into thinking the file has already been downloaded you'll need to manually create the .url and .sha256 hash files (the format can be cribbed from other downloads).

  • Raspberry Pi 4 as access point.

    Quote from TimboZero

    Can I set this to be an access point (same ssid and password) as my main fibre box to make the Wi-Fi in that room stronger?

    You can create a hotspot with the same name/passphrase as the other network in LE settings, but it will be an independent network, and there is zero configuration beyond name/passphrase (no choosing of IP range, frequency ranges, no config of auth) and it will not act as an extension of the existing wireless network so devices cannot roam between access points, they must disconnect and reconnect. You will also content with the reality of RPi wifi strength generally being a bit rubbish.

    In short, it is an intentionally simple hotspot (as you'd have on a phone) not an access-point or a router. If it works that's great. If it doesn't work there is nothing that can be done and the solution is using a proper AP/router device.

  • [x86-64] No Audio After Upgrading to LE 12.0.2

    The NUC supports both DP and HDMI output, but it was cheaper for Intel to implement the HDMI tranceiver using an LSPCON chip that converts DP to HDMI so both outputs can be handled in a single chip. The GPU still has an HDMI capability which shows up in the kernel (unless you manually disable it in kernel boot params) but this is not wired up to anything.

    NB: It may have worked on LE12 under the DP output too .. maybe?. No harm in staying on the nightly if it works though. Kodi will move to wrap up development on Piers soon and then there'll be an official release to update to.

  • [RPi5] Over-Saturated Coloring

    The media is 4K HDR, so when you start playback the TV is switched from SDR to HDR mode. This means everything is now in HDR mode so the OSD and (if you navigate out of playback) the Desktop will have saturated colours. Some platforms that Kodi supports (Android, Windows) can sometimes tonemap the OSD etc. to normalise the appearance, but on Linux and with low-power ARM SoC devices (as with Android) this is normally done using a dedicated hardware image processor function in the SoC (as doing it on the CPU is too intensive) and RPi boards do not have this capability (and even on devices that have it, software support in the kernel is rarely implemented in upstream Linux). There might be a possibility to improve things a little with shaders, but this is still something to be explored on the Kodi end.

    In short, it's currently working as intended/capable/expected and this is not a bug.