Hauppauge receiver now responds to EVERY remote in house! (1 Viewer)

[HappyTalk]

On MediaPortal 2.0.0.4 it was pretty annoying when pressing volume on the TV that mediaportal would respond as if menu had been pressed on haup remote! this was the only remote key that did it. However now with latest SVN's it is reponding to EVERY single remote in the house (usually as number key 0 or delete button!). The final straw was today when buttons on the projector remote caused mediaportal to respond and actually DELETE a movie file off the hard drive! I immideatly ran various unerase utilities BUT the file simply no longer exists. So not only did it delete the file it ensured 100% that it is unrecoverable.

I will file a bug report some time soon, but don't have time at the moment. I posted here to see if anyone else is getting this bizarre madness? For now I have to revert to 2.0.0.4 and avoid using volume on tv. I will also have to create read only shares for music and movies so as mediaportal does not have write access as it's just too dangerous.

 

[pirlone]

exactly the same problem here!
i expirience this prob for a long time now so i almost get use to it, but it's definetly a big problem. i try to put haupp receiver away from tv so it can't respond to other remote comands but it's real pain in the a**
somehow I can't believe it's mediaportal svn's issue, I blame it on hauppauge.
anyway, soon i'll replace this remote with mce remote and hope to leave this story behind...

rgs,
pirlone

 

[HappyTalk]

somehow I can't believe it's mediaportal svn's issue, I blame it on hauppauge.
pirlone

NO IT IS Mediaportal if you re-read my post this is clear. I stated that with 2.0.0.4 it occurs but only with the tv remote volume control. With later svn's it occurs with EVERY button of every remote in the house so something in the code must have changed to accentuate the problem. It's as if an unknown keypress is instead of being ignored it is triggering a '0'. I can flick between different MP versions and clearly see the difference. Also the Hauppuage remote worked 100% OK when it was used with MythTV or with it's own software. As I understand it you used to have to run the IR Haup program but this was no longer required as of v2.0.0.0 (i think) presumably as internal code was handling the driver communications?

 

[mPod]

That's quite funny.

Extract the appended XML file (depending on you having a 34- or 45-button remote) to your "InputDeviceMappings/custom" directory. This should solve your problem.

The problem seems to have come up because the 21-button remotes have been added lately. And those codes match your other remote control's codes. The appended XML files have been stripped off the other unneeded remotes.

 

[HappyTalk]

OK That helped with recent SVN. Other remotes stopped triggering it but TV remote sends a '9' now for EVERY button. So I just removed it thus:-

No need to download above files. Just run MP Config and go to remote | hauppauge | press mapping button. Remove the other 2 remotes leaving just the one you use (in my case by removing 35 and 21, just leaving 45 button one). Then go to the entry for the 9 button on the remaining remote, select 'All Layers' and again press the remove button.

I now no longer have any problems. I also no longer have a 9 button but It's easier to live with that as I channel change via the guide and never jump to exact time points in videos so '9' will not be missed. It would be nice to know though if codewise, 9 is being used as a default for any unrecognised BUT acknowledged remote press so is triggering as a fall through, rather than being ignored as it should be.

Cheers for help mpod - things nearly got broken yesterday when MP deleted a file!

 

[mPod]

Nope, there's nothing special about the "9" button.

 

[HappyTalk]

As an update I wanted to play sudoko which needed the 9 key, so I reinstated the 9 key and just set it to inactive in TVFullScreen/TVGuide/Fullscreen Video/Fullscreen Music/DVD is Playing/TVOSD which seems to solve it for now.