I can update tomorrow and will report if the problem persists in 2.3.6.
Server: Core2Duo 3,16GHz| Windows 7 Ultimate 64 bit | NPVR 3.2.9 | Analogue: Hauppauge PVR-150 | Digital dvb-c: Technisat CableStar HD 2 | No plugins
Clients: Laptop Windows 7 Home 64 bit via Wifi | Android tablet via Wifi | Androidbox s89-H via Lan
Updated to 2.3.6. there's improvement, but problem not solved:
After reboot: everything normal
After reboot, sleep and wake:
- ntray functions normally
- NPVR: I can program a recording, but nothing is recorded. I can cancel a recording without a freeze.
Then after restarting recording service through ntray: ntray and npvr freeze.
Server: Core2Duo 3,16GHz| Windows 7 Ultimate 64 bit | NPVR 3.2.9 | Analogue: Hauppauge PVR-150 | Digital dvb-c: Technisat CableStar HD 2 | No plugins
Clients: Laptop Windows 7 Home 64 bit via Wifi | Android tablet via Wifi | Androidbox s89-H via Lan
It sounds to me like your device is locking up after standby (some driver issue probably) and no longer functioning, then you're trying to stop and restart the recording service, but because it's lockup up in some driver call, the process refuses to exit. When the recording service attempts to restart it fails to get the sockets it needs, since they're already in-use in the old nrecord.exe that is still loaded.
Perhaps a "taskkill /F /IM NDigitalHost.exe" in WakeUp.bat would take care of the issue? If it's able to kill off NDigitalHost, that should release the device and then NRecord can spin up a new NDigitalHost.
(other posts in this thread mention a "resume.bat" but I have it in my notes as "WakeUp.bat"... which is it?)
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
I don't use the digital card, (I think that's why) I don't have a NDigitalHost.exe .
My graphics card (not the tv-cards) has a driver problem waking from sleep but functions normal in every other way (also after waking from sleep).
Could this cause my problem? I haven't got any other problems with drivers, windows or the graphics card.
Server: Core2Duo 3,16GHz| Windows 7 Ultimate 64 bit | NPVR 3.2.9 | Analogue: Hauppauge PVR-150 | Digital dvb-c: Technisat CableStar HD 2 | No plugins
Clients: Laptop Windows 7 Home 64 bit via Wifi | Android tablet via Wifi | Androidbox s89-H via Lan
oh, I sometimes just ASSume everyone else's configuration is the same as mine. There is your analog card though, right there in your signature.
@sub: the reason I can't get it through my head that Analog cards don't use NDigitalHost to record is that until now Digital and Analog cards seemed to work exactly the same - they just need the ts mux and possibly the software encoder, but after that Analog cards always looked just like Digital cards in the logs. Is there any reason Analog cards can't/shouldn't record using NDigitalHost too, or is it just a case of "haven't done it yet"?
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
Quote:@sub: the reason I can't get it through my head that Analog cards don't use NDigitalHost to record is that until now Digital and Analog cards seemed to work exactly the same - they just need the ts mux and possibly the software encoder, but after that Analog cards always looked just like Digital cards in the logs. Is there any reason Analog cards can't/shouldn't record using NDigitalHost too, or is it just a case of "haven't done it yet"?
There wasn't an easy way to do it for all capture devices, and I haven't seen any particular problem that was going to be helped by doing this work for analog as well, so I just focused on digital.
This goes above my understanding. Could my graphics driver wake problem cause my problem? Or is there a workaround for me?
What can I do?
Server: Core2Duo 3,16GHz| Windows 7 Ultimate 64 bit | NPVR 3.2.9 | Analogue: Hauppauge PVR-150 | Digital dvb-c: Technisat CableStar HD 2 | No plugins
Clients: Laptop Windows 7 Home 64 bit via Wifi | Android tablet via Wifi | Androidbox s89-H via Lan
As mentioned above, I suspect it's an issue with a device looking up in a driver after standby. Its most likely whatever capture device is you're trying to use. It might be an issue with the PVR150 on Win7 64bit or something similar. If thats the case, there probably isn't much you could do other than look for a different version of the driver that doesn't have that problem, or avoid using standby.