Hauppauge Remote Program Codes
VAT) each, Buy 4 for 16.66€ incl. VAT (14.00€ excl. Taxi2gate mmmx p3d v4.
The SageTV-provided EPG server has been shut off. For more information, see these topics:For continued EPG data, it is suggested to sign up for, then use the built-in found in SageTV version 9.To clear this message, click the red X in the upper left corner.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. Well, I ran Win10 updates today, rebooted and my Hauppauge IR remote does not work any more.When I set my STV9 to Show STV Commands linked to Infrared, there is no activity from my remote. Keyboard is accepted just fine.When I try to manually restart ir.exe, I get 'Found IR Controller (e2)' in a small window.I tried to update WinTV to version 8, no effect. I played with various versions of irremote.ini, no effect.There is a batch file IRquad.bat in WinTV directory now. I ran it and it returned 'Sorry, no valid IR device found'.Any help would be greatly appreciated.ThanksFrank.
Could someone please help me to troubleshoot Hauppauge IR remote? I am posting here as this is not a HW problem. Relevant HW works as it is supposed to.I have two Colossus cards.
IR sensor is plugged into one of them. The setup worked for years.After upgrade to STV 9, installation of July MS updates and several reboots the remote stopped working.I tried to install WinTV8, no change, reverted back to WinTV7.I have another smaller STV 7 machine that works just fine. I tested both remotes there. I copied existing ir.exe and irremote.ini from STV7 machine to STV9 machine. No change.Current status: Only page up/down works on remote. 2 or 3 other keys cause random actions (not the intended ones).
All other keys are dead.In Setup.Detailed Setup.Commands.Show SageTV Commands only one key shows: Menu as ALT. Other keys are either ignored or cause an escape from this screen.
Functioning PageUp/Down does not show either.I am at the end of my wits. To control STV from a remote keyboard is possible but very awkward. The same for remote mouse.Could please someone advise on how to capture what is the machine getting from the remote, or how to log the whole communication?Should I try to re-install STV9?Any other advice would be greatly appreciated.ThanksFrank. The Hauppauge ir receiver uses a program called ir.exe that gets installed by the Hauppauge installation software. It gets put in the Windows startup folder so it should start automatically when you start Windows.
The Hauppauge ir receiver uses a program called ir.exe that gets installed by the Hauppauge installation software. It gets put in the Windows startup folder so it should start automatically when you start Windows. Oh, do you have more than 1 Hauppauge device on the same PC? Hauppauge only supports using IR on 1 device. There is no way to tell it which one you want to use either. I think it usually goes with whatever was installed last.Yes, I have two (as stated in the OP).
Hauppauge Remote Program Codes 2017
However IR sensor is connected to one of them only and is used as a receiver for the remote. This setup worked for many years.What you wrote explains why when I plug the sensor into the other Colossus, the remote is completely dead.The fact that some keys on the remote work, albeit weirdly, would suggest that the HW path is OK. The problem lies in the way the keys are interpreted in the SW. What I am trying to figure out is where the corruption occurs. As I replaced both ir.exe and irremote.ini with the ones from the working machine, it must be something else.Except Hauppauge drivers, what else is in the SW chain of IR commands processing?Where does STV get the remote info (codes) from exactly? Yes, I have two (as stated in the OP). However IR sensor is connected to one of them only and is used as a receiver for the remote.
This setup worked for many years.What you wrote explains why when I plug the sensor into the other Colossus, the remote is completely dead.The fact that some keys on the remote work, albeit weirdly, would suggest that the HW path is OK. The problem lies in the way the keys are interpreted in the SW. What I am trying to figure out is where the corruption occurs. As I replaced both ir.exe and irremote.ini with the ones from the working machine, it must be something else.Except Hauppauge drivers, what else is in the SW chain of IR commands processing?Where does STV get the remote info (codes) from exactly?Make sure you only have one Irremote.ini which should usually in only in the windows folder.from herescroll down get basicirremote-iniNewRemote.zip from Opus4 postyou want copy the basicirremote-iniNewRemote.zipclose IR32Copy over Irremote.ini restart IR32.