More > JRiver Media Center 22 for Linux

Some remote control help, if you please.

<< < (4/4)

blgentry:
You seem to be very negative about this; almost like you are trying to talk yourself out of this solution.  Choose as you will of course.

FLIRC is universal.  It works on all platforms.  I'm relatively certain I could make MC with FLIRC on Linux work exactly like it works for me on Mac.

Good luck to you.

Brian.

raymondjpg:

--- Quote from: blgentry on July 05, 2017, 07:32:40 pm ---You seem to be very negative about this; almost like you are trying to talk yourself out of this solution.  Choose as you will of course.

FLIRC is universal.  It works on all platforms.  I'm relatively certain I could make MC with FLIRC on Linux work exactly like it works for me on Mac.

Good luck to you.

Brian.

--- End quote ---

I was mistaken, if FLIRC works on all platforms then it would be a possible solution for a Linux implementation of JRiver MC.

I am not trying to talk myself out of anything, I am always looking for alternatives to Windows!

blgentry:
Don't get me wrong:  FLIRC requires quite a bit of configuration to get it right.  FLIRC "pretends" to be a USB keyboard.  So what the system sees are key presses.  So it's a two step process:

1) Map your remote control keys to keyboard keys using the FLIRC tool.  This gets saved into the FLIRC itself.
2) Configure MC to respond to the keyboard keys you have mapped above.

I think I mapped something like 10 or 12 keys that MC already understood, and then custom mapped another 5 or 6 for various things that MC did not do "out of the box".  Things like going directly to the Playing Now screen in Theater view.

This took me a few days of experimentation, on and off.  But the end result seems to work pretty well.

Brian.

raymondjpg:

--- Quote from: blgentry on July 06, 2017, 06:36:13 am ---Don't get me wrong:  FLIRC requires quite a bit of configuration to get it right.  FLIRC "pretends" to be a USB keyboard.  So what the system sees are key presses.  So it's a two step process:

1) Map your remote control keys to keyboard keys using the FLIRC tool.  This gets saved into the FLIRC itself.
2) Configure MC to respond to the keyboard keys you have mapped above.

I think I mapped something like 10 or 12 keys that MC already understood, and then custom mapped another 5 or 6 for various things that MC did not do "out of the box".  Things like going directly to the Playing Now screen in Theater view.

This took me a few days of experimentation, on and off.  But the end result seems to work pretty well.

Brian.

--- End quote ---

Thanks for the tips. I did order a FLIRC Version 1 yesterday to test in Linux Mint. I saw that there was also a Version 2 available, but no indication anywhere as to what differences there may be between the two versions.

Navigation

[0] Message Index

[*] Previous page