Posted by: Rob - 2026-10-25, 12:45 PM - Forum: Windows
- Replies (1)
ubject: NextPVR does not detect AVerMedia A825 USB Dual DVB-T tuner on Windows 11
Hello,
I'm trying to use an older AVerMedia A825 USB Dual DVB-T tuner with NextPVR on Windows 11, but NextPVR detects only the IPTV Device. System details
Operating system: Windows 11, version 26H2, OS Build 26300.9711
Tuner: AVerMedia A825 USB Dual DVB-T
Hardware ID:
Code:
USB\VID_07CA&PID_0825&REV_0201
Driver provider: AVerMedia
Driver version: 8.0.64.70 (dated 5 June 2013)
What I've tried
Windows Device Manager lists the tuner and reports that it is working properly, with no yellow warning triangle.
The tuner driver is installed.
NextPVR Service is running.
I clicked Rescan for devices in NextPVR several times, including after restarting the service.
NextPVR continues to list only IPTV Device.
In
Code:
C:\Users\Public\NPVR-data\logs
,
Code:
NRecord.log.1
contains the IPTV device information but no occurrences of
Code:
AVerMedia
or
Code:
BDA
. Neither
Code:
NDigitalHost.log
nor
Code:
NDigitalHost.log.1
exists.
The same tuner was previously detected by the old AVerMedia software, which could scan channels but crashed when I selected a channel for playback. Windows still recognises the tuner.
Could someone advise how to diagnose why NextPVR does not discover this tuner? Is there a driver, BDA compatibility, or device-discovery issue I should investigate?
Thank you.
Hello,
I know I asked this question a few years back but for the life of me I cannot find the response. Where will I find instructions on how to install yauiclient?
since it is not opening do I send logs of the Nextpvr server or the client pc? If it is the client pc how do I get the logs from the yauiclient client pc?
Thank you for your time again.
Bruce
Hello,
I have another computer acting up This time I get a pop up from my antivirus. Is it active or a false positive?
Logs included as well as a screen shot.
Be advised my channels open fine on my phone with another iptv player.
Thank you,
Bruce
Hello,
Its been a long time being on here. I have an issue with Nextpvr not opening channels. I have upgraded to the latest version of Nexttpvr.
Logs included.
Thank you for you time
Bruce
Was watching live TV and got the message about the tuner being required.
2026-10-24 12:52:29.025 [WARN][92] The tuner you were using was required for a recording (UIController)
No recordings were in progress, only one was upcoming.
I have a HDHomeRun quad, so I would have expected the upcoming recording to use a second tuner automatically.
I exited the live recording, grabbed the log. Went back to watch live TV and wound up getting the message again. Second log attached as well...
Art
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:
Does this evidence suggest a Hauppauge BDA driver/capture issue, NextPVR's transport-stream handling, or something else?
Why would NextPVR report quality 100 and a successful lock while recording a heavily corrupted MPEG transport stream?
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:
I left the house early yesterday without watching anything and in the evening couldn't connect from a client machine. Had to hard boot the server, so I grabbed the logs.
In nrecord.log.2 it looks like this where things went sideways:
2026-10-13 06:45:07.197 [DEBUG][37] > Waiting for 60 seconds, press a key to
Art
