under vista, the MCE remote isn't registering

[zeflash]

I've installed it under XP on the same machine, and it works.
Using the latest setup (1024) with the latest update on top of it.
Any idea of what I could do? Weirdly the first time I booted vista, the mce remote driver was in error (code 37), and I had to disable / enable it again to make it work.

Any idea of what I could do? Anyone has it working in vista?

[Bitmonster]

Did you use the alternative driver under XP?

I've read somewhere at http://www.team-mediaportal.com/ that the old alternative driver is not working under Vista, but they have compiled a new build for Vista.

[zeflash]

Nope, I'm using the system driver. my XP is a MCE edition. And in Vista it's also detected automatically.

[Bitmonster]

Sorry, I currently don't have Vista (but I hope this will change soon), so I can't try it out. Has the eHome driver for the MCE remote properly installed itself in the device manager?

[zeflash]

Yes, I tried again today and the remote was behaving properly inside vista - yet evenghost still didn't register MCE events like it does in XP.

I'll guess I'll wait

[zeflash]

If I try to install the alternative driver (provided it works in vista), would the events then be registered ?
I could try I know, but if someone already tried it would save me some install time

[zeflash]

Ok, so in the end I did install the updated MCE driver for vista ... and it works!

*but* (well yeah everything's not perfect) I have issues with "bouncing" events. When I hit the down button on the remote once, I only get one event (which is expected).
If I hit the button twice quickly, like a double click, then I get 3 events somehow. Which makes navigation in lists a bit weird, with the selection that goes down or up 2 by 2 or even 3 by 3 sometimes (depends on the timing of my presses).

Now of course, I tried to change the timeout value in the MCE plugin - but it doesn't seem to change a thing. If I lower it then I get double events more often, if I increase it it seems to be a bit better but not perfect yet (I haven't try huge values like 1 secondes though - but I went up to 0.6 seconds I think, without getting rid of the problem).

Another bug that I noticed when tweaking this MCE time value; whenever I get in the configuration dialog and out, I have to restart eventGhost, as it's not registering the MCE events anymore.

[Bitmonster]

Is there any .DLL file in the new alternate driver package? Possibly called "MceIr.dll"?

[zeflash]

yes there is, along with mceir.sys.

[Bitmonster]

You can try to replace the dll in the plugin directory:
Eventghost/plugins/MceRemote

[zeflash]

I tried to replace the DLL from evenghost to the one of the alternate driver. It didn't seem to change anything - when I change the timeout value of the MCE plugin in evenghost, I still need to restart evenghost (events aren't registered anymore), and I still get double or triple events.

I used Bartman suggestion's from another thread, adding a Wait for 0.10s and a flush event afterwards. That kinda works even though in that case I can't queue multiple key presses.

Yet I think I can tell what's happening there. At some point, I put a ridiculously high timeout value in the MCE remote plugin, something like 1 second.
If I press a key once, and wait for 1 second, then press the key again, everything's fine.
If I press a key once, and while the plugin's waiting for the timeout, I press the same key again, this is where I get duplicated events. The more keys I press while waiting for the first timeout, the more duplicates I'll get.

That's quite noticeable on keys I use for toggle something on-screen - if at some point I click too fast, then I keep getting double events, which lead to either showing / hiding the OSD or showing / hiding it.

[Bitmonster]

I have rewritten the MCE plugin in 0.3.6.1045.

It takes another approach to identify the events. It might fix the duplicates, but it also might introduce new problems.

So try it out and report your findings.

[zeflash]

Thank you so much! It now works, no more double events
Ahhhh that's so cool !!
That's what I call a fast turnaround on a bug report

you rule.