Recording fails due to hibernation/sleep between wakeup time and start of recording

[gabortel]

My computer is set to hibernate. It wakes up 90 seconds (the default <WakeupPreRecordingSeconds>) before a scheduled recording, and hibernates about 10 minutes after the recording has finished. Usually it works perfectly, but sometimes the recording fails with the "Recording service not running at recording time" message.

As I figured out, it happens when hibernation occurs during that 90 seconds (about 10 minutes after a previous recording or other user activity on the computer). So, if the computer is already on at the wakeup time and the hibernation timer expires within the following 90 seconds just before the recording starts, then the computer hibernates and the recording fails.

I think the recording service or something else should prevent hibernation already during this period, but it does not. It is clearly shown by powercfg -requests, that there are no requests in this period. The request (SYSTEM: [DRIVER] Legacy Kernel Caller) appears only when the recording starts.

Any idea / suggestion / solution? Or did I miss something? Strange, that nobody else experienced this.

(ps. I think this is not specific to the version 3.1.1, it happened with 2.6.2 too.)

[sub]

We have had one or two people post about it in the past, but it's not a very common problem. I've added a reminder to my to-do notes for the next release.

[gabortel]

Looking forward to see. Thanks a lot!

[mvallevand]

I figure for those of us who do let their backend sleep server it happens a few time a year. Common maybe not, annoying very.

Martin

[Reddwarf]

Why not let your computer run 24/7? If it sits in the living room you'll get the power it uses back through heating, at least in winter time

[jcjefferies]

As has been said its something that happens very occasionally. What tends to be the cause is that just before a recording is due the computer starts to go to sleep/hibernation a process which can take around 20-90 seconds depending on the computer. Windows will not respond to any form of input until the process is complete so a "Wakeup" to start a recording during these few seconds is lost.

When it last happened to me about 6 months ago I decided to ask my son to write a script to run at the end of a recording to detect if another recording was due to start in the next 10 minutes. If a recording is due then there are several ways to stop the computer going to sleep. As it has not happened for such a long time I forgot to ask him!

Chris

[Deev8]

Strange, that nobody else experienced this.

It's a problem I experience occasionally, and I actually lost a recording this way last week. Once you know that the time gap between two scheduled recordings is "in the danger zone" you can tweak the pre and post recording padding as a work around - in my case I usually only notice after I've missed one recording. At least adjusting the padding avoids a repeat disapointment the following week. So anything sub could do to help in future releases would be great.

[johnsonx42]

I think sub said in the past that there is logic that is supposed to keep the system awake between the time it wakes up and the time the recording actually starts, but he suspects that something broke and that code isn't firing. I realize that doesn't exactly help anyone, that's just where things left off (I think).