MCE 2005 remote, mute issue, double button press

[Wakalaka]

"No remote" would effectively be the same as selecting the 'Default (Hauppauge)' option. With this setting, its only expecting keyboard events. Your problem of course is that the eHome drivers actually generate keyboard events and GB-PVR has no idea these keys have come from a remote. For example, when you press the 'up' navigation button on your remote, Windows just puts "up key pressed" message on to GB-PVRs input message queue.

The only way I could NOT handle those is by ignoring any keyboard events. (which is a change I wont be making)

When I selected the Hauppauge as my remote, GB-PVR would hang at the main menu and wouldn't respond to mouse or keyboard. If that option only responds to keyboard, and Event Ghost picks up the MCE remote and then posts keyboard events to GB-PVR, then that would work. GB-PVR doesn't need to know that the keyboard event originally came from a remote, does it?

[sub]

When I selected the Hauppauge as my remote, GB-PVR would hang at the main menu and wouldn't respond to mouse or keyboard.

I cant think of a single reason the keyboard wouldnt work for you with this option. This is the default setting everybody gets when they installed GB-PVR, and I'm not aware of anyone that hasnt been able to use the keyboard.

You seem to have some bizarre input problems on your setup.

The only difference between this option and the 'MCE Remote' option is that the MCE option also listens for some extra non-keyboard, and when received will post a fake keyboard event on the message queue. If you press a standard keyboard type key like 'up' this should be processed exactly the same regardless of what remote setting you have selected.

If that option only responds to keyboard, and Event Ghost picks up the MCE remote and then posts keyboard events to GB-PVR, then that would work.

Correct, but as I said the MCE drivers usually result in keyboard events being put on the message queue for the foreground app, so if both the MCE drivers and Event Ghost submit keyboard events, then it'll appear to respond as though the button was pressed twice. I dont know if the alternative driver solves this problem for you.

GB-PVR doesn't need to know that the keyboard event originally came from a remote, does it?

Correct.

[Wakalaka]

I rebooted my system and GB-PVR seems to be happy with Hauppauge set as the remote now. I also reinstalled the HIP replacement driver, and everything is behaving well with Event Ghost and GB-PVR. I still have the problem of live tv muted and no buttons respond, even though I see them get processed by Event Ghost. They're sent to GB-PVR, but the channel doesn't change.

[sub]

I still have the problem of live tv muted and no buttons respond, even though I see them get processed by Event Ghost.

Thats got to be something funky that just happens on your machine, otherwise there would be tons of compaints about it. I've never seen a single other comment about having this problem.

[Wakalaka]

Which leads me to want to reinstall GB-PVR from scratch to see if the problem goes away. Wish I could have GB-PVR dump a log of keyboard events so I could see what happens after Event Ghost posts the keyboard event.

[sub]

Wish I could have GB-PVR dump a log of keyboard events so I could see what happens after Event Ghost posts the keyboard event.

Sorry, I'm not in a position to help you with this until the next release. My build is no longer compatible with GB-PVR v0.99.12, so I cant provide you a patch that adds this.

[Wakalaka]

Sorry, I'm not in a position to help you with this until the next release. My build is no longer compatible with GB-PVR v0.99.12, so I cant provide you a patch that adds this.

Totally understandable. The fact that you're even actively helping on the forums is enough for me. If you ever get a chance on some version to do it, that would be awesome.