Posts by HiassofT

  • Important change in LE13 remote handling

    Quote from VLouis

    My questiuon would be: exist any alternative (simple) way to find the "key id" for different remote buttons?

    The easiest way is to enable debug logging in kodi and then watch the kodi log, using tail -f .kodi/temp/kodi.log and look for the HandleKey lines while you press the remote buttons.

    You'll see lines like this:

    Code
    debug <general>: bool CInputManager::HandleKey(const CKey&): volume_mute (0xf0b7) pressed, window 10000, action is Mute

    In this case the mute button was pressed, volume_mute would be the kodi keyname to use in keyboard.xml and 0xf0b7 is the kodi key id in hex.

    In your case the keyname would be "dvd" so you could also just use

    Code
    <dvd>System.Exec...</dvd>

    in keyboard xml - that's a bit easier to read and understand than key id="61692" :)

    so long,

    Hias

  • Nightly Builds

    Quote from HiassofT

    If you get "double button presses" from CEC then try increasing the Remote button double press timeout setting, eg to 30 or 50ms - that can be needed on some buggy TVs.

    Checking through the libcec issues I noticed you might need to set that to even higher values like 200 or 250ms - just check what works best for you.

    so long,

    Hias

  • Nightly Builds

    johnny depp the two CEC adapters are expected and kodi now supports separate configuration of both.

    If you have CEC issues make sure you start with clean settings, whatever you changed before in CEC settings may now interfere.

    Stop kodi, remove the old CEC settings and reboot:

    Code
    systemctl stop kodi
rm /storage/.kodi/userdata/peripheral_data/cec*
reboot

    If you get "double button presses" from CEC then try increasing the Remote button double press timeout setting, eg to 30 or 50ms - that can be needed on some buggy TVs.

    so long,

    Hias

  • Waipu TV ?

    This is because there haven't been any new releases for LE12/Kodi Omega since then.

    If you look at the release page you'll notice they are all version 22.x / Piers releases.

    The addon in our LE13 repo is up-to-date

    LibreELEC.tv/packages/mediacenter/kodi-binary-addons/pvr.waipu/package.mk at master · LibreELEC/LibreELEC.tv
    Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.
    github.com

    so long,

    Hias

  • [unoffical] LE13 Images for Slice CM3/CM4S

    Quick heads up:

    I've pushed an updated version to my slice-drivers branch https://github.com/HiassofT/slice…/kernel-5.10%2B that fixes the build issue in the slice audio driver with kernel 6.18 (it's a simple change to replace the deprecated and now removed old format definition to the new one).

    In order to get SPDIF out (somewhat) working you need both a kernel patch to the CS4265 driver and a alsa card conf so the iec958/SPDIF device shows up in alsa/kodi. See the top 2 commits in https://github.com/HiassofT/LibreELEC.tv/commits/le13-slice/ (for simplicity I added them for the RPi2 device, you'll need to adjust the paths to your structure).

    SPDIF support in the CS4265 driver is quite incomplete though (thus it's likely deliberately disabled in the upstream kernel driver), it doesn't support setting the control channel / AES bits via the standard alsa mixer controls and DACs/AVRs might struggle with that - so no guarantee that PCM/AC3/DTS audio via SPDIF will work (the original Slice images had the same issue, though).

    My Behringer SRC2496 accepted the PCM stream via Toslink/SPDIF, but I don't have any other devices here to test that with.

    so long,

    Hias

  • Important change in LE13 remote handling

    Ah, likely you had media and exit buttons in a remote section - that won't work.

    The lirc/ir remote handler is quite limited, it only supports a handful button codes - see https://github.com/xbmc/xbmc/blob…slator.cpp#L161

    You had to map linux input codes (like KEY_MENU) to those kodi remote button codes via a Lircmap.xml and then map the kodi remote buttons to kodi actions in remote.xml.

    Quite annoying, especially if you had a remote with lots of buttons.

    Fortunately all this is gone now :)

    so long,

    Hias

  • Important change in LE13 remote handling

    Create a keyboard.xml with a keyboard instead of a remote section.

    The key/button codes are a bit different (remote had special remote button codes), eg instead of mute you likely have to use volume_mute - if in doubt check the HandleKey lines in kodi.log in debug mode.

    so eg this should work:

    Code
    <keymap>
  <global>
    <keyboard>
      <volume_mute>RunScript(/storage/.config/BTconnect.py)</volume_mute>
      <record>ToggleWatched</record>
    </keyboard>
  </global>
</keymap>

    Have a look at the system keyboard.xml for current default mappings and available key codes.

    Edit: kodi log shows it's tripping over the media and exit button/keycodes in your xmls.

    so long,

    Hias

  • Nightly Builds

    Quick heads up:

    We've now finally retired Generic-legacy and won't provide any updated LE13 image and addon builds for it anymore.

    If you were still using Generic-legacy please switch to Generic.

    so long,

    Hias

  • Development Support [RetroAchievements]

    I'd recommend building kodi, game.libretro and rcheevos with debug info and also enable the address sanitizer.

    You can pass in the needed options as environment variables when building LE, but personally I prefer to create a .libreelec/options file with them. eg:

    Code
    DEBUG="kodi game.libretro rcheevos"
DEBUG_SANITIZER_CFLAGS="-fsanitize=address -fno-omit-frame-pointer"

    Then do a full clean image and game.libretro addon build.

    The undefined behavior sanitizer can also be helpful - see the gcc docs https://gcc.gnu.org/onlinedocs/gcc…on-Options.html

    Another possibility is to run kodi with valgrind - it's a lot slower than the address sanitizer but may give additional info.

    To include valgrind in the image you need to enable it:

    Code
    VALGRIND="yes"

    and then manually start kodi with valgrind kodi --standalone -fs --audio-backend=alsa+pulseaudio

    Depending on where exactly it's crashing you may need to enable debug info for additional packages.

    so long,

    Hias