Archive:List of MCE remote controls: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
(→‎AURC-002: split)
mNo edit summary
 
(48 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This is a (probably futile) attempt to keep up with the vast range of MCE remotes out there, and give some indication of how well they work with XBMC.
This is a (probably futile) attempt to keep up with the vast range of MCE remotes out there, and give some indication of how well they work with Kodi.


If you are adding a review please try to be as detailed as possible about the remote. For example:
If you are adding a review please try to be as detailed as possible about the remote. For example:
<ul>
  <li>What operating systems and versions of XBMC have you tested on</li>
  <li>Does the remote send keystrokes or is it MS compatible?</li>
  <li>If it's MS compatible have you tested reconfiguring it using the registry and did this work?</li>
</ul>


The article groups the Microsoft compatible (also known as eHome or RC6) remotes together first, as these are most configurable when you're using them with XBMC. Other than this there's no significance to the order of the reviews.
* What operating systems and versions of Kodi have you tested on
* Does the remote send keystrokes or is it MS compatible?
* If it's MS compatible have you tested reconfiguring it using the registry and did this work?


= eHome/RC remotes =
The article groups the Microsoft compatible (also known as eHome or RC6) remotes together first, as these are most configurable when you're using them with Kodi. Other than this there's no significance to the order of the reviews.


The remotes in this section all use the Microsoft eHome driver on Windows. See http://wiki.xbmc.org/index.php?title=Using_a_Microsoft_remote_control_in_Windows for more details. This type of remote is supported out of the box by XBMC Live.
<div class="toclimit-3">__TOC__</div>


eHome remotes are generally more expensive than the non-eHome remotes, but they are highly configurable and work very well with XBMC. Many universal handsets, for example the Harmony remotes, have emulation for eHome/RC6 handsets built in so they will work with an eHome IR receiver.
= eHome/RC remotes =
 
{{:Microsoft Media Center Remote Control}}
 
{{:AIM RC6 Media Center Remote Control}}
 
{{:HP MCE Remote}}
 
{{:HP Pavilion HDX Remote}}


{{:Asrock Remote}}
The remotes in this section all use the Microsoft eHome driver on Windows. See Using a Microsoft remote control in Windows for details.


{{:Mediagate GP-IR02BK}}
eHome remotes are generally more expensive than the non-eHome remotes, but they are highly configurable and work very well with Kodi. Many universal handsets, for example the Harmony remotes, have emulation for eHome/RC6 handsets built in so they will work with an eHome IR receiver.


{{:Mediagate MG-IR02BK}}
Note that Microsoft has modified the programming and device specification for remote controls several times. For example, in Vista, the Port Driver/Class Driver Model was added. This means that there may be some transceivers which may not function fully, if at all, on systems prior to Vista. For the curious (or bored) there is a specification for the [http://download.microsoft.com/download/0/7/E/07EF37BB-33EA-4454-856A-7D663BC109DF/Windows-Media-Center-RC-IR-Collection-Green-Button-Specification-03-08-2011-V2.pdf Windows Media Center remote].


{{:DEC-200B}}


{{:AVS Gear HA-IR01SV}}
{{:Hauppauge Media Center Remote Control Kit}}
{{:AURC-002}}
== Microsoft XBox 360 Universal Remote Control ==
[[Image:xbox_360_remote.jpg‎]]
This will work on Windows (I've tested on XP and 7) with the Microsoft receiver or a compatible receiver like the HP (the remote does not come with a receiver) though need a minor registry tweak. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da
then change the value of CodeSetNum0 to 8, and delete the three entries CodeSetNum1, CodeSetNum2, CodeSetNum3. You need to reboot for the change to take effect.
There are some buttons that aren't on the standard MS remote. The button numbers for these are:
<pre>
  28 - Open/close
  64 - XBox button
  4F - Display
  51 - Title
  68 - Blue/X
  66 - Green/A
  6C - Channel up
  6D - Channel down
</pre>
The volume and mute buttons do not work.
== Philips 5100 4in1 Vista MCE Remote ==
[[Image:philips5100-4in1 landscape.jpg]]
Philips have produced a family of remotes in this range designed for different sales regions each with different features.  This one has the ability to control 4 devices (PC, TV, Sat, Amp) and can be programmed using the manufacturer codes database supplied.  It also has the ability to learn functions from other remotes to replace any of its buttons, making it very versatile once customised to your home cinema setup.  However, the keys are not backlit. The supplied infra-red usb receiver only works with Vista, Windows 7 and Linux.
Note: Also works with the Official Microsoft MCE receiver as it sends the same signals (RC-6), meaning it can be used on Windows XP via this receiver.
Discontinued - (Can be found on ebay UK)
== Microsoft MCE Keyboard Remote ==
[[Image:Microsoftmcekeyboard.jpg‎]]
Similar to the buttons to the Microsoft MCE remote, but with a full keyboard and a 'nipple' for moving the mouse.  Range is limited and it requires a direct line of sight to the receiver.  Can be operated on the users lap. The keyboard has a very nice feel, though the mouse nipple is hard to use.
Works with the Official Microsoft MCE receiver and with compatible RC6 receivers like the HP receiver.


= Non eHome/RC remotes =
= Non eHome/RC remotes =


These remotes usually work by emulating a keyboard, that is when you press a button on the remote XBMC receives a key press just as if a key had been pressed on the keyboard. Most of the remotes emulate multimedia keyboards or send Windows Media Center keyboard shortcuts like ctrl-shift-P for Play.
These remotes usually work by emulating a keyboard, that is when you press a button on the remote Kodi receives a key press just as if a key had been pressed on the keyboard. Most of the remotes emulate multimedia keyboards or send Windows Media Center keyboard shortcuts like ctrl-shift-P for Play.
 
XBMC has all the required keyboard mappings for these remotes so they should work out of the box. However they usually cannot be configured so they have some limitations. For example, on Windows the green button will start Windows Media Center and this can't be changed without considerable messing around.
 
These remotes will work with XBMCLive as long as Ubuntu recognises them as a keyboard, which isn't always the case.
 
== VRC-1100 ==
 
[[Image:remote-VRC1100.jpg]]
 
There is no manufacturer's name on this remote or the manual, but they appear to be from Ortek (http://www.ortek.com/product.asp?pid=103&cname=Mobility). They are widely available on eBay. Maplin UK also sell an own-brand remote control (product code N18HC) that seems to be identical. The remote simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse, although it's no match for a proper mouse or trackpad.
 
Note that the the i button sends a right mouse click, which isn't much use in XBMC as the right click can't be mapped to an action. There is no way round this without using some helper app like Eventghost, but the Info action could be mapped to one of the other buttons.
 
If you want to add mappings for the four coloured keys and the four keys below them here are the entries you need in keyboard.xml. The top left (Internet Explorer) key can't be trapped.
 
<pre>&lt;t mod="ctrl,shift"&gt;Notification(Key, Yellow, 3)&lt;/t&gt; &lt;!-- Yellow button --&gt;
&lt;m mod="ctrl"&gt;Notification(Key, Blue, 3)&lt;/m&gt;        &lt;!-- Blue button --&gt;
&lt;i mod="ctrl"&gt;Notification(Key, Green, 3)&lt;/i&gt;        &lt;!-- Green button --&gt;
&lt;e mod="ctrl"&gt;Notification(Key, Red, 3)&lt;/e&gt;          &lt;!-- Red button --&gt;
&lt;o mod="ctrl"&gt;Notification(Key, u/Yellow, 3)&lt;/o&gt;    &lt;!-- Button under Yellow --&gt;
&lt;g mod="ctrl"&gt;Notification(Key, u/Blue, 3)&lt;/g&gt;      &lt;!-- Button under Blue --&gt;
&lt;t mod="ctrl"&gt;Notification(Key, u/Green, 3)&lt;/t&gt;      &lt;!-- Button under Green --&gt;
&lt;m mod="ctrl,shift"&gt;Notification(Key, u/Red, 3)&lt;/m&gt;  &lt;!-- Button under Red --&gt;</pre>
 
 
For full Linux support see http://trac.xbmc.org/ticket/8827
 
== Speedlink SL-6399 ==
 
[[Image:remote-SL6399.jpg]]
 
Cheap and cheerful remote. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX.
 
Apparently there are different usb receivers that come with the remote.
<pre>
ID 1241:1503 Belkin Keyboard      // all keys seem to work
ID 1241:e000 Belkin                // keys Start, RTV, Videos, Music, Pictures, MyTV don't work
</pre>
 
There are several extra buttons not on the standard MS remote. If you want to add mappings for
these keys here are the entries you need in keyboard.xml.
 
<pre>&lt;t mod="ctrl"&gt;Notification(Key, TV power, 3)&lt;/t&gt;          &lt;!-- TV power --&gt;
&lt;menu&gt;Notification(Key, More, 3)&lt;/menu&gt;                  &lt;!-- More --&gt;
&lt;z mod="ctrl,shift"&gt;Notification(Key, Aspect, 3)&lt;/z&gt;      &lt;!-- Aspect --&gt;
&lt;e mod="ctrl"&gt;Notification(Key, Red/Videos, 3)&lt;/e&gt;        &lt;!-- Red/Videos --&gt;
&lt;m mod="ctrl"&gt;Notification(Key, Green/Music, 3)&lt;/m&gt;      &lt;!-- Green/Music --&gt;
&lt;i mod="ctrl"&gt;Notification(Key, Yellow/Pictures, 3)&lt;/i&gt;  &lt;!-- Yellow/Pictures --&gt;
&lt;t mod="ctrl,shift"&gt;Notification(Key, Blue/MyTV, 3)&lt;/t&gt;  &lt;!-- Blue/MyTV --&gt;
&lt;g mod="ctrl"&gt;Notification(Key, Guide, 3)&lt;/g&gt;            &lt;!-- Guide --&gt;
&lt;o mod="ctrl"&gt;Notification(Key, RTV, 3)&lt;/o&gt;              &lt;!-- RTV --&gt;
&lt;f1&gt;Notification(Key, Help, 3)&lt;/f1&gt;                      &lt;!-- Help --&gt;
&lt;return mod="alt"&gt;Notification(Key, Maximise, 3)&lt;/return&gt; &lt;!-- Maximise/restore --&gt;
&lt;a mod="ctrl"&gt;Notification(Key, Radio, 3)&lt;/a&gt;            &lt;!-- Radio --&gt;
&lt;m mod="ctrl,shift"&gt;Notification(Key, DVD, 3)&lt;/m&gt;        &lt;!-- DVD --&gt;
&lt;a mod="ctrl,shift"&gt;Notification(Key, Audio, 3)&lt;/a&gt;      &lt;!-- Audio --&gt;
&lt;u mod="ctrl"&gt;Notification(Key, Title, 3)&lt;/u&gt;            &lt;!-- Title --&gt;</pre>
 
== Unbranded MCE remote ==
 
[[Image:remote-unbranded.jpg]]
 
There is no manufacturer's name on this remote or the manual, though it may be a [http://www.chinavasion.com/product_info.php/pName/pc-remote-control-media-function-remote/ Chinavasion CVSB-983] or [http://www.acowin.com.hk/product456.html Acowin AURC-001]. It can be used with Logitech Harmony Remote Software by picking Computer>>Media Center PC>>Chinavasion>>CVSB-983.
 
They are available on Ebay for as little as $2 ($10ish after S&H). It's cheap and feels a bit flimsy, but it works well enough. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse, although it's no match for a proper mouse or trackpad.
 
It isn't very configurable and certain buttons don't work as they should. For example, the fast forward and rewind buttons skip forward or backwards instead of moving gradually.
 
If you want to add mappings for the four coloured keys here are the entries you need in keyboard.xml. The other keys can't be trapped.
 
<pre>&lt;f1 mod="ctrl,alt"&gt;Notification(Key, Green, 3)&lt;/f1&gt;  &lt;!-- Green --&gt;
&lt;f2 mod="ctrl,alt"&gt;Notification(Key, Orange, 3)&lt;/f2&gt; &lt;!-- Orange --&gt;
&lt;f3 mod="ctrl,alt"&gt;Notification(Key, Blue, 3)&lt;/f3&gt;  &lt;!-- Blue --&gt;
&lt;f4 mod="ctrl,alt"&gt;Notification(Key, Yellow, 3)&lt;/f4&gt; &lt;!-- Yellow --&gt;</pre>
 
Update 16th Jan: the rewind button sends three keypresses, left, then ctrl-left, then ctrl-shift-B. The left press causes the video to jump back 30 seconds. With the later releases of XBMC the ctrl-shift-B then starts the rewind (release v9.11 ignores ctrl-keypresses).
 
Update 1st Nov 2010: Requires a minor kernel patch to support all buttons in Linux.  See patch in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607062.  Once patched, works well with Linux.
 
Update 12th June 2011: I've bought one recently. They must have changed hardware or whatever because mine works well with XBMC out of the box both on Win7 and Linux Ubuntu. Most keys are functioning correctly and 4 colored keys can be mapped by adding the following entries in keymap.xml:
<pre>&lt;keyboard&gt;
  &lt;one mod="ctrl,alt"&gt;YourAction1&lt;/one&gt; &lt;!-- Green --&gt;
  &lt;two mod="ctrl,alt"&gt;YourAction2&lt;/two&gt; &lt;!-- Orange --&gt;
  &lt;three mod="ctrl,alt"&gt;YourAction3&lt;/three&gt; &lt;!-- Blue --&gt;
  &lt;four mod="ctrl,alt"&gt;YourAction4&lt;/four&gt; &lt;!-- Yellow --&gt;
  ...
&lt;/keyboard&gt;</pre>
 
== Other unbranded MCE remote ==
 
[[File:Unbranded_remote.jpg||500px]]
 
There is no manufacturer's name on this remote or the manual, but it works very well with XBMC Dharma PVR on Windows XP Sp3. No additional software required (p.e USB drivers ). Live TV channels are showned trought Media Portal Server 1.1.3.0 installed on same computer as XBMC.
 
The Remote is MS compatible and using it is possible move mouse pointer with arrows button.
 
No reconfiguration needed. It is possible buy this remote also online website (like ebay).
 
== GoTView PC Remote ==
The GoTView PC Remote control looks exactly like the "unbranded remote" above. It is also detected as MCE remote by lircd, but has slightly different keycodes, which are incompatible with xbmc defaults.
To make things work correctly, add something like the following before the &lt;/keyboard&gt; &lt;/global&gt; lines in your /usr/local/share/xbmc/system/keymaps/keyboard.xml file
<pre>
      <one mod="ctrl,alt,shift">ContextMenu</one>
      <two mod="ctrl,alt,shift">ActivateWindow(PlayerControls)</two>
      <three mod="ctrl,alt,shift">ActivateWindow(music)</three>
      <four mod="ctrl,alt,shift">ActivateWindow(pictures)</four>
      <five mod="ctrl,alt,shift">ActivateWindow(video)</five>
      <home mod="ctrl,alt,shift">ActivateWindow(MusicPlaylist)</home>
      <r mod="ctrl">Queue</r>
      <h mod="ctrl,alt,shift">Info</h>
      <b mod="ctrl,alt,shift">ActivateWindow(MusicOSD)</b>
      <f mod="ctrl,alt,shift">ActivateWindow(VisualisationPresetList)</f>
     
</pre>
 
== Xbox 360 Wireless Controller for Windows ==
 
[[File:XBox360WirelessController.jpg]]
 
The [http://www.microsoft.com/hardware/gaming/ProductDetails.aspx?pid=090 Xbox 360 Wireless Controller for Windows], which is sold by Microsoft with a separate receiver, works with XBMC on Windows XP, Vista, 7 and with Standard Microsoft Drivers. For Linux there are  Userspace drivers available here:
[http://pingus.seul.org/~grumbel/xboxdrv/ Homepage and Binaries] or [https://github.com/Grumbel/xboxdrv/ Git-Source].
 
In order to use it properly, you should setup a [[Keymap.xml]] accordingly. This will work under Windows and Linux.
 
For Windows however there is the possibility to use an Eventclient. This Client will send the button-presses to your XBMC. There are disadvantages to this method however:
* You have to run the EventClient every time you want to use your XBMC
* It is a console-application with a window, that can disturb your experience
* The button-presses will be sent to XBMC even though it might not be in the focus (So - if you play a game for instance with your controller, the button-presses will still be sent to XBMC as well)
The EventClient can be compiled via the XBMC-Source ([https://github.com/xbmc/xbmc/tree/master/tools/EventClients/Clients/Xbox360%20Controller EventClient on Github]) or the binary '''Xbox360EventClient.exe''' is available from this [http://forum.xbmc.org/showpost.php?p=426397&postcount=11 Forum-Post] [[http://ul.to/4p5n3t Mirror]] (MD5: 4B69791B1DC2DA4400B5912CFF9EFED0).
 
== XBox DVD Remote ==
 
[[Image:Remote-xbox1.jpg]]
 
The original DVD remote for XBox 1. This is a simple well working remote, almost out of the box experience and it has a good support in xbmc.<br/ >
See [http://wiki.xbmc.org/?title=HOW-TO_wire_your_XBOX_DVD-Remote_for_USB wiring] and [http://wiki.xbmc.org/?title=Lirc_Config_for_Xbox_DVD_Remote lirc config]
 
This remote won't work "out of the box" with Windows as it doesn't send keystrokes and can't be configured to do so. It can be made to work with a helper app like Eventghost or IR Server Suite.
See http://forum.xbmc.org/showthread.php?t=45337 for the details.
 
== Flirc ==
 
Flirc is a small usb device that plugs into your computer and pairs with your same television remote. No need for another remote to clutter your table, pair once, and use forever. The best part about flirc is that it mimics a keyboard so every media center application understands it without any drivers. Flirc runs across all platforms.
 
[http://flirc.tv Flirc Website]
 
[http://farm6.static.flickr.com/5282/5686019349_761b2ab4d7_m.jpg Picture of Flirc]
 
(I don't have permissions to upload the file as an embedded picture)
 
== Original Boxee Box remote control ==
 
[http://images.gizmag.com/gallery_lrg/internettv-3.jpg picture of Boxee remote]
 
(I don't have permissions to upload the file as an embedded picture)


This remote comes with the Boxee Box from D-Link, but is also sold separately. It comes with at small USB receiver, and works out of the box as an external USB keyboard. On the front face it has navigation buttons, OK, Esc, and a Play/Pause button. On the back face, it has an almost complete QWERTY keyboard.
Kodi has all the required keyboard mappings for these remotes so they should work out of the box. However they usually cannot be configured so they have some limitations. For example, on Windows the green button will start Windows Media Center and this can't be changed without considerable messing around.
[[Category:Remote]]

Latest revision as of 02:22, 10 September 2020

This is a (probably futile) attempt to keep up with the vast range of MCE remotes out there, and give some indication of how well they work with Kodi.

If you are adding a review please try to be as detailed as possible about the remote. For example:

  • What operating systems and versions of Kodi have you tested on
  • Does the remote send keystrokes or is it MS compatible?
  • If it's MS compatible have you tested reconfiguring it using the registry and did this work?

The article groups the Microsoft compatible (also known as eHome or RC6) remotes together first, as these are most configurable when you're using them with Kodi. Other than this there's no significance to the order of the reviews.

eHome/RC remotes

The remotes in this section all use the Microsoft eHome driver on Windows. See Using a Microsoft remote control in Windows for details.

eHome remotes are generally more expensive than the non-eHome remotes, but they are highly configurable and work very well with Kodi. Many universal handsets, for example the Harmony remotes, have emulation for eHome/RC6 handsets built in so they will work with an eHome IR receiver.

Note that Microsoft has modified the programming and device specification for remote controls several times. For example, in Vista, the Port Driver/Class Driver Model was added. This means that there may be some transceivers which may not function fully, if at all, on systems prior to Vista. For the curious (or bored) there is a specification for the Windows Media Center remote.


Non eHome/RC remotes

These remotes usually work by emulating a keyboard, that is when you press a button on the remote Kodi receives a key press just as if a key had been pressed on the keyboard. Most of the remotes emulate multimedia keyboards or send Windows Media Center keyboard shortcuts like ctrl-shift-P for Play.

Kodi has all the required keyboard mappings for these remotes so they should work out of the box. However they usually cannot be configured so they have some limitations. For example, on Windows the green button will start Windows Media Center and this can't be changed without considerable messing around.