PC doesn't wake up sometimes

[aesn5]

Hello,

I've been using GB-PVR for several months now and it works very well. But sometimes it doesn't wake up for scheduled recordings. I've scheduled two succeeding recordings on last Sunday (2010-03-14), the first one on 22:40 and the second one on 23:55. Strangely only the second one was recorded (more precisely, as the second one aired just after the first, the first still got the last bit due to pre-show padding, as it was started when the PC resumed from hibernation for the second scheduled recording). What also irritates me is the log entry "Found new Pending recording needed wakeup request: Dexter (14.03.2010 23:55:00)". Shouldn't it be more something like "Found ... (14.03.2010 22:40:00)"? I've attached the logs. I appreciate any help. Thanks in advance.


Regards
aesn5

[pcostanza]

Maybe take a look at this standby tool.

[aesn5]

Thanks for your reply!

I didn't know this tool, I'll try it. By the way, I forgot to mention that I'm on Windows 7 x86.

But nevertheless, for me it seemed (!) like GB-PVR didn't register the wake-up event for the first scheduled recording in the first place. At least that's what I think I could see in the logs.

[martint123]

It certainly looks like a gbpvr oddity rather than a wake/standby problem.
I have no idea why, but the log certainly shows something missing. I guess the wake request is also missing from the exe.native log?

Code:

2010-02-28 20:42:30.795 VERBOSE [5] - checking Dexter 2010-02-28 20:42:30.795 VERBOSE [5] pending: (37) Dexter 28.02.2010 22:20 2010-02-28 20:42:30.795 VERBOSE [5] - checking Dexter 2010-02-28 20:42:30.795 VERBOSE [5] pending: (38) Dexter 28.02.2010 23:20 2010-02-28 20:42:31.029 VERBOSE [5] Found new Pending recording needed wakeup request: Dexter (28.02.2010 22:20:00) 2010-02-28 20:42:31.029 VERBOSE [5] Found new Pending recording needed wakeup request: Dexter (28.02.2010 23:20:00) 2010-03-14 11:29:23.446 VERBOSE [5] - checking Dexter 2010-03-14 11:29:23.446 VERBOSE [5] pending: (45) Dexter 14.03.2010 22:40 2010-03-14 11:29:23.446 VERBOSE [5] - checking Dexter 2010-03-14 11:29:23.446 VERBOSE [5] pending: (46) Dexter 14.03.2010 23:55 2010-03-14 11:29:23.650 VERBOSE [5] Found new Pending recording needed wakeup request: Dexter (14.03.2010 23:55:00)

[aesn5]

Yes, it's also missing in GBPVRRecordingService.exe-native.log.

Code:

2010-03-12 11:05:00.846 VERBOSE Asking Windows to be awake for EPG update at 2010-3-13 10:58:30 (UTC 2010-3-13 9:58:30) 2010-03-13 11:04:56.884 VERBOSE Asking Windows to be awake for EPG update at 2010-3-14 10:58:30 (UTC 2010-3-14 9:58:30) 2010-03-14 11:05:07.844 VERBOSE Asking Windows to be awake for EPG update at 2010-3-15 10:58:30 (UTC 2010-3-15 9:58:30) 2010-03-14 11:29:23.650 VERBOSE Asking Windows to be awake for recording (oid: 46) at 2010-3-14 23:47:30 (UTC 2010-3-14 22:47:30) 2010-03-14 23:47:51.764 VERBOSE getSetting(BDADisableStatusChecks) 2010-03-14 23:47:51.778 INFO BDARecorder:::StartRecording(TechnoTrend Budget C-1500 DVB-C, 1, D:\HTPC\GB-PVR\Recordings\Dexter\Dexter_20100314_22402355.mpg, T:C,682000,6900,QAM64,8~NID:1~ONID:1~TSID:1089~P:12020~V:166~A:128~L:ger~PMT:46~TXT:68~PCR:166~N:>RTL2) 2010-03-14 23:47:53.273 VERBOSE Checking tuning spaces

[martint123]

I think this may have to be one for sub to look at ??

[gEd]

does it only do it on a season recording ?

I just have a hunch but I am wondering if GBPVR thinks that the second show is a reschedule of the first show (as they have the same name)

Try changing this value in config.xml to 10 and retest

<AllowableTimeslotVariance>90</AllowableTimeslotVariance>

[aesn5]

Hi,

no, it also happened before when I only had a single schedule. Testing is a bit difficult here as the the described behavior only happens sometimes, like once a month or so. So, this could take long...

Now that I think about it, I also noticed other odd behavior. Sometimes when I schedule a recording, it is recorded by both my tuner cards (I got 2 DVB-C cards). I doubt that it has anything to do with the whole issue, because the recording works just fine, only with redundant one, but I just wanted to mention it. :p And once, when I tried to schedule a recording for a broadcast that was already airing, GB-PVR always started the recording and immediately stopped, telling me that the recording was successful. That happened every time I tried to record. Maybe I still got the logs for it. I will look for them tomorrow.

But still, the first issue is the most annoying one for me now.

[fla]

My PC also doesn't wake up for a recording once in a while (once in every 15 - 20 recordings). I never really figured out the exact pattern but it seems like if I schedule a recording in gbpvr and then immediately leave the machine idle so it hibernates 20 minutes later, there's a bigger chance that it won't schedule the proper wake up time. If gbpvr is used for hours after scheduling recording, it seems like the proper wake up time will most likely be scheduled.

[b00sfuk]

Same here, every 20 or so recordings it just fails to wake. Nothing in the logs to indicate why so I just put up with it. Seen it on both Vista and Win7. Next time it happens I'll try to post some more helpful info.