Posts by HiassofT

The output of "play" looks fine (as expected when the Harmony repeats the command 3 times): It sends the scancode 0xab22 three times, which then results in a single key_down event.

The "left" test is odd though, the Harmony transmits two different scancodes, first 0xab2c and then 0xaf63, and repeats that three times. This doesn't end well, when a different scancode is received it's interpreted as a release ("up") of the previous scancode.

That's something you need to fix in the Harmony configuration - make sure a button sends a single scancode.

so long,

Hias

Copying dt-blob.bin from LE9.2 to the FAT partition might be enough to get an RPi2 image booting. Recently a user used that to successfully boot RpiOS (ex Raspbian) on a Slice with CM3

Trying (and failing) to resurrect my Five Ninjas Slice with CM3 - Kernel Panic - Raspberry Pi Forums

As I don't have a Slice I haven't tested that myself so can't be 100% sure if that'll also work with current or future LE 10 images, but I'm quite confident and you should have a starting point.

so long,

Hias

Can you post the output of "ir-keytable -t" when you do a short button press on the remote?

Usually remotes send the scancodes every (approx) 100ms while the button is pressed, this is interpreted as a "held down" button by the input subsystem - you'll see an initial "key down" event and then get further key down events after the specified repeat delay.

If the scancodes are too far apart linux will detect them as separate button presses (i.e. key down followed by key up some 150ms afterwards).

If the scancodes are only a bit too far apart then tweaking the receive timeout (ir-ctl -t VALUE_IN_MICROSECONDS, eg ir-ctl -t 125000) can help to detect these as a held down button - ideally the Harmony remote should behave like standard remotes though and follow the protocol specs though.

so long,

Hias

You could try increasing the delay before repeat kicks in - use eg ir-keytable -D 750 to increase it from 500 to 750ms.

This will work while kodi/eventlircd are running so you can experiment with the values.

so long,

Hias

It's your Harmony remote sending those repeats, simply disable the command repeat feature in the Harmony config software and you'll be fine

Fixing Repeats

so long,

Hias

Seeking with H264 HW decoding is currently being worked on, yesterday we had a first working test version (but it's not finished/final).

I can't give an ETA when we'll do a first alpha release - RPi4 builds are already looking quite good but there are also other things that need to be fixed/ironed out before we start wider testing.

so long,

Hias

Not really. There is/was a kodi PR to add longpress support for remotes WIP - [remote] Allow longpress mod for remote keymaps by phunkyfish · Pull Request #16740 · xbmc/xbmc · GitHub but it's in a rather dormant state.

So the only way to get this is disabling eventlircd and remapping buttons via hwdb/ir-keytable so X11/kodi can deal with them.

so long,

Hias

More likely X11 doesn't cope with most button/keycodes, so you'd have to remap quite a lot of buttons/keys via hwdb or ir-keytable. Maybe some tweaking of x11 keymaps might also work (haven't tried that yet).

I don't have LE on x86 here but I just checked on my Debian x86 PC and the numeric buttons on the MCE remote don't work OOTB either (they send KEY_NUMERIC_0... instead of the typical KEY_0).

so long,

Hias

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)

: > /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

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

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

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

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

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

It's best to avoid the "MCE Keyboard", this is a really awkward protocol that's working poorly. Just stick to the Microsoft mediacenter (MCE) remote protocol, this is what you want to use ("Microsoft Windows Media Center SE" sounds like that might be fine, though I'm not really familiar with the harmony remotes)

so long,

Hias

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)

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

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

Both will work fine, choose whatever suits you best.

so long,

Hias