Severe intermittent TS corruption with Hauppauge WinTV-dualHD tuner

[acemib]

I'm hoping someone can help diagnose an issue I've spent several days troubleshooting.
System:

• NextPVR v7.1.1.260616 on a Windows Beelink mini PC
  
• Hauppauge WinTV-dualHD USB ATSC tuner
  
• Indoor antenna receiving Madison, Wisconsin OTA channels
  
• Kodi on Hisense Google TV and NextPVR app on iPad (for this zip file)
  
• BPVR server connected via Ethernet
  

Problem:
NextPVR intermittently produces severe pixelation, audio stuttering, and corrupted transport-stream recordings.
Initially, the problem appeared primarily during simultaneous streaming. The first stream would work well, but the second would pixelate severely, regardless of whether Kodi or the iPad started first.
Further testing revealed that either tuner can also produce severe corruption while operating alone.
The behavior is intermittent. A stream may start with terrible pixelation, gradually improve after 1–3 minutes, then deteriorate again without any intervention.
Troubleshooting completed:

• Tested both tuners independently, with the other disabled.
  
• Tested simultaneous streams in both startup orders.
  
• Independently rescanned each tuner instead of copying channel configurations.
  
• Disabled digital tuner priming.
  
• Restarted NextPVR services.
  
• Reproduced corruption in saved NextPVR live-TV transport-stream files.
  
• Created an actual NextPVR recording, separate from live playback.
  
• Tested the same antenna and Hauppauge device using Hauppauge WinTV.
  

Important comparison:
WinTV live playback is stable, and a recording made using WinTV played back cleanly.
However, NextPVR recordings using the same hardware exhibit severe corruption.
The problem is present in the recorded transport-stream files themselves, not just Kodi or iPad playback.
Latest confirmed failure — October 23, 2026:
At approximately 10:58:54 a.m., I initiated a WISC recording through Kodi using NextPVR.
The device log identifies Hauppauge WinTV-dualHD ATSC Tuner 1.
At 10:58:57, NextPVR reported:

Code:

locked=1, present=1, strength=45, quality=100

The resulting recording,

Code:

WISC_20261023_10581158.ts

, was severely pixelated.
An analysis of the approximately 105-second recording found roughly:

• 484,356 MPEG transport packets
  
• 7,700 video continuity-counter errors
  
• 790 audio continuity-counter errors
  

Additional signal-strength findings:
Reviewing earlier device logs from October 22–23, I found that successful tuner locks typically reported signal strength around 45–62, with quality usually 100.
There were occasional lower quality readings:

• October 23, 09:02:50 — Tuner 2: strength 45, quality 80
  
• October 23, 09:42:03 — Tuner 1: strength 46, quality 89
  
• October 23, 10:58:57 — Tuner 1: strength 45, quality 100, despite the corrupted recording
  

I recognize that signal-strength values are driver-reported and may not be directly comparable to other devices.
My questions:

1. Does this evidence suggest a Hauppauge BDA driver/capture issue, NextPVR's transport-stream handling, or something else?
   
2. Why would NextPVR report quality 100 and a successful lock while recording a heavily corrupted MPEG transport stream?
   
3. Is there a specific driver, logging option, or targeted diagnostic that could distinguish the capture paths used by NextPVR and WinTV?
   

I would prefer not to repeat channel scans, reinstalls, since both tuners can produce clean video and have been extensively tested.
Attached:

Code:

NextPVR_forum_logs_2026-10-23_SAFE.zip

I can provide the corrupted WISC

Code:

.ts

recording if needed.
Thank you for any guidance!

[mvallevand]

NextPVR reports what the driver gives nothing more and these are unreliable. There would be nothing we could do to help you AI explanation. Quality 100 and high values can actually be bad especially if you are using booster and/or splitters. It can also be cell tower and other RF interference.

Good luck checking the physical connections.

Martin