8VSB schedule mangled on one channel

[turndave]

I have the current version of NextPVR operating on Windows 10.  I am using two HDHomerun tuners: one the old HDHomerun Dual (HDHR3-US), and the other is the newer HDHomerun Connect Duo (HDHR5-2US).  Most of the channels are configured to use Schedules Direct, but in a few cases I need to rely on the 8VSB PSIP for EPG data due to it not being available from Schedules Direct.  Generally that works, but lately the schedule information is wildly incorrect on one specific channel (31-3... HNI).  I have tried Emptying the EPG and Updating it, as well as rebooting the computer.  I have confirmed that the schedule data for that channel is actually being broadcast correctly, both by looking at the EPG display on my TV, as well as using TSReader to monitor the HDHomerun output directly.  Note that the older tuners are first in the list of devices due to their being slightly more sensitive than the newer model.

Any ideas on how to resolve this issue?  I don't know exactly when this problem started, so I can't say for sure whether it started after I upgraded to v7.0.3 on October 2 (from v7.0.2).  I attached the logs, captured shortly after manually updating the EPG after verifying I had good reception of channel 31.

Thanks

Dave

[mvallevand]

Are you sure you aren't getting at least 4 listing for HNI?

2025-10-11 18:56:42.589 [DEBUG][7] Got 4 listings for source_id:3 (channel_oid:9015)

Frequency 31 did find listing and I didn't see errors.

If you are sure there should be more maybe create a one minute full mux of frequency 31 with TSReader or sub's program TSCapture program https://tscapture.com/ and provide an external link to the ts file. It will be around 200MB.

You shouldn't need more than 70 seconds for an ATSC scan.

Martin

[turndave]

I apparently wasn't clear.  NextPVR IS showing the usual @12 hours of EPG data... it simply bear no resemblance to what the actual EPG data is that the station broadcast.  Attached is a screenshot from the NextPVR web GUI.  And the  following URL is the TSReader capture:

https://www.dropbox.com/scl/fi/nhg5bb54m...05ypd&dl=0

Dave

[mvallevand]

Thanks yes I see the logs show that too now that I look for that problem. The channel seems to be mapped to multiple sevice IDs when not using all of them. The fullmux should help.

Maertin

[mvallevand]

Yes I confirm scanning that full with all channels a OTA it works but just 31 they are merged on the same ID.

Martin