Modern Linux kernels, like the ones used in LibreELEC, have built-in support for IR remotes. IR signals are decoded by the kernel and programs see button presses from IR remotes in the same way as key presses from a normal keyboard, as Linux input events. Required LIRC kernel setup lircd driver Default lircd and lircmd config files Supported remotes' USB devices; Other (MIDI, Bluetooth, udp, etc.) Home-brew serial and parallel devices. This is the successor to LIRC where a separate program, lircd, decodes the IR signals and programs could get the button presses from a socket as LIRC events. While this new scheme is really handy, there's a small gotcha: Kodi's remote handling is built for LIRC and it doesn't cope well with Linux input events. In general all buttons also present on a normal keyboard, like arrows and numbers, work fine but rather important buttons like OK and channel up/down don't. To solve this problem LibreELEC runs a small program in the background, eventlircd, which translates Linux input events from remotes into LIRC events. So, while under the hood the new scheme can be used, remote buttons still show up as LIRC events in Kodi. Kodi then translates the LIRC events to internal kodi button names (via Lircmap.xml) which are mapped to Kodi actions (via remote.xml / keyboard.xml files). This document only describes the LibreELEC configuration, information about Kodi configuration is available in the and wiki pages. LibreELEC still ships with LIRC so IR remotes with non-standard protocols and rather special setups can be supported. ![]() In general, keep LIRC disabled (in LibreELEC Settings → Services) and only enable it in the very few cases where you actually need it. If you upgraded from LibreELEC 8.0.x to 8.2 and you get double button presses or your remote doesn't work as expected disable LIRC in LibreELEC Settings and then reboot. Important changes in LibreELEC 9.0. LibreELEC uses ir-keytable to configure IR remotes, just like most current Linux distributions. Download software alat musik. Each IR receiver kernel driver installs a default keytable. This keytable specifies which IR protocol to use (eg RC-5, RC-6, NEC, ) and the scancode to Linux keycode mapping. ![]() Most universal receivers default to the rc-rc6-mce table so standard RC-6 MCE remotes can be used without any further configuration. Drivers for devices that are usually sold together with a remote usually install their own keytable - so that eg the Hauppauge remote that came with a Hauppauge DVB stick works out of the box. After the driver is loaded, ir-keytable -a is automatically run so that the kernel default configuration can be changed: •. Typically you'll have only one IR receiver you need to configure and the file is really simple. Eg if you found out that the samsung keytable works, create a /storage/.config/rc_maps.cfg file with the following content: * * samsung To test if that rc_maps.cfg file works run ir-keytable -a /storage/.config/rc_maps.cfg If everything's fine the output should look like this: LibreELEC:~ # ir-keytable -a /storage/.config/rc_maps.cfg Old keytable cleared Wrote 30 keycode(s) to driver Protocols changed to nec Test again if the buttons work, if everything's OK reboot. Configuration, the hard way. If you couldn't find a working keytable “the easy way” you need to create your own from scratch. The format of the keytable file is rather simple: It's a plain text file, the first line contains a header with a descriptive name (you can choose that rather arbitrarily, but better avoid special characters, spaces and such) and the remote protocol to use (the type: - which is very important). After that each line contains a mapping of remote scancode to Linux keycode. A typical keytable file looks like this: # table justboom, type: RC5 0x101a KEY_UP 0x101b KEY_DOWN 0x1013 KEY_LEFT 0x1014 KEY_RIGHT 0x1015 KEY_OK Before you can configure your remote “the hard way” you have to stop Kodi and eventlircd by running these two commands: systemctl stop kodi systemctl stop eventlircd If you miss to do this ir-keytable won't show any input events as Kodi or eventlircd have grabbed the input device (unfortunately ir-keytable doesn't print a warning in that case).
0 Comments
Leave a Reply. |