I just updated NextPVR and can't seem to update EPG.
Seems to be in an endless "Scanning Freq: _ " loop.
I don't use Windows on a regular basis, but EPG seemed to work before this.
I noticed that I have DVB/ATSC EPG and Schedules Direct options... I usually use Schedules Direct on Linux.
Is DVB/ATSC EPG necessary? Didn't see any way to change anything other than DVB/ATSC EPG options/settings.
I'm giving NextPVR a try and am having an issue I'm hoping someone can assist with. When playing several OTA stations (their IPTV versions as well) the video plays for 5-10 sec, pauses, then resumes but with the audio distorted. It almost sounds as if it's slowed down but remains in sync with the video.
I'm running NextPVR in docker on an Unraid server. I've tried transcoding via CPU and VAAPI but it has the same results. I also tried linking NextPVR to my Emby server and running it through that but it has the same results.
I ran 4.2.4 on my Win7 machine until early 2025 with an older version of Kodi on 3 different Nvidia Shields and everything worked great. In early 2025 I upgraded to Windows 10 finally and then I updated to NextPVR 297.0.1.241229 and I updated Kodi on a couple of my Shields. I remember everything working well but I haven't used NPVR to record until now. Unfortunately I never uninstalled 4.2.4 and they are both running on this machine.
I am pretty sure 7.0.1 is placed in C:\ProgramFiles\NPVR and the data directory for 7.0.1 is C:\Users\Public\NPVR-data\ I couldn't get the web interface to load and I remembered that I had changed it to a different port since 4.2.4 was still on the machine. I looked through the \NPVR-data\config.xml file and found that I had changed it to 8867. So the web interface seems to be working and so I assume the 7.0.1 service is running.
But tonight I quickly tried to start a recording. I went to the system tray, right clicked on NPVR, then clicked "Start NextPVR". But after starting the recording, I noticed that it was the old 4.2.4 client. I then noticed in Task Manager -> Startup that NTray is loading from C:\Program Files (x86)\NPVR which I assume is the 4.2.4 installation direction. But in Services, I notice that the location of the service that is started is C:\Program Files\NextPVR\NextPVRService.exe, so I assume the 7.0.1 service is running.
Is the old 4.2.4 client still able to record using the 7.0.1 service? I'm just a bit confused about what is 4.2.4 and what is 7.0.1. I have the older Kodi and older NPVR add-on on one Shield. I was able to start a recording on that Shield and it created a file on my computer, but the file was just 0 bytes and that Kodi does not show the recording I had created on the computer with the 4.2.4 client, although the newer Kodi's on the other two Shields do show the recording created with the 4.2.4 client on the computer.
Will just uninstalling 4.2.4 solve my issues/confusion? Thanks.
Brand new Windows 11 Geekom PC. Fresh install of NextPVR, copying setup from old machine per discussion on other thread. Last night went to watch NBC Nightly News, which was recording about 5 minutes in. Would not open. Tried watching live, would not open. CBS recorded at the same time and was watchable. No message about unable to get signal. Live watching worked fine via TV directly.
It appears that HD HomeRun ending in 306 has an issue, potentially with the 2nd tuner, which is where NBC was recording to my inspection. Log files are a bit confusing to me, so I've attached.
306 was the same tuner having issues before, but we thought it was just a refresh issue... I have one other HD HomeRun I could swap in if that's the issue, but don't want to if that's not the issue.
I don't understand why if NextPVR can't use it, it doesn't grab another tuner. 306 0 and 1 are the first on the priority list.
When I use HD HomeRun software, I can watch all 4 tuners live no problem.
I am looking at an alternate addon for scanning DVB-S in the UK for Astra 28.2 and I assume I need to support Freesat and Sky channel number but I have some questions.
- Do those of you who use DVB-S know how to use the tables here https://mizar.mythtv.org/wiki/DVB_UK
- Does anyone know what the G2 table is here https://www.satellite-calculations.com/D...Number.php
- For Freesat SD it doesn't look like any channels are regionalized, what is the purpose of using a bouquet for them in England (not in Scotland, Wales or NI)?
I've been fighting with the episode guide not loading, and just stumbled across a weird solution/bug.
When load the XMLTV file via httpS, the instance refuses to parse and WILL NOT load it. The process always claims 0 new/0 inserted/0 updated after EPG update is run. There are no errors in the logs, just normal attempts to process from what I can see.
After trying 100 other things, I switched over to plain-text http, and like magic the exact same file loads perfectly. File itself is static and the SSL cert is a trusted from LetsEncrypt provider. This makes absolutely no sense.
The URL to Guide is pulled via the domain where the cert is valid, so it's not a DNS mis-match issue or anything like that.
Issuer Name
Country US Organization Let's Encrypt Common Name E5
Validity
Not Before Wed, 06 Aug 2025 [REDACTED] GMT Not After Tue, 04 Nov 2025 [REDACTED] GMT
Subject Alt Names
DNS Name *.redacteddomain.com DNS Name redacteddomain.com
Public Key Info
Algorithm Elliptic Curve Key Size 384 Public Value [REDACTED]
Miscellaneous
Serial Number [REDACTED] Signature Algorithm ECDSA with SHA-384 Version 3 Download PEM (cert)PEM (chain)
Just for reference, both `wget` and `curl` running on the linux machine are perfectly fine with the SSL connection to pull the xmltv.xml file...
In the weeks since that discussion came to its conclusion, all the necessary equipment has arrived. In order to learn by doing things stepwise from simple to complex, I began by installing a Hauppauge ATSC tuner and NextPVR on one computer, just to get in some practice with the setup and usage processes.
That went well, so I moved over to the intended system, which includes a Verizon (Arris) IPC1100 P2 set-top box, a Hauppauge HDPVR2, a dedicated Windows 11 laptop, and the current version of NextPVR on the laptop.
For practice, I managed to get WinTV 10 to display the channel that the STB is tuned to. (To keep things simple, I had connected the STB to the HDPVR2 via component.) First success. Then I tried doing a manual recording in WinTV, and that worked too. Second success.
Next I tried setting up the Hauppauge IR blaster... and this has been a total FAIL. I haven't found a comprehensive, step-by-step guide to doing this in NextPVR, and trying it in WinTV hasn't worked either.
The few threads I've found in this Forum all provide only bits and pieces, and they seem to assume prior knowledge that I don't have. For example, this thread has a promising-sounding title, but it launches at once into a discussion of CLI commands.
This old thread references a blaster setup guide, but the gbpvr.com link given there no longer leads to it.
The "Import Channels" (fourth) image on the NPVR Wiki STB setup page doesn't match what I'm seeing. The image shows four fields to fill in, but I only have three fields. I don't have the middle one that, in the illustration, is filled in with info for XMLTV. And while I have an idea of what to enter in the path field, I have no clue what to do with the last field, the one that in the image reads "{channel_d2} {channel_d3}".
Apologies if this is coming off as a rant, but I felt I was really close to the finish line and now there's this. Any help will be appreciated. Please just bear in mind that I have zero background in this IR blaster stuff and extremely little in NextPVR, I come from a STB/WMC environment.
I've been happily using an old arm32v7 image, version 6.1.5.231022, for years on a Raspberry Pi 4. Works fine for my purposes.
Today I tried to update to the latest image, version 7.0.2.250621. The only thing I changed was to pull the new image from Docker Hub; I kept the rest of the configuration the same. To me it now "feels" like I've lost communication with my tuner, which is a USB-connected single tuner Hauppauge 950.
For this device, the docker run command specifies:
Code:
--device /dev/dvb:/dev/dvb
but perhaps this is not correct or sufficient for the new version of NextPVR? From dmesg I see the tuner device being found and being initialized with microcode on /dev/dvb, so that's good.
On the plus side, the web interface for the new version does come up, I can log into it, and I see my device list and channel map as before. EPG fetching also works. But there's no evidence that NextPVR is talking with the tuner (channel scan, manual program request yield either "Transcoder exited" or "There is no tuner available").
If I simply switch back to the old image (with docker tag) and reboot, everything works again. I'd sure like to have the benefits of the newest NextPVR version if possible - any suggestions? Thanks!
