Scheduled resume happens a few minutes late

[DomesticSimian]

I had a failed recording last night, and while looking at the logs I noticed that the OnResume happened a few minutes after the scheduled time. Full logs are attached, but here are some relevant snippets:

2021-01-04 12:37:00.398 [DEBUG][9] Loading recording schedule
2021-01-04 12:37:00.402 [DEBUG][9] [The Late Show With Stephen Colbert] at 1/4/2021 11:35 PM
2021-01-04 12:37:00.402 [DEBUG][9] Requesting wake up for 'RecordingOID889' [The Late Show With Stephen Colbert] at 1/4/2021 11:31 PM


<snip>
2021-01-04 17:31:03.458 [DEBUG][95] stopping device process
2021-01-04 23:34:27.882 [DEBUG][9] DefaultDirectoryChoice: first
2021-01-04 23:34:27.884 [DEBUG][9] Preferred filename is 'The.Late.Show.With.Stephen.Colbert.S06E59.Stacey.Abrams;.RuPaul.Charles;.Maren.Morris'
2021-01-04 23:34:28.345 [DEBUG][84] [Resume]
2021-01-04 23:34:28.345 [DEBUG][84] OnResume...

Any idea why that might be happening? Is there a way for me to increase the wake up time buffer so my PC will wake up earlier?

The actual failure happened shortly after that:

2021-01-04 23:34:46.003 [DEBUG][9] Unexpected error in GetTargetName: System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Recorded TV\The Late Show With Stephen Colbert\Season 06\'.

  at System.IO.FileSystem.CreateDirectory(String fullPath, Byte[] securityDescriptor)
  at System.IO.Directory.CreateDirectory(String path)
  at NShared.RecordingService.GetTargetName(ScheduledRecording scheduledRecording)
  at NShared.RecordingService.WorkerThread()

I am (temporarily) using a USB attached drive for my recordings, and I suspect there was some timing issue here where the drive had not fully resumed from standby when NextPVR attempted to create the directory, which resulted in the above failure.

Any suggestion on how to prevent that from happening again? Thanks!

[sub]

It looks like Stephen Colbert was due to start at 11:35pm. The recording was due to start at 11:34pm, because it had one minute of pre-padding. It woke the machine a couple of minutes early (11:31pm), to make sure the machine had plenty of time to wake properly before the recording started at 11:34pm.

Yes, looked like your D:\ drive wasn't available by 11:34pm. Not clear exactly why.

[mvallevand]

The resume is already well before padding time I think a full minute before padding.

Martin

[DomesticSimian]

2021-01-04 12:37:00.402 [DEBUG][9] Requesting wake up for 'RecordingOID889' [The Late Show With Stephen Colbert] at 1/4/2021 11:31 PM

Ok, so this log line implies that the PC should wake up at 11:31, right?

2021-01-04 23:34:28.345 [DEBUG][84] [Resume]
2021-01-04 23:34:28.345 [DEBUG][84] OnResume...

These lines seem to indicate to me that the PC actually woke up at 11:34. Am I misinterpreting what those lines mean? Also, my pre-padding is set to 2 minutes, so I would have expected the recording to start at 11:33.

[Graham]

2021-01-04 12:37:00.402 [DEBUG][9] Requesting wake up for 'RecordingOID889' [The Late Show With Stephen Colbert] at 1/4/2021 11:31 PM

Ok, so this log line implies that the PC should wake up at 11:31, right?

2021-01-04 23:34:28.345 [DEBUG][84] [Resume]
2021-01-04 23:34:28.345 [DEBUG][84] OnResume...

These lines seem to indicate to me that the PC actually woke up at 11:34. Am I misinterpreting what those lines mean? Also, my pre-padding is set to 2 minutes, so I would have expected the recording to start at 11:33.

I suspect that the first log message does not include the time that NextPVR sends to Windows asking for a wake up ... only the time that the recording is due to start.

The second message indicates the time that NextPVR Server resumed after Windows had finished its part of the wakeup process.

What does the Windows Event Viewer have to say about the wake up?

At the risk of stating the bleedin' obvious ... You can set the pre-padding to five minutes (or whatever) and that should make the problem go away.

[mvallevand]

Extra pre-padding won't make the problem go away, the wake up will still be 1 minute before prep-adding so if the device isn't waking in one minute the recording will still fail. There is no second attempt at start time.

Realistically use a drive that doesn't take as long to wake or turn off sleep until the replacement drive is ready.

Martin

[Graham]

Extra pre-padding won't make the problem go away, the wake up will still be 1 minute before prep-adding so if the device isn't waking in one minute the recording will still fail.  There is no second attempt at start time.

Obviously! .... I seem to be exceptionally empty headed today ...

[DomesticSimian]

So I take it there is currently no way to increase the "wake up time" buffer?

[mvallevand]

There is this setting in config.xml

<WakeupPreRecordingSeconds>90</WakeupPreRecordingSeconds>

You can play around with it.

Martin

[DomesticSimian]

Awesome thanks!