2009-03-17, 18:28
The only way to get xbmc to be responsive to remote commands when cycling through menu's is to use the Microsoft MCE remote and the Microsoft Drivers. By default the microsoft driver maps the up,down,left,right, buttons which are sluggish with other methods (this is a problem with the way eventghost, IRbox ect work.). I personally then map the other buttons like play and stop etc.. using eventghost - these buttons do not need to be held down to scroll through menus and work fine when mapped.
It is down to the fact that the remote sends three kinds of ir code to windows depending on how long you press the button down.
short press - one movement down
Medium press - constant movement down the list
Long press - fast movement down the list
This is then interpreted by the microsoft MCE driver as if you were holding down the arrow keys on your keyboard. The Microsoft driver seems to do this with much more intelligence than is possible with programs like eventghost.
So in effect, you have two systems in place:
- Microsoft MCE remote driver handling the arrow keys like a keyboard would on xbmc.
- Eventghost mapping the rest of the buttons (play, stop etc...) to xbmc using the event server.
It is down to the fact that the remote sends three kinds of ir code to windows depending on how long you press the button down.
short press - one movement down
Medium press - constant movement down the list
Long press - fast movement down the list
This is then interpreted by the microsoft MCE driver as if you were holding down the arrow keys on your keyboard. The Microsoft driver seems to do this with much more intelligence than is possible with programs like eventghost.
So in effect, you have two systems in place:
- Microsoft MCE remote driver handling the arrow keys like a keyboard would on xbmc.
- Eventghost mapping the rest of the buttons (play, stop etc...) to xbmc using the event server.