Posts by chewitt

  • Audio equalizer for Raspberry PI

    It will be possible in Kodi v18 if/when the ADSP add-ons are finished and supported. If you run LE 7.90.001-008 you'll find them in the add-on repo. If you run 7.90.009 (next alpha) they have been removed from our repo due to the upstream decision to bump them to v18.

  • Hyper-V Support?

    If you do the changes we promise Hyper-V will be neglected equally to vmware and vbox. Virtual is an internal testing tool not a "supported" project for broad public consumption. We have no objections to a few people using it as long as the support status is clearly understood. Some in the wider community would like Virtual to be taken seriously and supported, but as none of them want to step forward and act as its maintainer it's current status is unlikely to change anytime soon.

  • MP4 file playing issue from USB drive

    Quote from kmihmisc


    I am running Raspbian Jessie LITE with KODI Jarvis V16 updated by doing a "apt-get" from pipplware.pplware.pt. I was under the impression that the people who wrote LibreElec were also involved in the KODI / Raspberry Jessie Lite project. Please correct me if I am wrong. Is this an issue that should be reviewed by the Raspberry Jessie LITE or KODI project developers?

    There are a small number of people who are members of both project teams. However you are in the LibreELEC forum where we discuss and take interest in "Kodi on LibreELEC" issues. If you want support for "Kodi on something else" the questions belong in the Kodi or the other distros' support forum (Kodi's would be my recommendation). It's not that we're trying to be difficult .. I'm one of the 3-4 people who sits in both teams and I've never booted anything but LibreELEC on pi hardware or installed Debian on anything else, so I'd suck at guessing what your Jessie Light problem is.

  • WiFi and compilation error while building 7.0.2

    I'm still building official things on 16.04 which works fine as I created a 7.0.2-ish image yesterday. We're not really interested in trying to solve custom build issues on the 7.0 branch as Jarvis is basically a closed book now, but if you create a Krypton build (master branch) it will use gcc 6.2 which might sidestep the version issue. Despite the 'Alpha' working label Raspberry Pi builds are extremely stable.

  • FiveNinjas Slice LibreELEC preview build

    A note for anyone self-building things from my slice-8.0 branch on GitHub:

    Gordon figured out how to make Kodi correctly detect an IEC958 device which allows the S/PDIF output to send lovely 5.1 output to an AVR *BUT* you must ensure the "Sync playback to display" option in System > Playback is disabled for multi-channel audio to work. If you have SP2D enabled *all* audio is resampled to 2.0 PCM. In older Isengaard/Jarvis Kodi builds it's possible to have SP2D enabled and still get multi-channel output (sort of a bug that's fixed in Krypton) so if you update to these builds this might catch you out.

    NB: The snd_slice.conf to enable 5.1 output will be in v7.90.009 which is sort of ready but waiting for Kodi 17-beta 6 which is taking an age to be released due to some unresolved addon update/crash bugs affecting Windows Kodi builds.

  • Asus Chromebox from OE to Libreelec

    If you read the text on the download page, the bit where it says "For all other downloads (files to use with 3rd party SD creator tools, manual update files, NAND install files, noobs files, files to migrate you from OpenELEC, etc.) please select your hardware in the drop-list below:" .. and then click in the drop list you can navigate away from the Raspberry Pi downloads to the Generic AMD/Intel/nVidia image downloads.

    To recover an existing installation either create a new LE USB and attach a keyboard, then boot from the USB and CTRL+ALT+F3 to access a local console where you can mount the internal drive and download/extract/replace the KERNEL/SYSTEM files in the boot partition. Or create an Ubuntu LiveUSB and use GUI tools there to do the same thing.

    NB: LE has mechanisms to detect and abort updates when people load the wrong files, but when you first update from OE you're using OE's older update process and this has no protection.

  • FiveNinjas Slice LibreELEC preview build

    I think the best option is a simple finned heatsink that can be attached with a small dab of [heat] conductive paste and a small elastic band around the SO-DIMM board to hold it in place. This would be simple for users to apply and doesn't result in direct contact with the casing. Solutions that achieve case contact will be thermally more efficient but there's a higher risk of mechanical damage; not from thermal flexing, but when a fat-fingered user puts a huge gob of paste on the CPU which uses all the tollerance up and places stress on the SO-DIMM connector. The CM3/Slice has been designed to run quite happily at high temperatures so the goal of adding heatsink is not to achieve the best possible thermal transfer; only to reduce the temperatures enough to keep the thermometer off-screen. I'm only seeing it during large library scans or when trying to software decode HEVC content that it can't handle (with any level of overclock) so it's not really a big deal.