|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
Problem learning Hauppauge remote codes
How many of you have tried to teach the Hauppauge silver remote codes to a learning remote? Ever run into problems where the learning remote seems to be sending double button presses?
From a previous thread, I learned that the Hauppauge IR software recognizes just about any RC5 codes. That part works no problem -- you really can send any RC5 code & have it act upon it. But, the RC5 spec uses a toggle bit that alternates on repeated presses of the same button. (It gets reset when you press a different button.) This can be a problem when you teach the button code to another remote, since it may only learn 1 state of the toggle bit. The MX-700, for example, cannot learn RC5 codes & use the toggle bit -- it will only send the 1 setting that it learned. (RC5 codes preprogrammed into the remote for specific devices work properly -- so you can set device Philips VCR code #067, modify irremote.ini to recognize system 5 codes, & button presses work as they should.) So? Why is that a problem? The Hauppauge IR software appears to pay attention to the toggle bit. When it notices that a 2nd button press has arrived & that the toggle bit hasn't changed, it thinks that it missed a button press & generates another button code to make up for the 'missed' one. If you want to see that in action, try using the original silver remote's up arrow on the SageTV main menu. Alternate pressing the up arrow & pressing it while you cover the emitter. You should begin to see 2 up arrow results on the menu for each single button press when the emitter is uncovered. I'm not sure which is worse -- that the expensive MX-700 is unable to learn these codes properly, or that the Hauppauge software uses that toggle bit instead of ignoring it like it ought to. - Andy |
#2
|
||||
|
||||
I thought I read a post where a user was having the same issue. They found out if they redid the learning with just a short tap on the Hauppague remote that they were able to get rid of this issue. Not sure though.
Gerry
__________________
Big Gerr _______ Server - WHS 2011: Sage 7.1.9 - 1 x HD Prime and 2 x HDHomeRun - Intel Atom D525 1.6 GHz, Acer Easystore, RAM 4 GB, 4 x 2TB hotswap drives, 1 x 2TB USB ext Clients: 2 x PC Clients, 1 x HD300, 2 x HD-200, 1 x HD-100 DEV Client: Win 7 Ultimate 64 bit - AMD 64 x2 6000+, Gigabyte GA-MA790GP-DS4H MB, RAM 4GB, HD OS:500GB, DATA:1 x 500GB, Pace RGN STB. |
#3
|
||||
|
||||
Yeah, I remember some such comment in the past, but I wasn't able to find it in a search this time. I did try the quick tap method... and long hold, and... I even programmed codes in directly via Pronto files. If it is really the toggle bit as I mentioned, none of these should do anything, since the remote simply can't send the toggled version for a learned command. It would need a double learning mode -- learn the first press & then learn a 2nd press. If same: keep only 1; if different, alternate the signal sent. The newest remotes that Home Theater Master announced can do that. (URC-200, URC-300)
But, I would still like to find that thread if you happen to remember where it is or more details to search for. - Andy |
#4
|
||||
|
||||
__________________
Big Gerr _______ Server - WHS 2011: Sage 7.1.9 - 1 x HD Prime and 2 x HDHomeRun - Intel Atom D525 1.6 GHz, Acer Easystore, RAM 4 GB, 4 x 2TB hotswap drives, 1 x 2TB USB ext Clients: 2 x PC Clients, 1 x HD300, 2 x HD-200, 1 x HD-100 DEV Client: Win 7 Ultimate 64 bit - AMD 64 x2 6000+, Gigabyte GA-MA790GP-DS4H MB, RAM 4GB, HD OS:500GB, DATA:1 x 500GB, Pace RGN STB. |
#5
|
||||
|
||||
Thanks -- I missed that one in my search, but do remember seeing it because it was a continuance of a really old thread & I took note of that quick-press learning technique. The brief tapping does take care of the fact that you could otherwise have several button codes sent on every button press if you learn from one long key press, but it doesn't seem to get around the toggle bit problem, at least on the MX-700. I'll go follow-up with a reply to "eggs", out of curiosity of what happens when a key is pressed twice in a row.
- Andy |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|