NPVR v5 no longer prevents shutdown with a remote

[Lao Pan]

Sub After the release of v5.0.5 you provided a NPVRTray exe which prevented an accidental shutdown with a remote during an in-progress recordings. It would just blank the screen, leaving the computer running till the recording had finished (Awaymode?)

The tray app that was installed with v 5.0.6 appears to not have this function - you guest it, I shut down the computer during one of her recordings

I checked the logs (after zipping from the web app), but they don't go back far enough.

[sub]

I just checked the code, and it still looks like it's there. As long as your tray executable is running and the icon is green, the machine shouldn't go into full standby.

[stwarr]

I’m new to NextPVR and recently installed v5.0.6. I have the exact same problem on win10 build 2005 - the recorder service wakes the computer from sleep as expected if a recording is scheduled, the tray icon shows as red, but NextPVR does not seem to have performed the required steps to prevent reentering sleep mode during an active recording. I have confirmed this using ‘powercfg -requests’ which shows there are no active power requests during the recording. For contrast, when using SchiboPVR to drive my tuner, I *do* see active power requests registered, so this appears to be a software problem with NextPVR, and not a windows configuration issue.

I am currently trying to migrate from WMC, and not preventing sleep is a show stopper for me. Any chance of a fix soon?

[pkscout]

I’m new to NextPVR and recently installed v5.0.6. I have the exact same problem on win10 build 2005 - the recorder service wakes the computer from sleep as expected if a recording is scheduled, the tray icon shows as red, but NextPVR does not seem to have performed the required steps to prevent reentering sleep mode during an active recording. I have confirmed this using ‘powercfg -requests’ which shows there are no active power requests during the recording. For contrast, when using SchiboPVR to drive my tuner, I *do* see active power requests registered, so this appears to be a software problem with NextPVR, and not a windows configuration issue.

I am currently trying to migrate from WMC, and not preventing sleep is a show stopper for me. Any chance of a fix soon?

I suspect the chances would be much higher if you posted some logs demonstrating the behavior.

[stwarr]

I removed all existing logs, restarted the recording service, initiated a recording and then put the computer into sleep.

From nrecord.log:

Code:

2020-06-30 10:50:09.042 [DEBUG][9] allocating recording target filename: R:\Recorded TV\Homes Under the Hammer\Homes Under the Hammer.S23E16.ts
2020-06-30 10:50:09.042 [DEBUG][9] About to start recording (866 on 21): R:\Recorded TV\Homes Under the Hammer\Homes Under the Hammer.S23E16.ts...
2020-06-30 10:50:09.042 [DEBUG][9] (Recording is due to be stopped at 30/06/2020 11:45)
2020-06-30 10:50:09.043 [DEBUG][9] Free space 472914997248  (R:\)
2020-06-30 10:50:09.048 [DEBUG][9] Starting device host:
2020-06-30 10:50:09.048 [DEBUG][9] "C:\Program Files\NextPVR\DeviceHostWindows.exe" -listen:56878 -type:DVB-T -device:"TBS 6205 DVB-T/T2 Tuner 0" -instance:1 -parent:5328
2020-06-30 10:50:09.153 [DEBUG][9] http://localhost:56878/stream/start?slipseconds=7200&target=R%3A%5CRecorded%20TV%5CHomes%20Under%20the%20Hammer%5CHomes%20Under%20the%20Hammer.S23E16.ts
2020-06-30 10:50:09.384 [DEBUG][9] <stream>
  <handle>1</handle>
  <reason></reason>
</stream>
2020-06-30 10:50:09.384 [DEBUG][9] Started recording (866:1:R:\Recorded TV\Homes Under the Hammer\Homes Under the Hammer.S23E16.ts)

then at the point the PC went to sleep:

Code:

2020-06-30 10:50:35.402 [DEBUG][40] OnSleep...
2020-06-30 10:52:51.154 [DEBUG][4] OnResume...

  logs-20200630-1053.zip (Size: 37.55 KB / Downloads: 3)

[sub]

the recorder service wakes the computer from sleep as expected if a recording is scheduled, the tray icon shows as red, but NextPVR does not seem to have performed the required steps to prevent reentering sleep mode during an active recording.

Are you talking about idle sleep (where machine is configured to go to sleep after x minutes of inactivity), or the user actively choosing 'standby' from the Windows menu?

The former should absolutely be working, and has been in NextPVR since the beginning, and we know a lot of people rely on it.

The latter is a little more complicated, and needs to have NextPVRTray.exe running for a logged in user.

[sub]

I'd suggest setting <LogPowerManagement>true</LogPowerManagement> in the <General> section of config.xml file, then restart the NextPVR service, then reproduce the problem and supply the logs again

[stwarr]

Same sequence, but this time with <LogPowerManagement> set, and with the NextPVR service running as the desktop user/password rather than as SYSTEM:

  logs-20200701-1141.zip (Size: 26.77 KB / Downloads: 1)

The logs seem a bit confused to my eyes, but the service seems to recognise that it should be preventing standby mode, but fails to do so (as before, no system 'powercfg' entries are being created):

Code:

2020-07-01 11:37:28.943 [DEBUG][9] Started recording (873:1:R:\Recorded TV\Politics Live\Politics Live_20200701_11151300.ts)
2020-07-01 11:37:28.969 [DEBUG][9] No C:\Users\Public\NPVR-data\scripts\ParallelProcessing.bat
2020-07-01 11:37:29.284 [DEBUG][9] PowerManagement PreventStandby
2020-07-01 11:37:31.621 [DEBUG][20] http://localhost:49887/status
2020-07-01 11:37:31.624 [DEBUG][20] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
<Status>
  <Device oid="21" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 0)">
    <Recording handle="150001">R:\Recorded TV\Politics Live\Politics Live_20200701_11151300.ts</Recording>
  </Device>
<Device oid="22" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 1)"> </Device>
<Device oid="23" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 2)"> </Device>
<Device oid="24" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 3)"> </Device>
</Status>
</rsp>
2020-07-01 11:37:36.614 [DEBUG][12] http://localhost:49887/status
2020-07-01 11:37:39.571 [DEBUG][12] OnSleep...

After about 4 mins, I woke the PC again:

Code:

2020-07-01 11:41:26.506 [DEBUG][33] http://localhost:49887/status
2020-07-01 11:41:26.736 [DEBUG][9] PowerManagement PreventStandby
2020-07-01 11:41:27.162 [DEBUG][18] OnResume...
2020-07-01 11:41:27.168 [DEBUG][18] stopping device process
2020-07-01 11:41:27.198 [DEBUG][4] OnResume...
2020-07-01 11:41:31.489 [DEBUG][18] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
<Status>
<Device oid="21" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 0)"> </Device>
<Device oid="22" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 1)"> </Device>
<Device oid="23" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 2)"> </Device>
<Device oid="24" identifier="Local Recorder (TBS 6205 DVB-T/T2 Tuner 3)"> </Device>
</Status>
</rsp>

[sub]

Are you talking about idle sleep (where machine is configured to go to sleep after x minutes of inactivity), or the user actively choosing 'standby' from the Windows menu?

[sub]

For the former (machine configured to go to sleep after x minutes of inactivity), these "PowerManagement PreventStandby" messages should happen every 60 seconds, and indicate a call to tell Windows the machine is still in use. These are enough to keep the machine awake while recording. These do not show with powercfg. (these do not stop a Windows going to sleep when you force it however)t