Suspend and resume with SageTV

[julesjohn]

So my update after forcing hibernation via remote is that Sagewake did wake up for a scheduled recording which is great. But I now see two issues:

1) I noticed the machine did not return to hibernating after it woke up to record from hibernation. The "favorite" recording was at 4pm - 5pm and the next "favorite" recording was at 6:30PM. So it should have hibernated again after 5pm.

2) HTPC woke up for some reason at 6AM (3 mornings in a row now) and I have no scheduled recordings at any time in the AM. I changed my --noir and --nofavorite settings to 23-7 and now it wakes up at 7. So some issue there. I removed the --noir and --nofavorite times completely and now the Sage does not wake up for no reason at the end time. So appears to be a bug.

My SageWake commands (before removing times) were this:
SageWake --noir=23-6,11-15 --nofavorite=23-6,11-15 --nomanual --leadtime=180 --usehiber --schedfile="C:\Progra~1\FreyTe~1\SageTV\schedule.txt"

Not sure if you have used Hibernation with SageWake and not just Suspend and what you recommend using? May be different behavior. Let me know if you want me to help QA it a bit in this mode. Thanks.

[geoay]

I discovered recently SAGETV -> nice tool !
But I deal with the same problem than most of you :how to put my PC to sleep between to SAGE recording.
I read all the "Suspend & resume with SageTV" thread, but I have some difficulties to understand how to use SAGEWAKE.
I understood I have to modify Sage Properties in order to write schedule.txt which is used biy SageWake.
But after ?
Here a list of basic questions !
Run SageWake before launching SageTV ?
How to configure PC power management ?
How to force PC to sleep after using SageTV (reading recording) ?
How to awake the system without any keyboard or mouse (only remote) ?
Is this compatible with ATI remote Wonder -> does ATI RW will awake with Sage ?
Is this compatible with VNC server running in background (I use my main PC to monitor my HCPC via network) ?
Please help a newby user !
(sorry to my poor english : I'm not a native english speaker !)

[nielm]

I will answer a couple of questions, which may make your decision for the rest.

How to awake the system using only remote ?

That depends mainly on your remote and how it interfaces with your PC. I have an ATI RW and a serial port-based IR receiver. Neither can be used to wake up my machine.

Is this compatible with ATI remote Wonder -> does ATI RW will awake with Sage ?

The ATI RW has no power management capabilities, so no it can not wake up a PC from standby. This is a problem with the RW hardware (does not support wake-on-USB capability)

Is this compatible with VNC server running in background

That depends on your network card, but in general the answer is no -- it is unlikley that incomming network traffic will wake up your PC. (Some network cards support 'wake up on LAN', but they normally need a specially formed network packet to be sent to them).
These 'Wake Up on...' options can be configured in the device manager properties for the network card and modem (there may be options for 'allow this device to bring your computer out from standby' or similar).

[mwhitlock]

Originally Posted by julesjohn

1) I noticed the machine did not return to hibernating after it woke up to record from hibernation.

I have noticed this, too. It appears to be a bug that I will work on.

Originally Posted by julesjohn

2) HTPC woke up for some reason at 6AM (3 mornings in a row now) and I have no scheduled recordings at any time in the AM. I changed my --noir and --nofavorite settings to 23-7 and now it wakes up at 7.

It was probably doing what you told it. When you say "no IR from 23 to 6, that means 6:00 is the first intelligent recording of the day for which you will allow SageWake to wake your PC. If SageTV has scheduled an intelligent recording for 6:00, SageWake will turn your PC on. If you don't want it coming on that early, set your "no" range later. If you don't use SageTV's intelligent recording feature, you should use --noir with no ranges to totally prevent SageWake from waking for scheduled intelligent recordings.

[julesjohn]

Originally Posted by mwhitlock

I have noticed this, too. It appears to be a bug that I will work on.

It was probably doing what you told it. When you say "no IR from 23 to 6, that means 6:00 is the first intelligent recording of the day for which you will allow SageWake to wake your PC. If SageTV has scheduled an intelligent recording for 6:00, SageWake will turn your PC on. If you don't want it coming on that early, set your "no" range later. If you don't use SageTV's intelligent recording feature, you should use --noir with no ranges to totally prevent SageWake from waking for scheduled intelligent recordings.

Ok well I don't have IR enabled anyway. But what seems to be a bug is that 23 to 6 should not wake up the machine if there are no recordings at 6. The expected behavior to me would be that it wake up the next time it has a scheduled recording but for sure not between 23 to 6. So if the next scheduled recording is at 7 then the machine would be hibernating still from 6 to 7.

Just my two cents, but not a major deal. The issue of it not returning to hibernation after coming out of it for a recording is higher priority. Thanks for your efforts.

[mwhitlock]

There is no reason SageWake would wake the computer at the end of the "no waking" time frame. It would only wake the computer if there is an entry in your SageTV schedule file for a show at 6:00. Please note that the schedule file contains all the shows SageTV would be intelligently recording, even if you have intelligent recording disabled. That is why you must use the --noir option with SageWake if you do not have intelligent recording enabled in SageTV.

It should look like this:

SageWake --noir --nofavorite=23-6,11-15 --nomanual --leadtime=180 ...

[mwhitlock]

Here are a couple of screen shots of some things to come.

[jbuszkie]

Any timetable of when you think you'll release it????? :-)

[mwhitlock]

I have a few more things to finish before it will be consumable. It shouldn't be long. I do, of course, have grander visions for the future, but a working beta shouldn't be far off.

[mdmint]

Originally Posted by julesjohn

Just my two cents, but not a major deal. The issue of it not returning to hibernation after coming out of it for a recording is higher priority. Thanks for your efforts.

This may be a WinXP issue. I've seen this behavior on systems with Sage not even installed. Hibernate, wake from hibernation, won't hibernate again until rebooting system.

[julesjohn]

Another thing that I noticed is that if I force hibernation via SendMsg to my HTPC it may adversely affect Comskip processing. So that said I bring this up as something to consider in the Sagewake application.

It appears it would be a good idea if Sagewake is aware of any Comskip processing. If hibernation or suspend is done during Comskip it may cause issues. I brought this up in the Comskip thread here.

The problem is that Comskip can be set to process in the background, so as a user I wouldn't know if it is happening at that moment. I am not sure either if hibernation would occur if this process was happening or how Sagewake mainly would act in forcing hibernation again if Comskip processing started when Sagewake awoke SageTV for a recording and then wanted to put it back into hibernation. Probably something to just evaluate for Sagewake but not a huge deal. Thanks.

[mwhitlock]

Comskip should process the PBT_APMQUERYSUSPEND Windows broadcast message and return BROADCAST_QUERY_DENY if it is currently processing. This will deny SageWake's request to suspend/hibernate the system.

Of course, there really should be no problem suspending during Comskip processing if he's doing it right. ;-)

[mdmint]

Originally Posted by julesjohn

Another thing that I noticed is that if I force hibernation via SendMsg to my HTPC it may adversely affect Comskip processing. So that said I bring this up as something to consider in the Sagewake application.

It appears it would be a good idea if Sagewake is aware of any Comskip processing. If hibernation or suspend is done during Comskip it may cause issues. I brought this up in the Comskip thread here.

The problem is that Comskip can be set to process in the background, so as a user I wouldn't know if it is happening at that moment. I am not sure either if hibernation would occur if this process was happening or how Sagewake mainly would act in forcing hibernation again if Comskip processing started when Sagewake awoke SageTV for a recording and then wanted to put it back into hibernation. Probably something to just evaluate for Sagewake but not a huge deal. Thanks.

I use a Freeware util that can configure to shutdown or restart or loggoff or suspend or hibernate or lock computer based on time countdown, or specific time or date OR based on CPU usage which is what I am using to auto shutdown after comskips processed. AMP WinOFF

[henk99]

Since yesterday i have installed the sagewake utillity and i have been putting it through it's paces ever since. Doing some recordings and checking if it goes to standby and if it wakes up for a recording. All of this appears to work fine....kudos for that

However, i have some issues as well

1. When retuning the computer from standby (S3 in my case) everything seems fine and when i restore sagetv from the taskbar all works well. Hoever, i can't watch programs anymore. When i choose a program in the livetv guide (it is not recording a program at that time by the way...) and choose 'watch now' , i get a 'capture error in playback' (error -4.0x8007048f). i need to reboot the pc to get this error out. A simple exit and then a restart of Sagetv won't do.

2. I used a wake on lan program from another computer in my network to wake up my computer from the OFF state (not standby S3!!!). This always worked like a charm when my pc was OFF. However, when my pc is in standby, i can't get this 'wake on lan' function to work anymore from the other pc.

3. Also, when a recording is in progress, and i press the standby key on my logitech keyboard, it will go to standby! I was under the impression that sagewake prevented that from happening, so you don't accidentally stop a recording. I might have understood wrong of course....

You guys probably understand that issue number one is most annoying and hopefully some1 can help me solve that one.

Henk99

[mwhitlock]

Originally Posted by henk99

1. When retuning the computer from standby (S3 in my case) everything seems fine and when i restore sagetv from the taskbar all works well. Hoever, i can't watch programs anymore. When i choose a program in the livetv guide (it is not recording a program at that time by the way...) and choose 'watch now' , i get a 'capture error in playback' (error -4.0x8007048f). i need to reboot the pc to get this error out. A simple exit and then a restart of Sagetv won't do.

Sounds like your system isn't reinitializing your TV tuner when you come out of standby. Using hibernation instead of standby will probably solve this problem.

Originally Posted by henk99

2. I used a wake on lan program from another computer in my network to wake up my computer from the OFF state (not standby S3!!!). This always worked like a charm when my pc was OFF. However, when my pc is in standby, i can't get this 'wake on lan' function to work anymore from the other pc.

Try enabling "Allow this device to bring the computer out of standby" on your network card.

Originally Posted by henk99

3. Also, when a recording is in progress, and i press the standby key on my logitech keyboard, it will go to standby! I was under the impression that sagewake prevented that from happening, so you don't accidentally stop a recording. I might have understood wrong of course....

I'd bet you have some special Logitech software installed to work with that keyboard. Further, I'd wager that that Logitech software doesn't do the normal routine for suspending the system. It probably just puts the system to sleep without first polling the running programs if that would be okay like it is supposed to do. The default Microsoft implementation of the ACPI sleep key is to poll before allowing it to happen. In your case, there's nothing SageWake can do. Perhaps you can uninstall your keyboard software. You probably don't actually need it.

[henk99]

Originally Posted by mwhitlock

Sounds like your system isn't reinitializing your TV tuner when you come out of standby. Using hibernation instead of standby will probably solve this problem.

Try enabling "Allow this device to bring the computer out of standby" on your network card.

I'd bet you have some special Logitech software installed to work with that keyboard. Further, I'd wager that that Logitech software doesn't do the normal routine for suspending the system. It probably just puts the system to sleep without first polling the running programs if that would be okay like it is supposed to do. The default Microsoft implementation of the ACPI sleep key is to poll before allowing it to happen. In your case, there's nothing SageWake can do. Perhaps you can uninstall your keyboard software. You probably don't actually need it.

On your first point....no...that didn't change anything. I made the settings in the power settings for Xp and let it hibernate after 30 minutes. Tested it and it hibernated fine and then it recorder something and went to hibernate again. I then woke the pc up and tried to view something via livetv guide, but it gave the error again.
I noted a while back you have had the same problem with a gigabyte mobo? I have one from the same series, so how did you solve it?
My settings in windows are:
monitor off, 5 minutes
harddisk off, never
standby, never
hybernate, 20 minutes

In bios i have it set to 'suspend to ram', that means S3 i think.

I agree with you on the initialization, but hibernate didn't solve it.

Maybe you have other ideas?

PS: I also tried to implement the terminate/restart option, but that didn't change anything either.

[mwhitlock]

I'm pretty sure that putting the system to sleep while I have SageTV minimized does bad things for me. I always make sure I actually "sleep" SageTV, that is, put it in the taskbar notification area. Then I can suspend and resume the system and not cause problems in SageTV. I don't know what to suggest for your problem.

[henk99]

Hmmm....dang! I have all that already

I have the same problem when i exit sagetv (this has nothing to do with sagewake) and then restart it, without rebooting the pc. My Sagetv doesn't like that, i get the same error then.
It appears a bit related. When the pc returns from hibernate/standby it should probably re-initialize the pvr card. The same prolly goes when sagetv gets exited and then restarted again. It seems my PVR-150mce has probs with that.

Any suggestions? Anybody?.....please anybody....

[henk99]

Allright, it appears i found the solution to the problem.

I saw a thread that mentioned a tweak for PVR150 PAL versions. I'm in the Netherlands and i have a PAL version. There was a line in the sageproperties file ("mmc/video_format_code") that had to be changed. i did so, and all problems with capture errors disappeared.
It is also possible now to ext Sagetv and restart it again, and still having no errors. Before this i couldn't do that.
So, now i can suspend to ram or hibernate all i want, it comes back like a charm.

Cheers,

Henk99

[henk99]

After running sagewake smoothly for a month or so, all of a sudden it gives me problems.

This is what happens;
After i have put my computer to standby (S3) and it is left of for a day or so, i try to wake it by double clicking my mouse (like normal). When i get my windows desktop back, i see this pop up window of sagewake sitting there. It is stuck at 30 seconds or so and the box says "sagewake will put the pc to standby in....seconds" The time bar doesn't move anymore. Within seconds of waking up, the pc goes to standby....
I have had ocasions were 3 instances of that same dialog box are sitting there. I have to wake the pc up 3 times for all instances to be gone and for the pc to remain on. This behaviour causes me to miss recordings, because it behaves the same when the pc is woken from standby to do a recording!
I don't know why this happens, but it is annoying as you can imagine. Here is part of the sagewake log:

[quote]
- <Event time="3/13/2005 11:50:40 PM">
- <NextRecording>
<Show title="Crime Scene Investigation" start="3/14/2005 9:27:00 PM" stop="3/14/2005 10:45:00 PM" channel="4" />
</NextRecording>
<SetWakeUp time="3/14/2005 9:25:00 PM" />
</Event>
- <Event time="3/13/2005 11:55:12 PM">
<SystemSuspend />
</Event>
- <Event time="3/14/2005 2:30:13 PM">
<SystemResume />
</Event>
- <Event time="3/14/2005 2:41:24 PM">
<SystemSuspend />
</Event>
- <Event time="3/14/2005 9:25:16 PM">
<SystemResume />
</Event>
- <Event time="3/14/2005 9:25:39 PM">
<SystemSuspend />
</Event>
- <Event time="3/15/2005 12:38:27 AM">
<SystemResume />
</Event>
- <Event time="3/15/2005 12:38:41 AM">
<SystemSuspend />
</Event>
- <Event time="3/15/2005 12:39:01 AM">
<SystemResume />
</Event>
- <Event time="3/15/2005 12:39:01 AM">
- <NextRecording>
<Show title="CSI: Miami" start="3/15/2005 8:27:00 PM" stop="3/15/2005 9:45:00 PM" channel="7" />
</NextRecording>
<SetWakeUp time="3/15/2005 8:25:00 PM" />
</Event>
[\quote]

One thing to note is that every day i do an XMLTV download which is scheduled in windows. I have set this task to allow waking up the pc. In the log above you can see this event switching on the pc and after a few minutes switching to standby (2.30PM-2.41PM, marked red). Can this perhaps have something to do with it? I don't know but perhaps someone can help out.

At 9.25PM you can see it missing the recording of CSI (marked orange)

The events at 12.38AM untill 12.39AM is me waking the pc from standby by mouse. You can see that it switches off itself because of this sagewake pop up window.