Windows Media Center MCE remote in Win 10 in 5 easy steps

Tutorials & Guides
jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Fri Aug 18, 2017 3:11 pm

Before you start going through my tutorial, I thought It would be helpful to explain exactly what you will be doing to your computer, and why you will be doing it, and how your system will be different if you upgraded to Windows 10 rather than doing a fresh install of Windows 10. If you upgraded your machine from WIndows 7, your system is likely to still have the ehome infrastructure. To check, simply look in your device manager for the ehome drivers. With a fresh install of Windows 10 without the upgrade, these drivers will not exist. This tutorial was tested using the Win 10 Creator's update, and EG version 0.5.0 rc4, and took about 15 minutes to test. Without going into great detail, I'll start with an overview of what you need to accomplish in order to get your MCE remote working, and then provide a specific how to afterwards:

OVERVIEW

Step 1. Disable driver signing enforcement
Driver signing is a way for Microsoft to verify developers aren’t planting malware in their driver packages. Although this does add some measure of security to Windows, all a signed driver is really saying is that it has gone through some approval process on the part of Microsoft. If a driver is not signed, it does not mean it’s a virus or the driver will not work, it just means the developer for whatever reason hasn’t gone through that process. For more on driver signing and security look here: https://www.osr.com/blog/2015/03/18/mic ... indows-10/

Step 2. Install your IR sensor (This usually involves just plugging it in!!)

Step 3. Install EventGhost version 0.5.0 rc4 from here: http://eventghost.net/downloads/
Because development builds change often, and eventually get wrapped up into a release version its safe to say that when EG v 0.5 is released as a stable version you can just download that. While making this tutorial I used the EG as a service version but the latest development build should be sufficient

Step 4. Add the generic HID plugin
Event ghost is just the platform, and in order for it to accomplish any work you need add your desired capabilities to the program. These come in the form of plugins, and this architecture is what helps make EG light weight, and flexible.

Step 5. Create your macros and enjoy!!

HOW TO

Now that you know what your doing and why your doing it, it only makes sense that I should go a step further and explain how to do all of this (The driver disabling tutorial has been shamelessly stolen from Kgschlosser)

Step 1 - Disable driver signing enforcement

*****This will restart the computer right after pressing enter*****
First, the computer has to be restarted in the so-called "Options" menu. This is easiest to do with the "Run" dialog. Which is opened by means of the key combination Win + R. The command to boot into the Options menu is as follows:

Code: Select all

shutdown.exe /r /o /f /t 00
Nobody likes to carry out orders, of which he does not know what they are doing. Therefore, the explanation of the individual parameters:
Shutdown.exe - Is a Windows standard program that can shut down and reboot the computer in various ways
/ R - means: Restart
/ O - means: The computer should start in the Options menu
/ F - means: to restart directly and to close all programs automatically
/ T 00 -means the time in seconds until the restart is performed. In this case 0 seconds - ie immediate restart.

-In the first menu, click the "Troubleshooting" button. In the second menu screen, click the "Advanced Options" button.

-In the "Advanced Options", go to "Start Settings". Click the "Restart" button.

-After restarting the computer you land in the startup settings. Several options are available here, which are selected by pressing the numeric key. We need the option 7 - "Disable the driver signature" - to install unsigned drivers on Windows 1After another restart from the startup settings, you can now also install unsigned drivers in Windows via the device manager.

Step 2 - Plug In your Infrared Receiver

Step 3 - Install EventGhost

Step 4 - Installing the generic HID plugin

4.1 To add the HID plugin from within EG click on configuration located towards the top of the EG window, and click add plugin.
4.2 Scroll down until you see the Input Devices folder, under which you should see Generic HID. Double click on this. The generic HID plugin reads the Microsoft HID service, and lists all the devices that run using the HID service. HID stands for Human Interface Device, and it is basically anything you use to control your PC from your voice, to a mouse, to whatever other method you can think of. You should see about 4 entries that look something like this:

@hidserv.inf%hid_device_system_consumer%;HID-compliant consumer control device

Your IR receiver is actually the combination of 4 HID devices which all look similar but have small differences in their names. Either way, the device that is listed above is the one you’re going for so go ahead and double click that one to add it. If you’re not sure which one you need, then add all of the devices that start with @hidserv.inf%hid. The worst thing that will happen is you will see extra log data that you cannot use for your macros, and you can delete the plugins you don’t need later.

Step 5 – Create your macro

Press a button on your MCE remote, and look for the short, 2 or 3 digit code that is generated, NOT the longer codes that will be there if you added the extra HID devices. You should not use these because they change each time you press a button. In order to have your MCE button presses cause an event, drag the log code from the logging box into the macro you have created. To be clear about which event your looking for, I have created this log snippet that shows an example of the events generated when I press the next button on my MCE remote. In this example I’ve pressed next twice and the HID.Button.179 event is generated with each button press, along with the longer HID.Button event that we don’t need. The shorter event stays consistent between button presses while the longer code changes after a few button presses
Example
HID.Button.179
HID.Button.1+13+228+255+255+20+4+15+128+32+3+248+255+255
HID.Button.1+13+228+255+255+20+4+15+128+32+3+248+255+255
HID.Button.179
HID.Button.1+13+228+255+255+20+132+15+128+32+3+248+255+255
HID.Button.1+13+228+255+255+20+132+15+128+32+3+248+255+255

And that's all there is to it but if your still stuck or don't understand, or even need screenshots then speak up, and someone will be glad to help
Last edited by jachin99 on Mon Jun 04, 2018 4:26 pm, edited 6 times in total.

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Sat Oct 21, 2017 2:40 pm

EDIT: Over time some users have reported different issues with get their remotes using this exact method. As they find other ways to solve their problems I'll be posting their solutions here so that you all can have one go to thread for your remotes. Here they are...

Arcadeguy had trouble getting Irman working via a usb serial port adapter on Win 10. His solution was to install WinLIRC and use the LIRC plugin. Link: viewtopic.php?f=2&t=9899

tzr916 could not get his Generic HID device to generate a unique string. He used HID.Button*22* as a log entry instead. Link: viewtopic.php?f=2&t=9783&p=47720&hilit=tzr916#p47720
Last edited by jachin99 on Mon Jun 04, 2018 4:21 pm, edited 1 time in total.

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Mon Dec 11, 2017 4:03 pm

There has been some confusion about exactly which MCE plugin will get your remote working so I wanted to make a note about the differences between them. EventGhost currently ships with three different plugins with MCE in the name, and here are the differences between them

MCE: This plugin is under software control, and it is meant to send commands to Windows Media Center. This plugin will not help you control external programs with a given remote.

Microsoft MCE remote: Located under input devices in the add plugin window, this plugin was designed to receive events from MCE remotes that do not use the ehome driver. From kgschlosser...
ok quick rundown. the MCE remote is for Windows XP. and it has nothing to do with the ehome drivers. The way XP remotes worked is via keyboard emulation. The MCE remote for windows vista+ uses the Microsoft ehome drivers which does not use keyboard emulation but instead does a translation of the IR codes. the reason why the alternate MCE IR service has to be installed is because it acts like a man in the middle and grabs those IR codes as they are being passed from the driver to Windows.
Microsoft MCE Remote (Vista +): Also located under input devices in the add plugin menu, this is NOT the plugin used for the above tutorial. Microsoft redesigned how Windows received remote input in Vista, and Windows 7. IF YOU INSTALL THIS PLUGIN, SOME REGISTRY KEYS WILL BE DELETED, AND WINDOWS WILL NO LONGER "SEE" YOUR REMOTE PRESSES. EventGhost will see them so they will still show in your log, and you can control your desired program via the appropriate plugin. If your still using Windows Media Center, it will not react unless you restore these registry keys. This was implemented on the plugin as a way to avoid double key presses. Restoring these registry keys will fix your remote in WMC, and still pass your keypresses to EG, and its plugins, allowing you to retain external IR device control in EG.

Code: Select all

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da]
"CodeSetNum0"=dword:00000001
"CodeSetNum1"=dword:00000002
"CodeSetNum2"=dword:00000003
"CodeSetNum3"=dword:00000004

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57db]
"CodeSetNum0"=dword:00000001
"CodeSetNum1"=dword:00000002
"CodeSetNum2"=dword:00000003
"CodeSetNum3"=dword:00000004
Each of the two MCE plugins located under input devices require you to alter or install some service. For the older XP plugin, you are prompted to disable the HID service, which might cause some of your other input devices to not function properly. For the Vista + plugin you are required to install the Alt. IR service. I haven't seen problems with the Alt. IR service interfering with other input devices. I hope this clears things up a bit but if not, ask questions and i will try to provide more details in the clearest manner possible.
Last edited by jachin99 on Mon Jun 04, 2018 4:19 pm, edited 2 times in total.

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Sun Jan 07, 2018 4:53 am

////SUGGESTED HARDWARE///
These are known good IR Receiver/Blaster combos and remote that other users have reported success with in the past using Windows 7 and the Windows Visa+ plugin. If you wish to add to this list, please reply to this thread, and I will add it. Include the OS, Tell is if you had to disable driver signing enforcement for Windows 10, and let us know if which remote/receiver combo your using, along with any plugins you have used. I'll start.

Generic (B003EGXEUU ?) Dell MCE remote///Microsoft eHome tranciever with Radio Shack Blaster///Windows7///MCE Vista+ Plugin, MCE Plugin,
This remote produces short, unique codes in the EG log for each button press.

Dell Gyration Remote//Built-in Sony VGX XL201 Reciever//Windows 7 Pro 32 bit//Vista+ Plugin, Generic HID Plugin. This combination produces HID Codes in the log, and controls external equipment Via IR & Wifi
Last edited by jachin99 on Tue Feb 20, 2018 2:21 pm, edited 1 time in total.

blaher
Experienced User
Posts: 481
Joined: Thu Nov 17, 2011 1:27 am

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by blaher » Sun Jan 07, 2018 6:32 am

jachin99 wrote:
Fri Aug 18, 2017 3:11 pm

Step 4. Add the generic HID plugin
What is the reason for adding this plug-in, instead of just the Microsoft MCE Remote (Vista +) one?

MceRemote.Mce.Skip instead of HID.Button.179 with the generic plug-in, seems easier to me.

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Sun Jan 07, 2018 6:40 pm

Depending on what hardware and operating system one might be using this might be necessary to get remote events to show up in the log. Windows ten doesn't have ehome, and I'm guessing all remote support was removed from the OS.

blaher
Experienced User
Posts: 481
Joined: Thu Nov 17, 2011 1:27 am

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by blaher » Mon Jan 08, 2018 3:49 am

Ah, I see, that's interesting. I have Windows 10, and I also have an ehome device under device manager.

It's an HP infrared sensor, for what it's worth.

https://i.imgur.com/QOFi8aT.png

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Mon Jan 08, 2018 1:22 pm

Those drivers probably installed when you plugged yours into the PC. Unless someone had Windows Media Center on their Win 7 or 8 PC and upgraded to ten the ehome folder won't be there. This tutorial is kind of a test run, and I'm glad to get some feedback. If enough others chime in that they are successful then I might take out the Generic HID step. IR hardware that doesn't use ehome might need something like either generic HID or a specific plugin for their gear. I can't install EG on my test machine right now or else I would try this out on my own.

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Tue Feb 20, 2018 2:17 pm

blaher wrote:
Sun Jan 07, 2018 6:32 am
jachin99 wrote:
Fri Aug 18, 2017 3:11 pm

Step 4. Add the generic HID plugin
What is the reason for adding this plug-in, instead of just the Microsoft MCE Remote (Vista +) one?

MceRemote.Mce.Skip instead of HID.Button.179 with the generic plug-in, seems easier to me.
I am thinking Generic HID will cover more devices. The MCE Vista+ plugin will interfere with some programs receiving IR codes where I have not seen this behavior out of Generic HID. I use both because the Vista+ plugin sends IR blasts.

User avatar
kgschlosser
Site Admin
Posts: 3796
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by kgschlosser » Tue Feb 27, 2018 7:21 am

if the remote states that is for Windows Vista MCE then the MCE Remote Vista plugin will work without problems. If you have a remote that does not state this then you may have to use a serial connection to the remote. In some rare cases there are remotes that will use both the old XP MCE (key stroke emulation) as well as the new (eHome drivers) this is usually for advanced remotes. then you would need to install both the old and the new style MCE plugins. if you have a remote where some of the button presses work with the MCE Vista plugin but not all of them. and adding the XP MCE plugin does not help. then you can try using the HID plugin. There are some remotes that will only work with their drivers and a new plugin would have to be created for this remote specifically, the ATI Remote Wonder is one of these remotes.
If you like the work I have been doing then feel free to Image

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Tue Feb 27, 2018 3:34 pm

Another clarification, i have observed, and it has been brought up before, that adding the Vista+ MCE plugin intercepts IR signals, and there fore prevents Windows Media Center from receiving them. Under normal use cases, this isn't a big issue because when using the remote to control kodi for instance, you would have to link log events to kodi actions in EG anyway. For me, I have to re-link IR controls to WMC via the MCE plugin found under SOFTWARE CONTROL. This is only for IR codes, and I have not had to do this for my Gyration RF remotes because they do not use IR (So their signals aren't being intercepted by Vista+)

User avatar
kgschlosser
Site Admin
Posts: 3796
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by kgschlosser » Tue Feb 27, 2018 5:22 pm

it's not an IR thing. it's not using the MCE Vista ehome drivers. the remote uses a combination of keyboard emulation and mouse emulation. that is the reason why it works in XP as well. if you install the keyboard plugin you should see key combinations when you press the buttons on the remote.
If you like the work I have been doing then feel free to Image

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Wed Mar 21, 2018 9:44 pm

I'm going to try out one of these speakercraft emitters: https://www.bestbuy.com/site/speakercra ... Id=6081157
The price is outrageous but it is supposed to disperse the IR better. I'm having trouble with my current emitter and the TV in one room, and I think its just because the emitter is weak, or there is too much light on the reciever because it is behind the TV screen. I would run the emitter inside of the TV cabinet but I need to place it across the room to control other devices. With my current setup sometimes the emitter controls the TV, sometimes it doesnt.

User avatar
kgschlosser
Site Admin
Posts: 3796
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by kgschlosser » Thu Mar 22, 2018 12:19 am

I can tell you how to build one that is guaranteed to work.

you would need to buy this

https://www.mouser.com/ProductDetail/DF ... IQQAvD_BwE

and you will need an old set of headphones. ones with the 1/8" (3.5mm) plug on it.
and an old USB cable (for power)

you can connect this to your blaster and it will transmit IR about 35 feet.

it sounds like what you issue is has nothing to do with the emitter (ir led) but it is more of a distance issue. with the cable it's self. You are getting to much voltage drop.

There is one other solution but would require you to open up your device locate the ir receiver. cut the led off the blaster and use the 2 wires inside if it and attach directly to the receiver inside of the device.
If you like the work I have been doing then feel free to Image

jachin99
Experienced User
Posts: 455
Joined: Sat Feb 13, 2016 8:39 pm

Re: Windows Media Center MCE remote in Win 10 in 5 easy steps

Post by jachin99 » Thu Mar 22, 2018 1:16 pm

I'll try it out, send me some instructions

Post Reply