Two Click Remote Stall? (45-button Hauppauge)

[pat.holder]

Hi,

So here's the rundown. I have a PVR-150 with the 45-button remote. I had windows XP pro, and I recently upgraded to Vista. When I did, I made sure to get the newest hauppauge CD (v2.7) and I installed the latest IR.exe file (2.45). When I run the debug.txt file, I get reproducible input of remote commands.

Here's the catch: in Sage (for which I used the "SageCommands" file from Opus4), I can get fine response from inputing text commands, but the remote only works for two presses of any particular button, then it stalls. I can use any OTHER button after that (again, for up to two presses), but if I try the same button again I get no response. Once I've pressed a second button, the original becomes useable again, but not before that.

Any ideas? Is there a debug output I can look at somewhere? I'm pretty stumped.

Oh, also, I've already played with the registry setting for repeat rate with no luck.

Many thanks to anyone who can brainstorm what's going on!

[Opus4]

How is the ini sending commands to SageTV? Is it sending Windows messages or keys? If you are using one that sends messages, try using an ini that sends keys instead. Maybe the IR program has problems sending messages in Vista.

You're using the original Hauppauge remote, instead of teaching the codes to some other learing remote?

- Andy

[pat.holder]

So I'm not an expert here, but I believe it's sending key commands (ctrl+z, ctrl+x, etc.) I don't see it sending windows messages, but again I'm not definite. Also, along those lines, if I use keystroke commands to control sage they work fine; there is no delay using repeated up/down/etc.

As for original v. learning remote, I programmed the learning remote for my stereo, but it all depends on which one is actually on top of the table/easiest to see in front of me in the living room. They both work.

What other information can I look for to see what it's doing when it stalls?

[Opus4]

You can confirm that it is sending keystrokes by using the remote while at Detailed Setup -> Commands -> Show Command. If it shows a keyname, then it is using keystrokes.

When you restart ir.exe, then give focus to Notepad w/debug.txt loaded, a single button used repeatedly will keep working? If this works, but it doesn't work in SageTV, then I'm not too sure what to suggest since I don't remember a problem like this, nor its solution if it has been mentioned before. SageTV doesn't talk to the Haupauge remote; it just receives commands from it.

- Andy

[opy01]

I am having the exact same problem in Vista. I can hit fast forward twice then I have to hit play then fast forward twice again. It is kind of annoying. I thought the batteries were going already but I put new ones in and it worked the same. I also tried resetting the ir.exe but still nothing. I may be getting the Media Center remote soon so when that comes in I will see if it does the same thing.

[pat.holder]

sounds good opy1. Let me know if the media center remote does the trick. Also, a link for the model/newegg purchase point would be great.

i did what you suggested opus, and I still didn't have any luck. The debug gives clean response for each keystroke, and it registers the translated output. That is, it registers "channel up" or "channel down" and not the key stroke "ctrl + Z" in the debug.txt file. Again, there's no delay from debug.txt, which is why it makes me think the translation problem is between ir.exe and sage. I'm not sure whether vista has a translation problem with java, or if sage doesn't work with the driver in vista, but somethings buggy. Anyway, should I submit a bug report on this one?

Thanks for all the help everyone. Also, if you're having this same problem, please post info here! The more widespread we find out this is, the faster we can squash the bugger.

[Opus4]

If you can do repeated button presses with debug.txt, but not in SageTV at Detailed Setup -> Commands -> Show Command, then like I said above, I don't know what is happening. The Hauppauge ir.exe app is just emulating sending keystrokes to the app with focus.

It isn't an MCE remote from an MCE kit, is it?

You could see if SageTV or Hauppauge tech support has heard of anything like this in Vista.

- Andy

[opy01]

This is the craziest thing ever! I was thinking it worked fine on my XP drive but not my Vista drive but I got home last night to watch Mythbusters (greatest show ever) and it worked perfect on Vista for some odd reason. It was working perfect when I first installed but it got flaky about a week ago. Now I am trying to think back to exactly what has changed. I know I removed my wireless keyboard Monday night or Tueasday morning since it is defective but I only got it Saturday and I think the remote was flaky before that. I got Planet Earth waiting to record tonight so when I get home I will see if it still works.

I emailed Hauppauge about this yesterday and they havent responded to me yet. I am ordering the PVR-500 MCE kit today so by Monday I should have it in.

[dogenzenji]

I too just rebuilt my HTPC to Vista Ultimate 64 bit and am experiencing the exact same issue. What's odder is that it's not just with the remote that I have this issue but also with a Bluetooth keyboard. When navigating the menus one often presses the same cursor arrow keys well more than twice but because of this stall I'm forced to wait a rather long while or press another key before I can continue using the same arrow. Also FWIW, I'm running SageTV 6.4.8 with a Hauppauge WinTV-HVR-1950 and its 45 button remote with Java 1.6.0_11. I'm also using the SageMC 6.3.8a STV package.

[ejkeebler]

the remote sends alternating IR signals, if you are using a usb-uirt you actually have to link every button twice, if you are using the receiver that comes with the card i have no idea, but maybe that's a start.

[dogenzenji]

Thanks for the quick reply! Unfortunately I think that's a dead end because the same thing happens with my keyboard although I am noticing it's not with all keys like on the remote. On the keyboard, the problem only seems to happen with the cursor arrow keys.

[mikejaner]

I know for a fact that you have to program each button press twice. I had to do it also when I was teaching the USBUIRT to see the Hauppauge remote. The Microsoft MCE remote is the same way. The key is to select the command with your keyboard, press the button, select the command with your keyboard again, on Sage to start the learing process again, then press the button again on the remote. You will see two completely different codes learned from every button on the remote.

And to explain your description of the behavior of the buttons....
When you press a button, the remote sends out it's first IR code for that button. If you press the button a second time, it sends out the second IR code, then resets, so the first comes out on the next press.
This is the same for a different button press. If you press a button, it sends out the first IR code. If you press a diffrent button, it sends out the first IR code for that button also, but at the same time, resets every other button on the remote. so if you were to press a different button every time, you would only get the first IR code for each button.

[dogenzenji]

Thanks for your reply but I am not using USBUIRT and I have the same problem with my keyboard. I am using the Hauppauge IR blaster that is built in to the WinTV-HVR-1950. I think I may be SOL.

[mikejaner]

Originally Posted by dogenzenji

Thanks for your reply but I am not using USBUIRT and I have the same problem with my keyboard. I am using the Hauppauge IR blaster that is built in to the WinTV-HVR-1950. I think I may be SOL.

USBUIRT, is not really the issue. The Hauppauge remote is the issue. What are you using? Either way, you have to teach both codes of each button to whatever you are using. Trust me about the Hauppauge remote.

Edit: if I am reading right, are you using the Hauppauge IR Blaster/Reciever to recieve your remote commands? If so, I think you may want to rerun the SageTV installer. It has an option to set that up, and may be the fix to your problem.

[Opus4]

If the Hauppauge remote is being used with the Hauppauge IR receiver and the Hauppauge IR software, the remote's toggling IR code is already taken care of; it is only an issue when used with another IR receiver + software that doesn't take the toggle into account. When used with ir.exe and irremote.ini, there is no such thing as teaching it both toggle codes.

However, I don't know why this issue would be happening, especially since another piece of hardware is affected also (the keyboard).

In case there is a Java issue w/Vista, have you checked for a Java update?

Have you checked using the remote with debug.txt, as mentioned earlier in this topic? That worked fine for someone else, so it is probably a dead-end unless Hauppauge has an issue when using the remote with something other than debug.txt.

SageTV tech support might be able to suggest something to check in the debug log to see if SageTV is having an issue dealing with the input, but because of CES, it may take a little longer to hear back from them.

- Andy