AWTThread Hang when using USB-UIRT as Receiver

[peternm22]

Hello

Currently I'm using the Hauppauge remote and IR sensor, which works fine. But I'm trying to change to a different remote which doesn't have learning capabilities. I know the Hauppauge IR sensor doesn't support other commands, so I figured I would use the USB-UIRT I have to setup a new remote (since Sage has built in support for this). Right now I'm just using the USB-UIRT as an IR blaster, and I haven't had any trouble with it.

I go into Detailed Setup > Commands > Remote Control Configuration and then select "USB-UIRT Receiver + Any Remote". Immediately the CPU spikes to 100% and stays there causing SageTV to slow to a crawl. A look at the task manager reveals that it's SageTV.exe and not SageTVService.exe which is at 100%.

I manage to reset it to "No Remote or External Setup", and that seems to fix them problem after I restart the GUI.

Is it not possible to use the USB-UIRT as a receiver and blaster at the same time, or is something screwy with my setup?

Here are my specs:

SageTV 6.1.18 in service mode
SageMC 6.3.2c
Java 1.6
Windows XP Home
2x Hauppauge PVR-250
Athlon64 3000+

I checked the log file (which I attached to this post), and this is the error coming up:

Sat 4/28 18:57:21.884 AWTThread Hang Detected - hang time = 750

I switched to the default STV, with no customizations and I get the same problem. Any ideas what's going on?

Thanks.

-Peter

[BobPhoenix]

That particular error probably doesn't mean anything. However I have a suggestion for you. Are you running with Service mode? If so are you using the system account or a user? If you are using the system account or a different user from the one used when you are using the GUI I suspect that is your problem. Change SageTV service to use the same user as the one when you use the GUI. I had this same problem 100% CPU and turned this into Sage on one of the betas. They replied that it is a bug in the USB-UIRT drivers that causes this. I submitted a support request with USB-UIRT but I never heard back after submitting the info they asked for. But I found my own solution - use the same userid for the service and the GUI.

BobP.

[peternm22]

Thank you!

Thanks Bob, your suggestion worked perfectly. The SageTV service was using the system account, so I just switched to my user account and everything is working now.

-Peter