Posts by HiassofT

  • MCE keyboard IR remote

    This is tricky. The only way to get proper MCE keyboard handling or longpress support for remotes is to disable eventlircd processing (for MCE keyboard you also have to enable the mce_kbd protocol via ir-keytable/rc_keymaps).

    You can do that by creating an empty udev rule file (remove it to restore normal behaviour)

    Code
    : > /storage/.config/udev.rules.d/98-eventlircd.rules

    The drawback is that then several buttons, most importantly the OK button, no longer work - kodi doesn't support OK etc keys on a keyboard. You can fix that by doing key remapping via a hwdb.d file, search the forum for examples if you're feeling brave.

    so long,

    Hias

  • A good config.txt for pi4?

    Tearing is an issue with the fkms video driver in LE 9.2 - that's fixed in LE 10 which uses the kms driver.

    Keep config.txt as is, if you have issues with HEVC files you may consider increasing gpu_mem to 384 - ebut that's only for LE 9.2, in LE 10 things will be very different.

    Do overclocking at your own risk and always keep in mind that things under the hood may change and your overclock settings may result in an unstable system after each update. So if something's odd first thing to check is if it works stable without overclocking.

    so long,

    Hias

  • RPi4 testbuild with HD audio passtrhough (Atmos etc)

    Thanks a lot for testing and the feedback!

    LibreELEC 9.2 uses the old display driver so it doesn't support HBR audio passthrough.

    As the new display driver requires audio data in IEC958 format (converted from S16/24/32 etc by alsa-lib) you can't check for the actual audio format used by programs via /proc, you have to enable verbose or debug output in the programs to see what they use.

    Not 100% sure about the sox player, but IIRC kodi uses 32bit float for internal PCM audio processing and will in general use 24bit for output (enable debug logging in kodi to see the details). This gives you enough headroom to apply volume attenuation to 16bit audio data, without loosing bits, and ensures 24bit audio will be transmitted fine, too. So in general there's nothing to worry about PCM and compressed audio in kodi.

    so long,

    Hias

  • Harmony Hub issue with MCE Remote: some buttons don't work

    Again, no, this won't help you with MCE Keyboard - LE 9.2 doesn't ship with any configuration files for that.

    LE with newer ir-keytable comes with mce_keyboard.toml, which is basically the same as rc6_mce with both rc-6 and mce_kbd protocols enabled.

    Still, you don't want to use that, mcd_kbd doesn't use key configuration from that file - the driver sends fixed KEY_A etc (like normal keyboards) which aren't really supported in LE's/Kodi's IR remote stack (you'd need to extend Lircmap.xml to translate KEY_A or whatever to some button name).

    Simply stay away from MCE Keyboard, that causes lots of unnecessary troubles.

    so long,

    Hias

  • Harmony Hub issue with MCE Remote: some buttons don't work

    Quote from ghtester

    /etc/rc_maps.cfg and /usr/lib/udev/rc_keymaps/libreelec_multi.toml

    Uh, no, LE 9.2.6 doesn't use toml files.

    The wiki page describes the setup and files used in LE 9.x, master / LE 10 uses a newer ir-keytable version which uses toml files by default (the old files without toml extension are still supported though). The new toml format isn't documented on the wiki yet as it'd just confuse LE 9.x users for now, this will follow at some later point when we release LE 10.

    so long,

    Hias

  • Harmony Hub issue with MCE Remote: some buttons don't work

    The output looks fine and if you still have MCE Keyboard buttons mapped to menu/exit the output is expected - ir-keytable shows you that the MCE Keyboard protocol mce_kbd is supported but not enabled.

    The MCE Remote (rc-6 protocol) usually has "Back" and "(DVD) Menu" buttons that map to exit/back and (context)menu in kodi. Just use these and stay away from MCE keyboard in the harmony configuration software.

    BTW you can find more info on the wiki Infra-Red Remotes - LibreELEC.wiki and if you search the forum for mce_kbd you'll find info how to get MCE keyboard working - but that's rather tedious and not really needed in your case, MCE Remote should have everything you need/want and will work OOTB.

    so long,

    Hias

  • lirc changes in 9.2

    Yes, LibreELEC switched to ir-keytable but lirc is still there for now if you really want/need to use it. See the wiki for more details Infra-Red Remotes - LibreELEC.wiki

    Your dmesg doesn't show any sign of the gpio-ir driver being loaded, so check config.txt if you have any typos in there.

    dtoverlay=gpio-ir, is all you need then you should get the following lines in dmesg (note that I use GPIO 5, so your lines may look a bit different)

    Code
    xbmc:~ # dmesg | grep gpio_ir
[    4.257079] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver@5/rc/rc0
[    4.257233] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter
[    4.257353] input: gpio_ir_recv as /devices/platform/ir-receiver@5/rc/rc0/input1

    so long,

    Hias

  • No 4K resolution on RPI4

    hdmi_enable_4kp60=1 is the correct setting. Also remove all other hdmi options you added and make sure you've enabled "Ultra HD deep colour" in your TV's settings (usually that setting is separate for each HDMI port, and it might be called slightly differently on your TV).

    so long,

    Hias

  • Bigger HDD is required when updating my KODI.

    Your initial problem was not with the total size of your SSD, but that older OpenELEC/LibreELEC versions created a rather small boot partition (/flash on the filesystem) which now became too small. Re-installing current LE (wiping your previous partitions) will fix that.

    Current LibreELEC will work fine even on an 8GB SSD/SD-card/HDD, although I'd really recommend going for 32GB (or more) to have some spare room for larger movie libraries. If you want to store media files on your SSD/HDD/... you'll need a lot more space, of course.

    so long,

    Hias

  • Increase log_buf_len (Generic Intel)

    Most devices use the kernel default of 128k (CONFIG_LOG_BUF_SHIFT=17), not sure why Generic is set to 64k. Would be best if you created a PR and change it to 17, too

    so long,

    Hias