Archive:List of MCE remote controls - Revision history

Karellen at 02:22, 10 September 2020

2020-09-10T02:22:44Z

@@ Line 13: / Line 13: @@
 = 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.
+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.
@@ Line 19: / Line 19: @@
 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].
 = Non eHome/RC remotes =
@@ Line 52: / Line 26: @@
 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.

Karellen: Karellen moved page List of MCE remote controls to Archive:List of MCE remote controls without leaving a redirect: Not used, not needed

2020-09-10T02:21:38Z

Karellen moved page List of MCE remote controls to Archive:List of MCE remote controls without leaving a redirect: Not used, not needed

← Older revision	Revision as of 02:21, 10 September 2020
(No difference)

Karellen at 08:20, 21 July 2020

2020-07-21T08:20:01Z

← Older revision		Revision as of 08:20, 21 July 2020
Line 60:		Line 60:
	{{#lst:GoTView PC Remote\|summary}}		{{#lst:GoTView PC Remote\|summary}}

	~~{{#lst:Emprex 3009ARF\|summary}}~~

	[[Category:Remotes\|*]]		[[Category:Remotes\|*]]

Karellen at 01:13, 17 June 2020

2020-06-17T01:13:10Z

← Older revision		Revision as of 01:13, 17 June 2020
Line 53:		Line 53:
	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.		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.


	~~{{#lst:VRC-1100\|summary}}~~

	{{#lst:Speedlink SL-6399\|summary}}		{{#lst:Speedlink SL-6399\|summary}}

Ned Scott: xbmc -> kodi

2019-10-21T22:20:50Z

xbmc -> kodi

← Older revision		Revision as of 22:20, 21 October 2019
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:
Line 7:		Line 7:
	* If it's MS compatible have you tested reconfiguring it using the registry and did this work?		* 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 ~~XBMC~~. Other than this there's no significance to the order of the reviews.		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.

	<div class="toclimit-3">__TOC__</div>		<div class="toclimit-3">__TOC__</div>
Line 13:		Line 13:
	= eHome/RC remotes =		= 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~~. This type of remote is supported out of the box by Kodi Live~~.		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 ~~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 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 [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].		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].

Ned Scott: /* Non eHome/RC remotes */ some lingering XBMC to Kodi replacement text

2019-10-21T22:19:33Z

Non eHome/RC remotes: some lingering XBMC to Kodi replacement text

← Older revision		Revision as of 22:19, 21 October 2019
Line 51:		Line 51:
	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.		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.		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.

	~~These remotes will work with XBMCLive as long as Ubuntu recognises them as a keyboard, which isn't always the case.~~

	{{#lst:VRC-1100\|summary}}		{{#lst:VRC-1100\|summary}}

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:41:36Z

Bot: Automated text replacement (- XBMC + Kodi )

← Older revision		Revision as of 08:41, 4 May 2015
Line 3:		Line 3:
	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:

	* What operating systems and versions of ~~XBMC~~ have you tested on		* What operating systems and versions of Kodi have you tested on
	* Does the remote send keystrokes or is it MS compatible?		* 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?		* If it's MS compatible have you tested reconfiguring it using the registry and did this work?
Line 13:		Line 13:
	= eHome/RC remotes =		= 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. This type of remote is supported out of the box by ~~XBMC~~ Live.		The remotes in this section all use the Microsoft eHome driver on Windows. See [[Using a Microsoft remote control in Windows]] for details. This type of remote is supported out of the box by Kodi Live.

	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 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.
Line 49:		Line 49:
	= 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.		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.

NedBot: Robot: Substituting template: Name

2014-06-05T20:18:38Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:18, 5 June 2014
Line 3:		Line 3:
	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:

	* What operating systems and versions of ~~{{name}}~~ have you tested on		* What operating systems and versions of XBMC have you tested on
	* Does the remote send keystrokes or is it MS compatible?		* 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?		* If it's MS compatible have you tested reconfiguring it using the registry and did this work?
Line 13:		Line 13:
	= eHome/RC remotes =		= 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. This type of remote is supported out of the box by ~~{{name}}~~ Live.		The remotes in this section all use the Microsoft eHome driver on Windows. See [[Using a Microsoft remote control in Windows]] for details. This type of remote is supported out of the box by XBMC Live.

	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 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.
Line 49:		Line 49:
	= 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 ~~{{name}}~~ 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 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.

	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.		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.

NedBot: Bot: Automated text replacement (- XBMC + {{name}} )

2014-06-05T01:09:36Z

Bot: Automated text replacement (- XBMC + {{name}} )

← Older revision		Revision as of 01:09, 5 June 2014
Line 3:		Line 3:
	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:

	* What operating systems and versions of ~~XBMC~~ have you tested on		* What operating systems and versions of {{name}} have you tested on
	* Does the remote send keystrokes or is it MS compatible?		* 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?		* If it's MS compatible have you tested reconfiguring it using the registry and did this work?
Line 13:		Line 13:
	= eHome/RC remotes =		= 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. This type of remote is supported out of the box by ~~XBMC~~ Live.		The remotes in this section all use the Microsoft eHome driver on Windows. See [[Using a Microsoft remote control in Windows]] for details. This type of remote is supported out of the box by {{name}} Live.

	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 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.
Line 49:		Line 49:
	= 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 {{name}} 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.		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.

Ned Scott: Ned Scott moved page Remote control reviews to List of MCE remote controls

2014-04-11T21:08:59Z

Ned Scott moved page Remote control reviews to List of MCE remote controls

← Older revision	Revision as of 21:08, 11 April 2014
(No difference)

← Older revision		Revision as of 08:20, 21 July 2020
Line 60:		Line 60:
	{{#lst:GoTView PC Remote\|summary}}		{{#lst:GoTView PC Remote\|summary}}

	~~{{#lst:Emprex 3009ARF\|summary}}~~

	[[Category:Remotes\|*]]		[[Category:Remotes\|*]]