No standby after update to Version 7

[Escape7]

Hello sub and Martin.

I changed the devicehostwindows.exe back to the original one. The other files are still updated.

This morning: EPG did run, PC was standby.

Logs attached. I had this behavior previously. With the updated nshared.dll standby worked.

@Martin -> How messy do the tuners look with the original devicehost?

Peter

[mvallevand]

The closing is fine after a recording or EPG update. I don't understand the sync issue since I don't know the code just the logs, but on each frequency tune there is a brief time that DeviceHostWindows is reading from two frequencies, whether that is physical or just data buffers I am not sure.

Where I have seen the big problem (not in your recent logs) is if the first stream doesn't send data the tuner gets disconnected but then the second thread tries to read from the closed tuner. When it

Code:

2024-12-21 03:01:36.424    [DEBUG][4]    StartStream(): \\.\pipe\NPVR_fee27e2a-e912-43fa-81ed-97573d726d6a:pids=18
...
2024-12-21 03:01:36.785    [DEBUG][4]    pipe client connected (NPVR_fee27e2a-e912-43fa-81ed-97573d726d6a)
2024-12-21 03:01:37.271    [DEBUG][4]    Processed 83848 bytes
2024-12-21 03:02:37.868    [DEBUG][4]    Previous line repeated 1197 times
...
2024-12-21 03:02:37.898    [DEBUG][5]    StartStream(): \\.\pipe\NPVR_145fb6fc-da4e-4851-8a58-92a630379deb:pids=18
...
2024-12-21 03:02:38.153    [DEBUG][5]    pipe client connected (NPVR_145fb6fc-da4e-4851-8a58-92a630379deb)
2024-12-21 03:02:38.216    [DEBUG][4]    Processed 83848 bytes
2024-12-21 03:02:38.415    [DEBUG][5]    Processed 83848 bytes
2024-12-21 03:02:38.433    [DEBUG][4]    Processed 83848 bytes
2024-12-21 03:02:38.614    [DEBUG][5]    Processed 83848 bytes
2024-12-21 03:02:38.632    [DEBUG][4]    Processed 83848 bytes
2024-12-21 03:02:38.704    [DEBUG][5]    Processed 83848 bytes
2024-12-21 03:02:38.794    [DEBUG][5]    Processed 83848 bytes
2024-12-21 03:02:38.830    [DEBUG][4]    Processed 83848 bytes
2024-12-21 03:02:38.867    [DEBUG][5]    Processed 83848 bytes
2024-12-21 03:02:39.030    [DEBUG][5]    Previous line repeated 2 times
2024-12-21 03:02:39.047    [DEBUG][4]    Processed 83848 bytes
2024-12-21 03:02:39.101    [DEBUG][5]    Processed 83848 bytes
2024-12-21 03:02:39.247    [DEBUG][5]    Previous line repeated 2 times
2024-12-21 03:02:39.249    [DEBUG][4]    pipe client disconnected (NPVR_fee27e2a-e912-43fa-81ed-97573d726d6a)

I think this translates to these message on the server though, since the tail of the one thread [49] and the head of the other [36] are both using the same data.

Code:

2024-12-21 03:02:38.216    [ERROR][49]    TS continuity counter indicates missing packets
2024-12-21 03:02:38.415    [ERROR][36]    TS continuity counter indicates missing packets
2024-12-21 03:02:38.433    [ERROR][49]    TS continuity counter indicates missing packets
2024-12-21 03:02:38.614    [ERROR][36]    TS continuity counter indicates missing packets
2024-12-21 03:02:38.704    [ERROR][36]    TS continuity counter indicates missing packets
2024-12-21 03:02:38.831    [ERROR][49]    TS continuity counter indicates missing packets
2024-12-21 03:02:38.867    [ERROR][36]    TS continuity counter indicates missing packets
2024-12-21 03:02:39.063    [DEBUG][49]    DeviceHost stream has stopped

Martin

[Escape7]

OK, i also dont unterstand what that means.

But just for my head and thinking:

- This all startet, because with v7 there was the problem that standby was prevented after the EPG update.
- sub modded/changed the devicehostwindows.exe to get that problem fixed
- Then we had other things, like EPG detail data getting cut off -> sub changed the nshared.dll + as continued to modify the devicehostwindows.exe
- Problems with bluescreens came up
- From this point on i changed back to the original devicehost -> Bluescreen gone and standby worked
- So the initial standby problem seams to be caused bei the nshared.dll and not from devicehost -> am i getting that right?

- Now we have the newest nahared.dll + newest npvrtsmon.ax + newest devicehostwindows.exe -> Bluescreen because tuners do not get released
- newest nahared.dll + newest npvrtsmon.ax + original devicehostwindows.exe -> Some strange things in the logs, but everythings is working fine -> standby works, EPG works and is not cut of

So the original devicehostwindows.exe is not the problem for standby (i know i repeat) -> Perhaps only the strange logs need to get "cleared" / fixed and the rest of devicehostwindows.exe is absolutly ok?

I am no programmer, but all started with the standby problem, and that was fixed by nshared.dll (in my head).

[mvallevand]

There never was a standby problem. NextPVR doesn't even tell the PC to go to standby but it does tell Windows not to sleep during recordings. That pipe: message in the recording list was the issue, NextPVR was telling Windows it was recording because of a sync error. I am sure that the changes in NShared help but work is needed in DeviceHostWindows too.

The BSOD is related to the sync issue, you just never experienced it others did, so your tuners acts differently. The fact that many of us including sub don't have the sync issue makes it hard to diagnose. EPG detail truncation is not related.

What is clear from your logs is as soon as the graph is not begin used the tuner is closed.

2024-12-21 03:35:34.054 [DEBUG][15] pipe client disconnected (NPVR_87dad01a-41c5-49af-a573-cf8a9dbead63)
2024-12-21 03:35:34.055 [DEBUG][15] About to request async graph stop

I feel the missig piece for sub is ensuring that the tuner doesn't get closed during the entire EPG update for everyone.

Martin

[sub]

I just spent the last couple of hours looking at this, and really couldn't see any sign of an issue here. Everything looked like it was working correctly, so difficult to understand what the problem might be.

I've attached the latest version of the relevant files, which are in the state they'll be in future releases unless we can identify a specific issue. I'd suggest you try these new versions, because other you'll be stuck if you're relying on old versions of files.

[sub]

If it still has the issue, we might need to try getting you to create a c:\temp directory, and set HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR\LogTSFlow=1 (DWORD) in the registry, then restart your server. It'll create a c:\temp\mon.txt log file with some more low level logging info.

[Escape7]

Hello sub. I will start testing right now.

Extra Logging is enabled. Old Loggs cleared.

[Escape7]

So here are the test results:

As mentioned i updated the 3 files. Cleared old logs. Restarted PC.

- Did an EPG Update -> worked fine
- Did (for testing) recordings. And used KODI for watching a recorded show
- As soon as "Terra X" recording ended -> Bluescreen


Logs attached, i reverted back to the old devicehostwindows.exe -> the 2 other files keep new.

[sub]

Does your windows event viewer show any details about the BSOD?

[sub]

I'm kind of running out of options really. I'm not even really sure there is a problem beyond your device.

Have you tried running with 'keep digital devices primed'? This at least avoids the stopping the device, which is the time your machine has issues.