Perplexing (but serious) problems with MCE remote

[sub]

Its really just a matter of available time. Learning IR signal via the MCE remote is actually quite a complex task, and already consumed far more development/testing time than I would have like to. I do hope to improve the process with more checks, along the lines of what you describe above, but I dont know when I'll get to it.

[ricklous]

For clarification on the HIP front, the problem ive mentioned on the threads is one with the alternative driver for the MCE2005 remote not seeming to have any power management built into it. When my PVR resumes to record a scheduled program, it leaves the screen switched off. you can't bring the screen to life by pressing the remote when using the 3rd party driver, but you can with the eHome one. So my setup currently uses the eHome driver to generate the up/down/left/right/enter from the remote, and HIP with the MCE plugin to generate all the other keys and do my STB channel changing with the codes i taught it when i had the alternative driver loaded. HIP only needs the alternative driver to learn new codes, so once youve done that you can switch back to the eHome driver.

I would agree that its better to try and limit the amount of software you have loaded but HIP offers so many options and flexibility, to me its the perfect compliment to GBPVR, and I find it as stable as GBPVR itself. for example, you can use HIPs scheduler to automatically switch your TV and STB to standby when the PC enters suspend, and switch them back on when it resumes, which wins points in my green-minded-WAF tally

The hardest part is definatly the teaching of codes though. Its a bit of a black art that took me a while to master. Persistence and patience is definatly the biggest skills needed in that department!

[pwborders]

Sub:
I can surely see what you mean about time and how to spread it between the different aspects of this program. Personally I don't see where you ever found the time to have a baby.

In reality I was hoping for someone to volunteer to write an external utility to help in the learning process. It should be pretty straight forward and if it took a few command line arguements it could even be called from config in place of the internal learning code. Just pass it the directory to store the codes in and a switch saying it was called by config so that it could behave accordingly.

Ricklous:
Sorry about the misspell of your username before. So HIP will output with the ehome driver but not record, that is interesting. Do the recordings from HIP for your STB look like the recordings that config makes? It would be nice if they did since they can be made with the ehome driver installed as long as the right dll is in the directory with the recording program. That is how I made mine for the internal IR blaster support, using MCEIrRec.exe, and it worked great. With your current half HIP setup do you still have gbpvr set to MCEremote? Does HIP get the codes before it does or do you have problems with duplicate codes? I really would appreciate a little more information on your current half HIP setup, if there is another thread just let me know where. Thanks.

[ricklous]

Do the recordings from HIP for your STB look like the recordings that config makes?

i dont know, sorry. i havnt tried using the config option as i got hip working 100% and didnt want to change things around too much from what worked.

With your current half HIP setup do you still have gbpvr set to MCEremote? Does HIP get the codes before it does or do you have problems with duplicate codes?

no i have it set to 'default(Hauppauge)'. I may well be wrong (im not a programmer...) but my understanding of the eHome from various postings is that it generates a mix of keyboard commands and commands that are specificly for MCE. the keys that generate keyboard commands still act on GBPVR regardless of what remote you have the config set to, and regardless of weather HIP is loaded or not. the MCE ones (the majority) are ignored if 'MCE Remote' isnt selected in the GBPVR config. i have HIP set up with the MCE Plugin, and all keys are mapped, but the ones that generate keyboard commands are left with a blank output and the ones that generate MCE commands are mangled into GBPVR commands and output to GBPVRs window. so GBPVR receives the keyboard commands directly from the eHome driver and the rest via HIP. I posted my config file here if it helps:
http://forums.gbpvr.com/showpost.php?p=1...ostcount=4

[sub]

You should set the remote type back to default if you're using HIP.

[pwborders]

Ricklous:

Thanks for the update, I guess I may try HIP one day but since everything is working for now I will probably wait a little. Have to make another backup of the system.


One more little question. As I understand since HIP sends directly to the window instance it can send commands to a window that doesn't have th focus but what about the MCE keys (arrows and enter)? Have you tried things with the gui not having focus? That is one of my greatest annoyances, at least once a week I have to go back to where the computer is and click on the gui so that I can control it because I left the computer without remembering to click on the gui. I use the computer as a computer sometimes (like now) and always have to remember to click the gui as the last thing before putting it to sleep.

[ricklous]

yeah the ones coming directly from the eHome driver go to whatevers in focus. I get around this by using HIPs Master Controller. you define a button on your remote to bring it up (I use *) and it appears regardless of whats in focus. its a OSD that allows you to switch to (or load if it isnt already) one of the programs HIP is configured to use, or shut down/restart your PC, etc. Quite useful...