You do realize that PostProcessing is called at the end of each recording?
Case: You have two simultaneous recordings going on. Once the first one ends, PostProcessing will be called, and the hibernation will be forced by "shutdown /h". And you lose the rest of the other program. NPVR is (in almost all situations) unable to stop the computer from hibernating if a specific request is made (ie, if its not triggered by Windows' idle timer)
You are better off, troubleshooting why your computer refuses to hibernate. Have you checked the BIOS settings (also worth checking regarding WOL from outside the LAN)? You might need to enable support for hibernation. And windows itself needs to be set to allow it.
I had so many problems with win7 sleep timers causing my PC to not start recording when due, cut off recordings and cutting off subsequent transcoding through postprocessing.bat, I abandoned them. The transcodes would resume on waking the PC but I wanted the CPU intensive stuff to happen overnight as the PC runs up its cooling fans which is noisy.
This lead me to:
- Chose "never" sleep in the power settings.
- Use the event scheduler to wake the PC just before 6pm every night, because it is the News usually my first recording in the evening. I believe later versions of NPVR has addressed the wakeup before recording issues so this may be superfluous now.
- I use pBS's awaymodeactive program which prevents PC sleep or shutdown, again this may now be addressed within NPVR.
- I transcode from midnight when recording has generally finished and I have usually gone to bed. Each postprocessing.bat creates a file with OID.ppr as the filename (OID is a unique recording ID) which is deleted when that particular postprocessing has finished, it then looks to see if any other *.ppr files exist. If there are none then this is the last postprocessing.bat file that has executed so it tells the PC to go to sleep.
Some of this may not be required now, but it works for me so I will leave it as is for now.
It may be worth having a look at "Power Triggers" which can be set to perform a range of actions when the computer suspends or resumes. I had a problem with the network card on my server where sometimes on resume it could not see the NextPVR client although it was on the Internet but restarting the network device would cure the problem. I now use Power Triggers to restart the network card every time the server resumes and not had the problem since. You can Start, Stop or Restart any Services, Devices or Process at Suspend or Resume.
Sykor Wrote:You do realize that PostProcessing is called at the end of each recording?
Case: You have two simultaneous recordings going on. Once the first one ends, PostProcessing will be called, and the hibernation will be forced by "shutdown /h". And you lose the rest of the other program. NPVR is (in almost all situations) unable to stop the computer from hibernating if a specific request is made (ie, if its not triggered by Windows' idle timer)
I was testing the situation with 3 different recordings one after another and there was no problems, after each recording pc went to hibernate and it woke up before next schedule. So I am satisfied how the system reacts.
jcjefferies Wrote:It may be worth having a look at "Power Triggers" which can be set to perform a range of actions when the computer suspends or resumes. I had a problem with the network card on my server where sometimes on resume it could not see the NextPVR client although it was on the Internet but restarting the network device would cure the problem. I now use Power Triggers to restart the network card every time the server resumes and not had the problem since. You can Start, Stop or Restart any Services, Devices or Process at Suspend or Resume.
I've just test Power triggers to start my BR drive from sleep - no luck, I got red cross. I think there might be hardware problem related my mobo-BR drive combination (with latest mobo drivers, bios update and BR-rom firmware!)