Remote Only when GBPVR has Focus?

[garetmax]

I didn't have any problems learning the remote.
I went ahead and relearned it but I'm still having the slow problems.

I'm now wondering if the problem is really a GB-PVR memory usage problem for my setup. I haven't had problems before and don't think the CPU usage was that high previously. Now, whenever I open GB-PVR, my CPU usage runs around 100%.

I did some screen captures that show that my CPU is getting maxed out now when running GB-PVR.
Screenshot1 is when someone was on my MVP watching a show, but GB-PVR was not running on my main computer.
Screenshot2 is when I turned on GB-PVR and the MVP was not running.
Am I supposed to have 2 gbpvr.exe files running in task manager?
Screenshot3 is when neither the MVP or GB-PVR is running.

I went into config and turned off all of the custom plugins and also took the dlls out of the plugin directory but that had no effect.

What do you think?

Thanks

[garetmax]

I'm narrowing it down.

It's definitely something to do with the USB-UIRT.

It doesn't seem to be anything to do with plugins.

When I go into GBPVR config and change the remote control type from USB-UIRT to default hauppauge the CPU usage goes way low and GB-PVR seems to run correctly.

I took the irremote.ini out the the windows system directory. Was I supposed to?
I took the ir.exe out of the windows startup process. Is this necessary?
I relearned all of the keys for the remote.

Do I need to do anything in the capture sources for setting up USB-UIRT?

What are the exact steps to setting up the USB-UIRT?

Thanks

[stefan]

I took the irremote.ini out the the windows system directory. Was I supposed to?

I don't think that is necessary. On the other hand, if you don't use it for something else (which I doubt you do) you won't need it any more.

I took the ir.exe out of the windows startup process. Is this necessary?
I relearned all of the keys for the remote.

I think you have too. At least if you still use the hauppauge remote to control gbpvr. Otherwise ir.exe will try to handle stuff, too. I got weird results when I forgot to remove ir.exe.

Do I need to do anything in the capture sources for setting up USB-UIRT?

Nope

What are the exact steps to setting up the USB-UIRT?

I think what you have done should be about right...

I think that if you ask john over at the support forum at usbuirt.com he has some tool that you can use to convert ir signals to keystrokes. Maybe you can use that to diagnose whether it's the usb-uirt itself that's acting up, or only in conjunction with gbpvr...

[sub]

Reproduce the problem, and I'll see if I can see anything in the logs.

[garetmax]

I've been sick for the last week and have finally been able to work on this again.

I've wiped out my original GB-PVR and started from scratch. The only plugin I have going now is XRecord.

I'm still seeing the same problem. I went in and mapped only the 4 nav buttons on my remote.

Attatched is my gbpvr.exe.log and the USB-UIRT-remote.ini files.

Does anything look wrong in there?

Thanks

[sub]

Its like it lags sometimes but not always, and if it lags too long on one button, it forgets about doing it but it might do it after another couple pushes and maybe 5-10 seconds later.

There are no errors in the logs. All I can really suggest as a diagnostic test is bringing up GB-PVR in a window, and also show Windows clock, then do a few simple tests to press keys noting the exact second number that you pressed the button. Compare these to the timestamps in the log for each key press:

3/11/2006 11:19:27.859 VERBOSE [32] USB-UIRT Input thread received: 314101579085,1460319

Whether these times match, or if it shows the lag, will give an indication of where the problem is occurring.

[garetmax]

Sub,

I did some testing a few times using just the nav down button and the times are matching up exactly in the log.

This example shows when I pushed the nav down button only ONE time. One push on the button gave these 3 lines.

This is from the gbpvr.exe.log
3/11/2006 03:52:10.958 VERBOSE [32] USB-UIRT Input thread received: 130000092EFC,17823488
3/11/2006 03:52:11.109 VERBOSE [32] USB-UIRT Input thread received: 130000092EFC,17823578
3/11/2006 03:52:11.259 VERBOSE [32] USB-UIRT Input thread received: 130000092EFC,17823699

This is in the USB-UIRT-remote.ini file.
NAVDOWN=130000085155,150000285515,1500002A5151,170000A20545,110000021555,170000A85114,

Where do these numbers come from? Are these supposed to match up somehow? Is the USB-UIRT-remote.ini file supposed to be in the gbpvr folder or somewhere else?


I just did another test.
I went into config and changed the remote back to default hauppage.
I didn't hit the fix remote settings.
I hit ok to close config.
I then deleted the USB-UIRT-remote.ini file.
Then I went back into config and changed the remote to USB-UIRT.
I didn't learn any of the keys.
I hit ok and closed config.

I then just opened GB-PVR and my CPU maxes out at 99-100% because of the gbpvr.exe.
As soon as I change the remote back to default hauppauge, I don't have the CPU problem.


I feel like I'm missing something basic here.


Thanks for helping and looking at this.

[sub]

This example shows when I pushed the nav down button only ONE time.

This is from the gbpvr.exe.log
3/11/2006 03:52:10.958 VERBOSE [32] USB-UIRT Input thread received: 130000092EFC,17823488
3/11/2006 03:52:11.109 VERBOSE [32] USB-UIRT Input thread received: 130000092EFC,17823578
3/11/2006 03:52:11.259 VERBOSE [32] USB-UIRT Input thread received: 130000092EFC,17823699

Depending on the remote, it can be quite normal for it to transmit the IR codes several times. The first value here is the IR Code detected by the USB-UIRT. The second value is the timestamp of when it was received. They're only treated as a new keypress if there is a gap of at least 300 in the timestamp.

This is in the USB-UIRT-remote.ini file.
NAVDOWN=130000085155,150000285515,1500002A5151,170 000A20545,110000021555,170000A85114,

Where do these numbers come from? Are these supposed to match up somehow?

These numbers were the possible numbers detected by the USB-UIRT during the button learning. In theory, if you press the same button when you're running GB-PVR, it should result in one of these numbers, which by way of a mapping tells GB-PVR which button you've pressed.

Usually you only get one or two numbers here, so I'm surprised you have so many. I make me think maybe the USB-UIRT is having problems learning the signal from your remote.

I then just opened GB-PVR and my CPU maxes out at 99-100% because of the gbpvr.exe.

If you use your hand to cover the sensor on the front of the USB-UIRT for a few seconds, does the CPU usage drop?

[sub]

I've had a good look at the code now to refresh myself on how it works. Never say never, but I'm fairly confident my code couldnt be causing this 99-100% CPU thing. The loop I have in my code for receiving keypresses from the USB-UIRT has a big sleep for 150ms each time around the loop, which would make it impossible to be using this CPU, so it must be occurring somewhere inside the USB-UIRT driver.

[garetmax]

Sub,

I'll see if I can try another older driver for the USB-UIRT. I downloaded the one on the http://www.usbuirt.com website which is version 1.4.

I did install this driver again and it didn't fix it.

Does anyone have the previous usb-uirt driver? If not, I'll try to get one from Jon over at his website.

Thanks again.