Intermittent EPG update failure

[turndave]

From time to time, the EPG fails to update.  I mostly use Schedules Direct, but have a few channels I use  8VSB for EPG source.  I have two HDHR3-US tuners and two HDHR5-2US tuners.  Using Windows 10 with the current version of NextPVR.  When the problem is occurring, the guide update process quickly retrieves the Schedules Direct data and then stalls before getting the 8VSB data.  If I look at the "NextPVR Backend Status", only one of the tuners is shown as active, but it has a strange looking entry (see attached screenshot).  If I restart the NextPVR service, this strange entry is no longer there and EPG updates work fine... for now.

Attached also are the logs.

Dave

[mvallevand]

I can see how it happened, the tuner service stopped sending data for most of your 2 minute scan,

2025-12-16 05:13:39.262 [DEBUG][58] DeviceHost stream has stopped

2025-12-16 05:13:41.627 [DEBUG][10] Processed 83848 bytes
2025-12-16 05:15:39.955 [INFO][5] Got POST request: /stream/start?slipseconds=1200&pids=8187

but I can't tell you why. That gap left the tuner in a bad state.

Martin

[mvallevand]

Did you change anything with your system since you applied this patch https://forums.nextpvr.com/showthread.ph...#pid604294

Martin

[turndave]

Not that I recall, other than perhaps rescanning channels at some point. And not long ago I tried switching a few channels I had set for ATSC EPG to Schedules Direct to see if the latter had good guide data yet, and then switched those channels back to using ATSC EPG data.

It is a Windows 10 machine, so I signed up for the MS extended service a month or so ago until I have a chance to deal with replacing the computer, but I can't see how that would affect NextPVR.

[mvallevand]

OK thanks. Could you can confirm NShared.dll is dated in October that would help I thought there was some protection against this sequence in that patch, but I guess not.

Code:

2025-12-16 05:13:39.154    [DEBUG][58]    parsing MGT C7
2025-12-16 05:13:39.155    [DEBUG][58]    TVCT (1): 0x1ffb
2025-12-16 05:13:39.155    [DEBUG][58]    EIT-0: 0x1408
2025-12-16 05:13:39.155    [DEBUG][58]    EIT-1: 0x1409
2025-12-16 05:13:39.155    [DEBUG][58]    EIT-2: 0x140a
2025-12-16 05:13:39.155    [DEBUG][58]    EIT-3: 0x140b
2025-12-16 05:13:39.155    [DEBUG][58]    ETT-0: 0x1388
2025-12-16 05:13:39.155    [DEBUG][58]    ETT-1: 0x1389
2025-12-16 05:13:39.155    [DEBUG][58]    ETT-2: 0x138a
2025-12-16 05:13:39.155    [DEBUG][58]    ETT-3: 0x138b
2025-12-16 05:13:39.155    [DEBUG][58]    got MGT [EIT pids 4, ETT pids 4]
2025-12-16 05:13:39.161    [DEBUG][59]    SourceATSC.Reset()...

[turndave]

It is dated October 22.

[mvallevand]

Thanks for checking.

Martin

[turndave]

The next time this happens, what should I do to help isolate the problem? What is the best timing for collecting the logs? When I first notice the guide hasn't updated? Or after I have manually triggered the guide update and it has "stalled" (apparently after retrieving Schedules Direct data and before it can retrieve 8VSB data)? At some other point?

Dave

[mvallevand]

Wait for the next.version and once you see the pipe stuck in the logs or empty ATSC channels post the logs.

Martin