X10 remote issue: Multiple commands with 1 button press (1 Viewer)

forza11

Portal Member
September 26, 2010
22
2
MediaPortal Version: 1.1
MediaPortal Skin: standard
Windows Version: windows xp sp3

I'm using the X10 remote from Medion. Everything works great except for the directional buttons. One press results in multiple commands being send to MP, so it's quite a challenge to select the right show/option.

Weird thing is that when i deselect the 'X10 remote' under remote settings in the config panel, these directional buttons work great. However, the other commands on the remote stop working, so this is not really an option.

any ideas?
 

alexdepalma

MP Donator
  • Premium Supporter
  • January 31, 2008
    540
    493
    Home Country
    Spain Spain
    Some times that also happened to me. I have various remotes. If I select MCE and X10 remote this used to happen. Also if you have MCE included in your windows (remote working as key press). My solution is to manually assign an unused key code to the arrow movements in "X10.xml" (this name may varie depending of your personal selection in remotes) The file can be found in C:\ProgramData\Team MediaPortal\MediaPortal\InputDeviceMappings if you hit "Learn" in "Remote" menu of MP Configuration.

    Something like this


    <button name="Up" code="019">
    <action layer="0" condition="WINDOW" conproperty="2007" command="ACTION" cmdproperty="31" sound="click.wav" />
    <action layer="0" condition="*" conproperty="-1" command="ACTION" cmdproperty="3" sound="cursor.wav" />
    </button>
    <button name="Down" code="012">
    <action layer="0" condition="WINDOW" conproperty="2007" command="ACTION" cmdproperty="30" sound="click.wav" />
    <action layer="0" condition="*" conproperty="-1" command="ACTION" cmdproperty="4" sound="cursor.wav" />
    </button>
    <button name="Left" code="013">
    <action layer="0" condition="WINDOW" conproperty="2007" command="ACTION" cmdproperty="29" sound="click.wav" />
    <action layer="0" condition="*" conproperty="-1" command="ACTION" cmdproperty="1" sound="cursor.wav" />
    </button>
    <button name="Right" code="011">
    <action layer="0" condition="WINDOW" conproperty="2007" command="ACTION" cmdproperty="28" sound="click.wav" />
    <action layer="0" condition="*" conproperty="-1" command="ACTION" cmdproperty="2" sound="cursor.wav" />
    </button>
    <button name="Ok" code="015">
    <action layer="0" condition="WINDOW" conproperty="11" command="ACTION" cmdproperty="47" sound="click.wav" />
    <action layer="0" condition="WINDOW" conproperty="10" command="ACTION" cmdproperty="10" sound="back.wav" />
    <action layer="0" condition="WINDOW" conproperty="2007" command="ACTION" cmdproperty="105" sound="click.wav" />
    <action layer="0" condition="*" conproperty="-1" command="ACTION" cmdproperty="7" sound="click.wav" />
    </button>


    I added a "0" in front of the code="xx"

    This code is not recognised by MP but is used by the remote driver as key press.

    I'm almost sure it will work for you.


    Alex
     

    Users who are viewing this thread

    Top Bottom