2011-08-24, 05:55 AM
I have seen this phenomena several times. It happens at the time between one recording finishing and the next recording starting when the system is set to sleep after a period of inactivity.
In the most recent example:
Recording A was scheduled to finish at 23:15 (23-08-2011)
There was 3 minutes of padding on the recording, taking the time up to 23:18
Windows 7 is set to sleep after 5 Minutes, so does so at 23:23
Recording B was scheduled to start at 23:25
Normally the system will come out of sleep 4 minutes before next recording (Includes 2 mins of pre padding), which would be 23:21, but at this time power is already on from the previous recording and in the process of shutting down.
The system shuts down at 23:23 and misses the next recording.
If I lengthen the sleep period to 10 mins, it would affect a recording starting 15 mins later. As recordings are usually scheduled in 5 minute increments I could set the system time out to 8 minutes, which might work, as long as I use the same padding!
I have attached the logs, not that they show much.
In the most recent example:
Recording A was scheduled to finish at 23:15 (23-08-2011)
There was 3 minutes of padding on the recording, taking the time up to 23:18
Windows 7 is set to sleep after 5 Minutes, so does so at 23:23
Recording B was scheduled to start at 23:25
Normally the system will come out of sleep 4 minutes before next recording (Includes 2 mins of pre padding), which would be 23:21, but at this time power is already on from the previous recording and in the process of shutting down.
The system shuts down at 23:23 and misses the next recording.
If I lengthen the sleep period to 10 mins, it would affect a recording starting 15 mins later. As recordings are usually scheduled in 5 minute increments I could set the system time out to 8 minutes, which might work, as long as I use the same padding!
I have attached the logs, not that they show much.
