Reply to thread

Message: <blockquote data-quote="rsenden" data-source="post: 661472" data-attributes="member: 24295">Hi,I'm unfamiliar with both the Audio Renderer Changer (ARC) Plugin and the original MCE remote, but I'll try to answer some of your questions.KeyboardInputPlugin (KBIP) only intercepts regular keypresses. Most MCE remote clones 'emulate' a regular keyboard for most or all button presses, so you can use KBIP to map those buttons to MediaPortal actions and such. Seeing your description, I guess the original MCE remote doesn't emulate key presses for most buttons. As such, this remote is not supported by KBIP unfortunately.Although not related to KBIP (and as such replies should go to the ARC thread and/or PM); if I remember correctly the standard remote mapping contains a 'Key Pressed' action. Depending on how the ARC Plugin detects keystrokes, you may be able to map a remote button to a 'Key Pressed' event that is in turn handled by the ARC Plugin.Another option is to map a remote button to the ARC window, if it indeed has a window as described earlier in this thread. KBIP allows you to select custom plugin windows in the setup screen, the standard MP remote mapping unfortunately doesn't AFAIK. However, you could try to manually edit the corresponding XML file to add the correct window. First map the button that you want to assign to ARC to an existing MP window using MP Setup, then edit the XML file (%AppData%\Team MediaPortal\MediaPortal\InputDeviceMappings\custom\Microsoft MCE.xml from the top of my head) by changing the cmdproperty attribute for that button to the window id that was posted earlier. Note that this is unsupported and may or may not work, and may cause the MP Remote setup screen to cease functioning or delete your customized mapping file. As such, first set up all other buttons of your remote, then try the above, and make a backup of the original and modified file.Kind regards,Ruud</blockquote>

Verification