Enable support for IR RC MCE Keyboard on startup


#1

The MCE Keyboard events do not need any lircd profiles, and can be supported in parallel to RC5/RC6 lircd profile. If mce_kbd is enabled when kodi starts, this makes it very easy for Harmony remote users to get a comprehensive solution to many any command they like. A Harmony can be mapped to a Microsoft / MCE Keyboard profile, which lets us assign any key on a keyboard to any Harmony key.

Currently on each reboot we would need to re-enable mce_kbd like this:
sudo ir-keytable -p lirc -p rc-6 -p mce_kbd

It would be good if there was support in MY OSMC to enable mce_kbd on bootup and possibly also define key delay and key repetition speed on the UI which then uses ir-keytable to set the values on bootup.


#2

You can put this in rc.local for now.

We are redesigning remote support but it’s not in line with what you are trying to achieve. Our goal for the foreseeable future is to make user space configuration as flexible as possible. This would mean keeping the current method of devolution, where we defer IR events to a user space context unless USB hardware is attached (where we handle RC6 via kernel unless disabled in My OSMC).

I’d much prefer getting this resolved in the right way via LIRC. Did you try recording your own profile?

Sam


#3

Hi Sam, the point is that most people are not keen on tinkering around with lirc profiles. the MCE KBD solution we be dead easy, it works fine in parallel to lircd, so I don’t catch your point so far, why the small modification of making mce_kbd protocol available on boot is would not be feasible, and instead forcing/encouraginf people to dive into lirc profiles. From a usability point of view it just makes no sense to go in that direction. In that case people would expect a more extensive lirc profile pool, especially for such prominent universal remotes such as the Logitech Harmony family. The current lircd profile for OSMC is just not flexible enough. The MCE Keyboard is.


#4

The idea of Harmony is that you can select any profile you’d like.
There won’t be a one size fits all situation, particularly for users that own these remotes.

If the standard profiles suck for Harmony remotes, maybe we need a Harmony profile under My OSMC -> Remotes?

Sam


#5

A really powerful profile for Harmony would really help. You don’t have this remote with so many buttons and features and then just use the bare minimum…
No, i’m not going to make that profile, as I said, I woul dprefer the solution with MCE KBD, because I dont want to go into lirc details.


#6

No one needs to go in to LIRC details if a profile is achieved.
But when we tried to consolidate on a common Harmony profile; we were told that many people had different preferences.

So I am still for a common, sane, Harmony profile.

Sam


#7

Had a chance to check this more thoroughly.

As stated previously, the changes you are making are just deferring the interpretation of codes from userland (LIRC) to kernel (ir-keytable). The fact that this works indicates that there isn’t an issue with the receiver (meson-ir); but a profile mismatch with LIRC.

I think a correct profile will do the trick here.

We added the option ‘disable RC6’ to My OSMC decoding to prevent sporadic behaviour for some users on Pi that were experiencing duplicate presses when using the built in kernel IR decoders when using a USB receiver. They found the userland (LIRC) interpretation more reliable.

There is no repeat filter when using kernel based decoders as you will bypass eventlircd’s repeat filter. This filter was introduced originally to reduce incidence of duplicate presses; but this was set many years ago.

I’m happy to produce some test builds if you are willing to test My OSMC remote profiles and repeat filter changes.

Cheers

Sam


#8

Sure if you want to test something I’m in.