That looked like it pretty much failed to update the epg, but nothing related to the change I made. (so never got to the log messages I added for the other issue)
If you reboot, and manually kick of an EPG update, does it work?
Actually here is another update. Functionally similar to last build, but I changed a couple of the log messages that would be confusing to others that might look at the logs. There is also one minor functional change around synchronization.
Are you sure the 03:05 recording completely failed? It appear it was recorded to disk but the tuner is now not being closed properly after a recording. I suggest using an older DeviceHostWindows since the new one has introduced a new problem.
Odd, since on tuner 7 the first attempt started and locked the tuner
2024-12-02 21:42:03.365 [DEBUG][4] Starting Stream: D:\NextPVR\Brokenwood - Mord in Neuseeland\Brokenwood - Mord in Neuseeland Das Spiel vom Tod_20241202_21452315.ts
that was marked failed because of the new bug so a second recovery attempt was made on tuner 8 and it gets an -0 meaning the original was on disk
Starting Stream: D:\NextPVR\Brokenwood - Mord in Neuseeland\Brokenwood - Mord in Neuseeland Das Spiel vom Tod_20241203_01550325-0.ts
I expect they would have both been on disk assuming you didn't delete the failed recordings. These aren't related to the EPG update just a new bug.
Hello sub. I can imagine, that it is quite difficult to find the error.
With this devicehostwindows.exe something "new" is happening:
- Changed the exe and cleared logs
- Cleared EPG
- Did an EPG scan
- Some stations are missing....... but scan worked
- Started a seconed EPG update without deleting old data -> BlueScreen
- PC restartet -> Hit EPG update -> Bluescreen
Now changing back again to an older devicehostwindows.exe
- EPG update running.
Log till to the changing back attached. I had the bluescreen on another test devicehostwindows.exe also, but cant remember wich version. The more older ones, do not do that.