Understanding how Nrecord.exe controls sleep / wake?

[j2gbpvr]

I've had the same problem on three computers for a few months now. Before that it was fine and never woke 1 minute after sleeping.
I set power saver option to sleep after 5 minutes and disable wake in mouse, keyboard, and NIC.
Started in WIN 7 with NPVR 3.4.8 and still does it in WIN 10 PRO with NPVR 3.5.7
Event log always shows NRecord.exe waking the computer every three minutes.
Powercfg -lastwake also shows NRecord.exe waking it.
I right click the NPVR icon and select Restart Recording Service to get it to stop. Then it would stay asleep until the next record time.
Then I upgraded all three computers to WIN 10 Pro at the end of July and it would do it more often.
Then upgraded to NPVR 3.5.7 and it would do it more often.
Now it seems to do it every day so I Restart Recording Service every time before i want it to sleep.

[jksmurf]

@j2gbpvr - interesting...I'm not alone :-)

btw I wonder what happend to slinven's post quoting my signature line about being patient - touche' :-). I guess I should be. Patient.

[sub]

btw I wonder what happend to slinven's post quoting my signature line about being patient - touche' :-).

He was spam. Has created posts quoting random stuff, with links to buying rings. Banned and posts removed.

[jksmurf]

He was spam. Has created posts quoting random stuff, with links to buying rings. Banned and posts removed.

OK cheers ... . Any comment on j2gbpvr's note, sounds identical to mine?
or on my @sub note in post #10?


k.

[Graham]

Forgive me if I am missing the bleedin' obvious ... what does your wakeup.bat do? I am guessing it restarts something to do with PCH or wotnot.

[jksmurf]

Forgive me if I am missing the bleedin' obvious ... what does your wakeup.bat do? I am guessing it restarts something to do with PCH or wotnot.

Actually it is a legacy brute force attempt by me, from before the time that sub made double wake requests, to make the PC wake up [see http://forums.nextpvr.com/showthread.php...ngs/page3], post #24 where sub adds a new Nshared which (subs words) "schedules two wakeups per recording. The second one is 30 seconds later."

This is my wakeup.bat

Code:

echo off
echo %date% %time%
devcon status "USB\VID_2040&PID_5020&REV_0000"
:Reports the source of the wakeup
powercfg -lastwake

echo on
echo: Wake Up you silly silly thing!

I could actually dispense with it, TBH, because clearly something ELSE (Windows related) wakes the PC, which then causes NRecord.exe to go "Ooooh, the PC has woken up (resumed), I better go run the Wakeup.bat script". So as a wakeup call its actually superfluous, because it is already (ostensibly) awake...

Code:

2015-10-05 03:06:39.908    [DEBUG][17]    Resuming...
2015-10-05 03:06:40.859    [DEBUG][6]    cycling MVP servers
2015-10-05 03:06:40.859    [DEBUG][6]    Starting MVP server 0
2015-10-05 03:06:47.136    [DEBUG][10]    Recording service noted the system was resuming...
2015-10-05 03:06:47.136    [DEBUG][10]    Starting: C:\Users\Public\NPVR\Scripts\Wakeup.bat
2015-10-05 03:06:50.732    [DEBUG][10]    C:\Users\Public\NPVR\Scripts\Wakeup.bat has exited

[j2gbpvr]

I reverted back to NPVR 3.3.8 last night on all three computers and have not had problems since.
I think the problem started in NPVR 3.4.8 and remained in NPVR 3.5.7.
Had to first uninstall NPVR 3.5.7 using Programs and Features.
Installed NPVR 3.3.8 and verified NRecord.exe was dated 10/25/2014 even though NPVR About still shows 3.5.7.
It kept my tuner devices and channel configuation so I didn't have to reconfigure it.
Made a copy of npvr.db3 just in case.
Will keep an eye on them to make sure it's working correctly.

[jksmurf]

sub this has got to be telling us something surely ? At least what might have been amended (dual wake-up calls?) in the later revisions, that might be going wonky in specific circumstances?

k

[j2gbpvr]

It just woke up one minutes after going to sleep on one computer so I guess that wasn't the problem.
Put it back to NPVR 3.5.7.
Not sure what else to try.

[jksmurf]

j2gbpvr -

Have you checked your setting for unattended sleep timeout - in my PC (a) it wasn't in the list of options in Power Options, I had to add it - see links below for how to and (b) it was set for 2 mins (120 secs). I have upped mine to 60mins. My sleep setting is an hour and 5mins, but what MAY have been happening is that with that option set at 2mins, the PC might go to sleep after 1hr5mins, but then NRecord wakes it up "hey buddy wake up", then being unattended it tries to nod off after 2mins and Nrecord.exe says "hey buddy wake up!" and so on.

Like the fellow in one of those links, wrote:

Code:

Unattended Sleep Timeout key (introduced with Vista). Since the default timeout is [B]120 seconds[/B], I changed that to prevent the PC from returning to Standby when it's running unattended overnight AV & MBAM scans.

http://www.sevenforums.com/tutorials/246...meout.html
http://www.tenforums.com/general-discuss...8-1-a.html

Where my theory comes unstuck is I have yet to see a clear explanation as to WHY NRecord.exe says "hey buddy wake up!" when I had no show being recorded at that time; only comskip (called from postprocesing.bat, called from Nrecord....).

k.