Using an MCE remote - Revision history

Karellen at 10:05, 19 July 2020

2020-07-19T10:05:10Z

← Older revision		Revision as of 10:05, 19 July 2020
Line 24:		Line 24:
	this article the articles above will make more sense.		this article the articles above will make more sense.

	~~If you haven't yet bought a remote there are some reviews in the article~~
	~~[[Remote Control Reviews]].~~

	Media Center remotes are obviously designed to work with Microsoft		Media Center remotes are obviously designed to work with Microsoft
Line 106:		Line 104:
	mappings for the myriad of extra buttons on a typical MCE clone remote.		mappings for the myriad of extra buttons on a typical MCE clone remote.
	In that case see [[Using an MCE remote control in Windows]] for		In that case see [[Using an MCE remote control in Windows]] for
	an introduction, or go straight to [[Modifying keyboard.xml]]		an introduction, or go straight to [[HOW-TO:Modify_keymaps\|Modifying keyboard.xml]]
	if you want to jump straight in and start modifying the key		if you want to jump straight in and start modifying the key
	mappings.		mappings.

	[[Category:Remotes]]		[[Category:Remotes]]

Ned Scott: Ned Scott moved page Using an MCE remote in XBMC to Using an MCE remote

2015-05-05T23:44:19Z

Ned Scott moved page Using an MCE remote in XBMC to Using an MCE remote

← Older revision	Revision as of 23:44, 5 May 2015
(No difference)

NedBot: Robot: Substituting template: Name

2014-06-05T20:18:32Z

Robot: Substituting template: Name

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

2014-06-05T01:19:33Z

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

Ned Scott: Ned Scott moved page Using a remote control with XBMC to Using an MCE remote in XBMC

2014-04-11T21:07:20Z

Ned Scott moved page Using a remote control with XBMC to Using an MCE remote in XBMC

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

Ned Scott at 08:41, 2 December 2011

2011-12-02T08:41:13Z

← Older revision		Revision as of 08:41, 2 December 2011
Line 1:		Line 1:
			{{incomplete}}
			{{cleanup}}
	Note: this article assumes you are using XBMC v10.0 Dharma or a later		Note: this article assumes you are using XBMC v10.0 Dharma or a later
	version. Earlier versions of XBMC such as v9.11 Camelot do not support key modifiers		version. Earlier versions of XBMC such as v9.11 Camelot do not support key modifiers

>NedBot: Robot: Changing Category:Remote to Category:Remotes; cosmetic changes

2011-09-26T12:27:47Z

Robot: Changing Category:Remote to Category:Remotes; cosmetic changes

← Older revision		Revision as of 12:27, 26 September 2011
Line 49:		Line 49:
	<ol>		<ol>
	<li>The remote can send an IR code like the Microsoft remote. To use		<li>The remote can send an IR code like the Microsoft remote. To use
	the remote an application has to link to the IR driver.<br> </li>		the remote an application has to link to the IR driver.<br /> </li>

	<li>The remote can send the Windows message WM_APPCOMMAND. This		<li>The remote can send the Windows message WM_APPCOMMAND. This
	message is used to send a multimedia application messages like "Play",		message is used to send a multimedia application messages like "Play",
	"Pause", "Stop" etc. To use this type of remote an application has to		"Pause", "Stop" etc. To use this type of remote an application has to
	process the WM_APPCOMMAND messages.<br> </li>		process the WM_APPCOMMAND messages.<br /> </li>

	<li>The remote can simulate multimedia key presses when you press a		<li>The remote can simulate multimedia key presses when you press a
Line 60:		Line 60:
	keyboard, which has extra keys for multimedia functions like "Play"		keyboard, which has extra keys for multimedia functions like "Play"
	etc. To use this type of remote an application has to process the		etc. To use this type of remote an application has to process the
	multimedia keypresses.<br> </li>		multimedia keypresses.<br /> </li>

	<li>Finally the remote can simulate the standard MS Media Center		<li>Finally the remote can simulate the standard MS Media Center
Line 108:		Line 108:
	mappings.		mappings.

	[[~~category~~:~~Remote~~]]		[[Category:Remotes]]

>Jhsrennie: /* ... and how to solve it */

2010-11-29T08:06:53Z

... and how to solve it

← Older revision		Revision as of 08:06, 29 November 2010
Line 82:		Line 82:

	Ironically the official MS remote will not work with XBMC out of the		Ironically the official MS remote will not work with XBMC out of the
	box. This is because it uses IR codes i.e. type 1 in the list above,		box, or rather it will partially work: some buttons will work while others won't.
			This is because the MS remote uses IR codes i.e. type 1 in the list above,
	and XBMC does not support this. The good news is that the MS remote is		and XBMC does not support this. The good news is that the MS remote is
	easily reconfigured to work as a type 4 remote instead. This is covered		easily reconfigured to work as a type 4 remote instead. This is covered

>Jhsrennie at 08:04, 29 November 2010

2010-11-29T08:04:59Z

← Older revision		Revision as of 08:04, 29 November 2010
Line 34:		Line 34:
	controllers using software called Lirc. Assuming there is a Linux		controllers using software called Lirc. Assuming there is a Linux
	driver for your remote controller you can configure Lirc to use it with		driver for your remote controller you can configure Lirc to use it with
	XBMC~~. Details are in the Linux article above~~. Note that XBMCLive is		XBMC. Note that XBMCLive is
	already configured to work with the official MS remote. Sadly, on		already configured to work with the official MS remote. Sadly, on
	Windows the situation is a lot more confused.		Windows the situation is a lot more confused.

>Jhsrennie at 09:40, 15 October 2010

2010-10-15T09:40:12Z

← Older revision		Revision as of 09:40, 15 October 2010
Line 1:		Line 1:
	Note: this article assumes you are using ~~the beta of the~~ Dharma ~~release~~		Note: this article assumes you are using XBMC v10.0 Dharma or a later
	or a later ~~build (strictly speaking any build later than 26407)~~. Earlier		version. Earlier versions of XBMC such as v9.11 Camelot do not support key modifiers
	versions of XBMC such as v9.11 Camelot do not support key modifiers
	like control, shift and alt so the key mappings required for Media Center		like control, shift and alt so the key mappings required for Media Center
	Remotes will not work.		Remotes will not work.

← Older revision		Revision as of 20:18, 5 June 2014
Line 1:		Line 1:
	{{incomplete}}		{{incomplete}}
	{{cleanup}}		{{cleanup}}
	Note: this article assumes you are using ~~{{name}}~~ v10.0 Dharma or a later		Note: this article assumes you are using XBMC v10.0 Dharma or a later
	version. Earlier versions of ~~{{name}}~~ such as v9.11 Camelot do not support key modifiers		version. Earlier versions of XBMC such as v9.11 Camelot do not support key modifiers
	like control, shift and alt so the key mappings required for Media Center		like control, shift and alt so the key mappings required for Media Center
	Remotes will not work.		Remotes will not work.
Line 75:		Line 75:
	== ... and how to solve it ==		== ... and how to solve it ==

	The good news is that from build 26407 onwards ~~{{name}}~~ has support		The good news is that from build 26407 onwards XBMC has support
	built in for remote controllers of types 2, 3 and 4. This includes the		built in for remote controllers of types 2, 3 and 4. This includes the
	vast majority of the cheap MCE remotes, so the basic functions like		vast majority of the cheap MCE remotes, so the basic functions like
Line 83:		Line 83:
	[[Using an MCE remote control in Windows]].		[[Using an MCE remote control in Windows]].

	Ironically the official MS remote will not work with ~~{{name}}~~ out of the		Ironically the official MS remote will not work with XBMC out of the
	box, or rather it will partially work: some buttons will work while others won't.		box, or rather it will partially work: some buttons will work while others won't.
	This is because the MS remote uses IR codes i.e. type 1 in the list above,		This is because the MS remote uses IR codes i.e. type 1 in the list above,
	and ~~{{name}}~~ does not support this. The good news is that the MS remote is		and XBMC does not support this. The good news is that the MS remote is
	easily reconfigured to work as a type 4 remote instead. This is covered		easily reconfigured to work as a type 4 remote instead. This is covered
	in the article [[Using a Microsoft remote control in Windows]].		in the article [[Using a Microsoft remote control in Windows]].

← Older revision		Revision as of 01:19, 5 June 2014
Line 1:		Line 1:
	{{incomplete}}		{{incomplete}}
	{{cleanup}}		{{cleanup}}
	Note: this article assumes you are using ~~XBMC~~ v10.0 Dharma or a later		Note: this article assumes you are using {{name}} v10.0 Dharma or a later
	version. Earlier versions of ~~XBMC~~ such as v9.11 Camelot do not support key modifiers		version. Earlier versions of {{name}} such as v9.11 Camelot do not support key modifiers
	like control, shift and alt so the key mappings required for Media Center		like control, shift and alt so the key mappings required for Media Center
	Remotes will not work.		Remotes will not work.
Line 75:		Line 75:
	== ... and how to solve it ==		== ... and how to solve it ==

	The good news is that from build 26407 onwards ~~XBMC~~ has support		The good news is that from build 26407 onwards {{name}} has support
	built in for remote controllers of types 2, 3 and 4. This includes the		built in for remote controllers of types 2, 3 and 4. This includes the
	vast majority of the cheap MCE remotes, so the basic functions like		vast majority of the cheap MCE remotes, so the basic functions like
Line 83:		Line 83:
	[[Using an MCE remote control in Windows]].		[[Using an MCE remote control in Windows]].

	Ironically the official MS remote will not work with ~~XBMC~~ out of the		Ironically the official MS remote will not work with {{name}} out of the
	box, or rather it will partially work: some buttons will work while others won't.		box, or rather it will partially work: some buttons will work while others won't.
	This is because the MS remote uses IR codes i.e. type 1 in the list above,		This is because the MS remote uses IR codes i.e. type 1 in the list above,
	and ~~XBMC~~ does not support this. The good news is that the MS remote is		and {{name}} does not support this. The good news is that the MS remote is
	easily reconfigured to work as a type 4 remote instead. This is covered		easily reconfigured to work as a type 4 remote instead. This is covered
	in the article [[Using a Microsoft remote control in Windows]].		in the article [[Using a Microsoft remote control in Windows]].