[WINDOWS] HOW-TO use MCE remote in XBMC under Windows the easy way - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: XBMC General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: Windows support (/forumdisplay.php?fid=59)
+---- Thread: [WINDOWS] HOW-TO use MCE remote in XBMC under Windows the easy way (/showthread.php?tid=78179)
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112
similar - badokun - 2011-04-16 17:02
Looks pretty similar...
elitegamer360 Wrote:There are so many clones around the world and I can tell you if you are not careful you can get the wrong hardware pretty easy.
- elitegamer360 - 2011-04-16 18:06
badokun Wrote:Looks pretty similar...
Thank you for posting the picture, I just wanted to find out if there is any thing weird that might impact the functiuonality of the Remote. All Looks good on paper but it does not work in real life!!!
I see that you have "HID Non-User Input Data Filter (KB 911895)" If I am not mistaken this relates to your "Microsoft USB Dual Receiver" for a wireless Keyboard/mouse. Does it operate on an RF or IR signals?
I think it should not have any impact on your remote but just for the sake of testing, could you try and restart your PC without the "Microsoft USB Dual Receiver" plugged in. Just make sure the Remote's IR usb receiver is plugged in and reboot. See if that makes any difference at all!
Without pluging the Microsoft USB Dual receiver try and apply the original remote settings then reboot and use Showkey to find out if the remote sends any signal. If not try and apply my registry settings Restart again and try showkey.
I forgot to ask you, what type of HTPC are you using? does it have an onboard IR receiver by any chance?
- LazarusLong - 2011-04-17 18:30
OK folks, I have an odd one...
I am running Windows 7 (32-bit) with XBMC and have a "Pinnacle" branded Windows MCE remote. On the back of the remote it says "RC6". No branding on the front of the remote. The receiver is branded "Pinnacle".
I can't get it recognized at all in XBMC and ShowKeys is also not recognizing it. However, I did download IR Server Suite and installed it and it was able to see buttons being pressed on the remote. Couldn't figure out how to get XBMC to work however, so I uninstalled it.
In Device Manager I do see the eHome listed under HID and also USB.
Any ideas ??
EDIT: This is the exact remote I have: http://www.amazon.com/Pinnacle-Remote-Windows-Media-Center/dp/B000WR2E00/ref=pd_sxp_grid_i_2_2
- elitegamer360 - 2011-04-17 22:07
LazarusLong Wrote:OK folks, I have an odd one...
You seem to have a similar problem to badokun, honstly this is the second time I hear about a remote that has the eHome driver but does not act as an RC6 remote instead its more like an ENE CIR HID!
I've researched about this and the only explanation is that it lists the eHome driver as a dummy driver some how! And the hardware actually uses an INTEL CIR Driver thats based on the "HID-compliant consumer control device" only.
$39.95 for a fake MCE remote is quite expensive, its a rip-off actually! I usually read reviews before buying anything and with the amount of 1 star reviews this is a NO buy for me!! There is no simple way to figure out the type of the remote before buying unless they come from a branded manufacturer which they usually list the specifications of their products accurately.
Well it looks like the fake eHome remotes will not be programmable and will only work on the default settings exactly like the cheap cloned MCE remotes that does not have the right hardware built-in to use the "Microsoft eHome Infrared Transceiver". The other explanation that I can think off is that Microsoft Certified remotes for Windows XP will not work on new releases of Windows, in a similar way the new Hardware Certified for Windows Vista or Windows 7 will not work on XP. I'm saying that because I've seen this happen so many times which makes it a reasonable explanation, some people might differ, but I say with quality RC6 hardware it will not matter what Operating system you use.
So one should be careful when buying remotes, I think if you use Windows XP it is better to buy a remote that is fully certified by Microsoft (Designed for Microsoft Windows XP Media Center Edition) like your "Pinnacle" remote. And if you have Vista or above then stay away from any remote certified for use with Windows XP. I've had another thread were people reported remotes that did not work with Windows XP etc, etc... But I have never seen or heared about any one having a problem when buying an RC6 device certified for their proper Operating system.
This is my only logical explination that I can think of at this time!
- LazarusLong - 2011-04-18 03:54
elitegamer360 Wrote:You seem to have a similar problem to badokun, honstly this is the second time I hear about a remote that has the eHome driver but does not act as an RC6 remote instead its more like an ENE CIR HID!
Actually, I only paid $ 12.99 for it from Woot.com (back in 2008 when I had Vista). It worked fine with Vista MCE back then, but doesn't work in MCE under Windows 7 either. 'Course, it could be because I'm still running the Windows 7 Release Candidate (never actually purchased the retail release LOL).
I think the issue is probably that the translation in the registry is incorrect so I'm going to do some poking around there.
I'm just honestly surprised how well XBMC runs on my ancient PC (Dell P4, 2.0 Ghz). I think this thing is about 6 years old!
- LazarusLong - 2011-04-18 04:53
LazarusLong Wrote:Actually, I only paid $ 12.99 for it from Woot.com (back in 2008 when I had Vista). It worked fine with Vista MCE back then, but doesn't work in MCE under Windows 7 either. 'Course, it could be because I'm still running the Windows 7 Release Candidate (never actually purchased the retail release LOL).
Well, I was able to get everything working using EventGhost for now. Would still love to have it work "natively", but this will do for the time being. I've been using the Android app also and it actually works faster anyways!
- xm41907 - 2011-04-19 04:54
First off, I have two concerns. The Reg file causes my remote to stop working. I have to uninstall it to get functionality.
Now for the background. I recently upgraded my computer from xp to Win7 and am having trouble getting the remote to work correctly. I have a Mediagate GP-IR02BK and it was working great with Event Ghost. After the upgrade it's giving me troubles.
Mmany of the basic functions worked right away, but I can not view movie details/info when pushing the info button. I tried to install Event Ghost and copy my XBMC file to it. The file didn't work at all. None of my functions were found. So I tried the MCE addon and was able to get my back button working right (I prefer it to have escape functionality instread of backspace), but still no luck with the info button.
SO, that brought me to the Reg fix. I've tried it multiple times. With the Keyboard.xml file and without. Every time, after I install it and reboot, I loose the remote functions and have to uninstall to get it back.
Anyone else having issues with the reg file causing a malfunction or know of a work around for the info button?
- elitegamer360 - 2011-04-19 10:33
As we know the "Mediagate GP-IR02BK" known to be a good MCE remote, I know couple of people used it with no issues at all!
Are you using the usb receiver that came with you remote or something else?
Have you checked what drivers your receiver uses in Windows 7? Does it use the eHome Driver? I have a picture posted about this a couple of posts back please check it out.
EDIT: what config.reg did you use v1.24 or v1.25?
If you used v1.25 please try v1.24 and let me know if it makes any difference!
- xm41907 - 2011-04-19 13:30
elitegamer360 Wrote:@xm41907:Elite, yes I'm using the original receiver. It worked great under xp/EventGhost. It is using the Ehome driver. That's what I had to uninstall and reinstall to get working again after merging v1.25. I'll try v1.24 tonight. One thing I notice late last night was that the default registry entries look nothing at all like entries in v1.25. There are no key entries at all. I'm wondering if my remote uses a different scheme than the common one and keeps the key entries somewhere else. I'll try v1.24 tonight and report back. Also, I'll post the default registry entry for your info.
It doesn't really matter as I just won a Logitech Harmony 650 on Ebay for $35. I can live with the half functioning remote for a few more days.
- elitegamer360 - 2011-04-19 18:37
xm41907 Wrote:Elite, yes I'm using the original receiver. It worked great under xp/EventGhost. It is using the Ehome driver. That's what I had to uninstall and reinstall to get working again after merging v1.25. I'll try v1.24 tonight. One thing I notice late last night was that the default registry entries look nothing at all like entries in v1.25. There are no key entries at all. I'm wondering if my remote uses a different scheme than the common one and keeps the key entries somewhere else. I'll try v1.24 tonight and report back. Also, I'll post the default registry entry for your info.
I've asked you to try v1.24 because its been downloaded over 5000 times and no one reported issues. Only issues are being reported after I updated to v1.25 which is worrying! I do not know if its a coincidence or is there actually something wrong with v1.25, although I tested it on 5 different systems before releasing but I learnt this not even enough lol!
You are the third user in a row who's reporting issues with your setup, if you try v1.24 and it works then its my fault and I wil need to revise v1.25.
EDIT: every time someone posts about an issue I forget to ask them about Eventghost because I never use it! Now in Eventghost you might have "Disable HID Service" checked, you need to enable it again by unchecking this option!