MCE remote issues

[wasson]

First off, let me just say that this software is awesome. It does everything I hoped it would do, and requires very little trouble shooting to get it working.

I bought an MCE remote and it worked with GBPVR right out of the box... but only for some functions. Up/down/left/right seemed to work okay, but the other buttons were hit or miss as to their functionality. I think I have an older/less featured version of the remote or something.

I'd heard that I should download HIP, as that would intercept my remote signals and I could assign them keystrokes instead. I set it up this way, and it's working great! Well, except that now every time I hit a key, the program reads it as hitting the key twice. If I hit channel up, it goes up 2 channels. Same for every button.

Obviously this wasn't an issue when I wasn't using HIP and simply using the built-in MCE functions. I assume HIP is at fault, but I could find very little trouble shooting info on the net about them at all, much less this problem specifically.

I'd like the best of both worlds, obviously. The reliability of the built-in MCE functions as well as the functionality of the HIP keyboard stroke replacement stuff. Any ideas?

[venger]

Hey Wasson,

I came across the same pb when i first set up my mce remote with HIP...

Did you replace the MCE driver with the 'special' one designed to work with HIP?
Well.. I didn't replace the XP-builtin driver for the remote since I didn't need access to the blasters.. and I wanted to fiddle as little as possible...

The trouble is when you use the existing XP-builtin driver, both XP and HIP start to process your IR commands. I can't confirm this but my guess is: for each IR command you send from your remote, TWO keystrokes are being generated (one by XP, and the other by HIP).

So the workaround is simply:
Do not define HIP actions for IR commands that are already processed by XP (eg UP, DOWN, etc)

have fun :0)