Wake from standby IR Blaster doesn't send channel change

[amac]

Has anyone experienced this issue with SageTV 4.0? On a clean boot, SageTV works fine. On a wake/resume from standby, the IR blaster that comes with a Hauppauge PVR150 stops sending the channel change. Sage software thinks it has changed the channel.

I've also noticed other issues after standby:
- stopping the software can take a very long time
- navigating menus can sometimes be excruciatingly slow

I've temporarily given up on standby.

My hardware:
Hauppauge Pvr150/remote/blaster
Win2k
Jave 1_4_2

[Scriber]

Originally Posted by amac

Has anyone experienced this issue with SageTV 4.0? On a clean boot, SageTV works fine. On a wake/resume from standby, the IR blaster that comes with a Hauppauge PVR150 stops sending the channel chane. Sage software thinks it has changed the channel.

I've had the same issue with this since V2 so I did the same. I presumed a driver issue.

[kha]

I have started evaluating 4.1 and I am seeing the same problem as described above.

[amac]

I've been doing some additional testing on waking from standby. I have Hauppauge PVR150 and am using the IR remote/blaster that comes with the card.

When resuming from standby, if I manually intervene and restart the IR program before a recording is set to start (and so issue a channel change command), all seems to work fine.

If I don't restart the program, then Sage seems to go into never never land (perhaps because it is waiting for a confirmation response from the Hauppague software?).

Perhaps someone at Sage can fix this.

In the meantime does anyone know of a utility that I can run whenever I wake from standby in order to run the restart of the remote control software?

Regards,

Andy

[teedublu]

Here's another one:

I never have been able to get the Actisys blaster to work reliably after resuming from S3 or Hibernate standby.
Tried again with ver 4.1.3
Prior attempt was 2.2.8
I'm not running as a service.

Whatever goes wrong, I found that warm restart doesn't always fix it -- I have to shutdown/cold boot it.
(by fix it, I mean: get the Actisys blaster working again)

(Seems like this thread should be in SageTV Software)

TW

[amac]

Well I thought by using Sagewake I would have resolved this problem. Unfortunately, Sagewake seems to have its own problems and doesn't always wake up when it should.

All my testing indicates that SageTV needs to stop and start Hauppauge's IR.EXE program when the computer comes out of standby/hibernate. As I indicated earlier, when the computer comes out of standby, if I manually kill the IR process and restart it, I do not experience any problems with SageTV and it's response to the remote.

Curiously, when coming out of Windows standby, even if I don't use the remote, and use the mouse (in concert with the program guide) to change channels and watch a show, it is excruciatingly slow to respond (and so often does not change the channel correctly). Obviously there is an issue with the IR transmitter and Sage. If I then kill the IR process, Sage responds quickly/normally to mouse clicks.

I submitted a support request to Sage a couple of weeks ago but haven't heard back. The request was when coming out of Windows standby, to kill the IR process and restart it. But that was specific to my issues with the Hauppauge software.

Since other people possess other remote/blaster/transmitter devices and are experiencing the same problem, probably the easiest solution would be for Sage to add a property to sage.properties which specifies a file (exe or script) to be run after Sage wakes up and has reinitialized the hardware.

Each user could provide their own custom solution to solve power management recovery issues. In my case I would write a bat file that simply runs the following commands.

IR.EXE \quit
IR.EXE \quiet


Is anyone from Sage listening?

[silentmonolith]

I'm having the same issues here - I don't blame SageTV though. It's Hauppauge's fault. My 150 can't record properly after coming back from standby/hibernate no matter what PVR software I use (I haven't used WinTV yet because it looks like an application for Windows 3.1 )
The problem is 150 has a conflict with the operating system itself. I`ve even e-mailed the big guys @ Hauppauge and this is what they wrote:

Hi
I'm afraid we cannot offer support for getting our products working
with
3rd party software, it is up to that manufacturer to provided support
for our cards in that environment, rather than us to make our cards
compatible with it.
-------------------------------------------
I guess you forgot to mention the Hauppauge 150 MCE, designed to be compatible with Windoze MCE...but hey we're dealing with Microsoft here, a multi billion dollar company....
--------------------------------------------------------

I would suggest using the WinTV 2000 application to capture video and
then editing the file in your chosen application. Although we do not
directly support recording from sleep mode as it has been unreliable in
the past.

---------------------------------------
your suggestion is noted but WinTV 2000 has to be brought to 2006's level of viewing experience
------------------------------------------

Best regards

James Foster


------------
Thanks James, at least you wrote back

[amac]

Actually James,

I tried out BeyondTV 4.0 before Sage and it was able to issue channel changes coming out of standby. Perhaps they were resetting the IR software as I have suggested Sage do.

As to Hauppauge, they claim to not support power management except for the fact their release notes for the driver indicate they are supporting it. They just don't want to hear about bugs. Who to blame is always a hard one. Sage claims to reset the hardware when they come out of standby. My issue is, if they can reset the hardware, why not reset the software. They go hand in hand.

I have submitted a bug request to Sage with some of the text from this forum. I'll post if they respond. In the meantime, I'm going to investigate another option that might work for me. I don't have a lot of time for development, but I'm going to research if I can't use the windows scripting host to trap an event at the time the computer wakes.

I'd really rather sage provide a solution for me.

[silentmonolith]

Why waste time on reinventing the wheel? SageWake was created for this purpose! Combined with my little script my Sage 2.2 works flawlessly -it wakes up as it should, records and then powers off!

[amac]

Originally Posted by silentmonolith

Why waste time on reinventing the wheel? SageWake was created for this purpose! Combined with my little script my Sage 2.2 works flawlessly -it wakes up as it should, records and then powers off!

Your reply was in reference to a post that the admin removed because it was a duplicate from another thread. The post simply refered to another thread: http://forums.sagetv.com/forums/showthread.php?t=16522

To answer your question, it is not wasting time, nor is it reinventing the wheel. I understand Sagewake was created for that purpose. I believe I was even the one who suggested you use Sagewake. SageTV also has power management facilities.

Bottom line is, they don't provide the desired behaviour on my machine with respect to Hauppauge IR Blasters. Why would I want to continue with Sagewake? I'm happy Sagewake solved your problem and that of many other users. The symptoms I've experienced with Sagewake were documented by someone else in the Sagewake thread and were never addressed. Namely, it seemed to work for a short period, but eventually the machine would wake up at the prescribed time with a dialog box opened by Sagewake indicating it was re-entering standby in 60 or fewer seconds.

We all have different configurations and versions of Sage, Java, Windows, different motherboards, bioses, and patches applied. Who knows the reason for its behavior? It's not an ego thing. I'm not trying to supplant Sagewake nor am I trying to be the power management guru. I reported a bug on this subject to Sage and have been working with them, but so far to no avail. Up until a month ago, I knew nothing about how Windows handled power management and frankly I had no desire to.

I needed a solution that worked on my machine. I posted it in the event that it might help someone else (which it already has). I'm sorry if you view that as a waste of time or reinventing the wheel.