sub Wrote: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.
fair enough. Mostly that was a 'just curious' question.
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
WKleeven Wrote:After sleep and wake, I manually stopped nrecord.exe, ntray.exe and nextpvr.exe then "start NPVR service" from startmenu.
NTray is frozen, I can start NPVR from startmenu, I can program a recording, recordings starts but when I try to cancel the recording NPVR freezes.
After a reboot(!), I did a "stop NPVR service", then I let the pc go to sleep and wake up again, then "start NPVR service". Everything works normal!
After a reboot(!), I manually stopped ntray.exe and nrecord.exe but not nextpvr.exe, let the pc go to sleep and wake again. Lots of problems again.
If you want me to try another combination, to further investigate the source of the problem, please let me know.
Wim
I don't understand how if it's a driver issue, I can record after waking from sleep (first situation I describe in post #17, see above).
I think the database-file is locked after wake from sleep that's causing the problem, not the driver.
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
First situation in post #43 described above. After the recording has finished, I can view the recording, but I can't delete the recording (NPVR freezes again).
But I notice a file that keeps popping up "npvr.db3-journal" in the NPVR directory, but npvr.db3 doesn't get a new time. Could it be something is trying to update npvr.db3, but it doesn't succeed?
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
Regarding the locked database, are you running any plugins? Can you see if running without them has the same problem? We've seen problems causing database lock problems in the past.
I think I've got only the system plugin, but I attached some files so you can check for yourself.
How do I remove the plugin? Is it enough to unselect in settings, or do I have to delete the folder "System" in "Plugins"? Or something else?
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
Just when I was testing disabling the plugin, my wife wanted me to record a show. I had time to try just once and this time (hopefully always, I will check tomorrow and post again) everthing is normal!
I've had problems with plugins before. It's too bad, these things happen.
I'll report tomorrow after more testing, just to be sure.
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
I am very happy to report that disabling the System plugin solved my problem!
Thanks everybody for the help.
Wim
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
WKleeven Wrote:I am very happy to report that disabling the System plugin solved my problem!
Not that I don't believe you, but the System plugin doesn't do anything (that I'm aware of) that would try to update the npvr database. It does make calls - via the API - for accessing the database, but doesn't do anything that would cause writes or a lock. Are you sure it's not just coincidence that disabling it has helped?