I think you may have what I'd define as a 'workflow' issue.
My suggestion would be.
Once you have the remote working then open a terminal session and run
ir-keytable -v -t
Press every single key on the remote and make a note of what that key outputs
Now open /etc/rc_keymaps/'the keymap file you're actually using'
Also open https://www.mythtv.org/wiki/Keybindings
Let's say when you press the Play key on the remote ir-keytable -v -t
outputs '00FC678 PLAY'
You probably want this to actually output KEY_PLAY rather then PLAY,
so looking at your /etc/rc_keymaps/'the keymap file you're actually
using' find the '00FC678 PLAY' line (yours will be a different value
obviously) and edit PLAY to KEY_PLAY.
save /etc/rc_keymaps/'the keymap file you're actually using'
CTR-C ir-keytable to kill it
reboot (I had to reboot as the bindings for the keymaps from
/etc/rc_keymaps/'the keymap file you're actually using' are set in the
kernel at boot time then, although this may not still be true).
start a mythfrontend session
using your normal keyboard navigate to a valid media file and start
it, then pause it.
now using the remote see if the PLAY button works as it should.
If it does you now know the principla is working correctly and it just
becomes a matter of 'mapping' the syntax of the keybindings correctly,
so reopen the /etc/rc_keymaps/'the keymap file you're actually using'
and edit every single button to give you the output you want it to
Here's an example of a chunk of my edited rc6_mce file # table rc6_mce, type: RC6
# 0x800f0400 is usually KEY_NUMERIC_0 - same for all numbers
0x800f040e KEY_MUTE # 0x800f040f is usually KEY_INFO
0x800f040f KEY_I # 0x800f0410 is usually KEY_VOLUMEUP
0x800f0410 KEY_F11 # 0x800f0411 is usually KEY_VOLUMEDOWN
0x800f0411 KEY_F10 # 0x800f0412 is usually KEY_CHANNELUP
0x800f0412 KEY_PAGEUP # 0x800f0413 is usually KEY_CHANNELDOWN
0x800f0413 KEY_PAGEDOWN # 0x800f0414 is usually KEY_FASTFORWARD
0x800f0414 KEY_U # 0x800f0415 is usually KEY_REWIND
0x800f0415 KEY_J # 0x800f0416 is usually KEY_PLAY
0x800f0416 KEY_P # 0x800f0417 is usually KEY_RECORD
0x800f0417 KEY_R # 0x800f0418 is usually KEY_PAUSE
0x800f0418 KEY_P # 0x800f0419 is usually KEY_STOP
0x800f0419 KEY_ESC # 0x800f041a is usually KEY_NEXT
0x800f041a KEY_Z # 0x800f041b is usually KEY_PREVIOUS
0x800f0421 KEY_RIGHT # 0x800f0422 is usually KEY_OK
0x800f0422 KEY_ENTER #0x800f0423 is usually KEY_EXIT
Hope this makes sense and you can work through the correct mappings,
it's not that complicated, but it is very confusing because you need
to understand how the 'flow' is working before you can crack it.
If you need any further help just let me know.
On 26 August 2017 at 20:57, Hika van den Hoven <firstname.lastname@example.org> wrote: > Hoi Tom,
> Saturday, August 26, 2017, 9:39:42 PM, you wrote:
>> One thing I was curious about was this: When I installed (compiled
>> under Gentoo) ir-keytable I noticed that the media-libs/libv4l
>> required by media-tv/v4l-utils appears to build based on the current
>> kernel pointed to by /usr/src/linux. Does this mean that that always
>> needs to be recompiled for new kernels? I'd sort of assume so.
> I see no dependencies pointing to the kernel except for through
> virtual/os-headers to sys-kernel/linux-headers.
> But if a recompile is needed it will indicate it.
> Tot mails,
> Hika mailto:email@example.com
> "Zonder hoop kun je niet leven
> Zonder leven is er geen hoop
> Het eeuwige dilemma
> Zeker als je hoop moet vernietigen om te kunnen overleven!"
> De lerende Mens
> mythtv-users mailing list
> MythTV Forums: https://forum.mythtv.org
mythtv-users mailing list
firstname.lastname@example.org http://lists.mythtv.org/mailman/listinfo/mythtv-users http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org