Some time ago, I complained about this, saying that every time Microsoft did an update and automatically rebooted, that the recorder stopped working. It was suggested to disable "Scan devices at startup," and that appeared to fix the problem (everything else is set to default). However, this last time the problem showed up again. After restarting the service, it started working again. Any more suggestions as to what I should do to fix this issue? It hasn't happened often enough yet to see if the problem has come back permanently, or if it's intermittent. I attached a screenshot of the error and log files.
Hey Im new to the forums here so please forgive my formatting.
image: Nextpvr/nextpvr_amd64table
There appears to be no option in the settings menu to choose nvenc ? only "vaapi" and "cpu" is present and this causes issues with some of my streams.
i probed ffmpeg inside the container and this is the output ....
I also tried to delete the container adding "--gpus all" nvidia to runtime and -e variables NVIDIA_VISIBLE_DEVICES=all
NVIDIA_DRIVER_CAPABILITIES=compute,video,utility.
Im kind of at a loss and I Dont know what else to do .
I tried to install a a Windows 11 update today and noticed that NextPVR is running. Checking NextPVR "Status" produced the attached output. I checked both the web and the desktop interface to NextPVR and could not find anything currently recording. Moreover, it has been in this state all day (about 8 hours).
I've also attached log files for your reference.
Should I just go ahead and let Windows update itself (and effectively end the running job), or try to fix whatever the problem is first?
When I record the BBC oder BBC2 via IPTV, regulary parts of the record are double.
When playing the file, he jumps back 20 seconds and plays the last 20 seconds again. And this happens in the broken parts every 30 seconds or so. Some parts are even tripled. In the end the half an hour recording ist 2 hours long.
When I record 4 hours of snooker, the result is usually around 6,5 hours. Parts are ok, parts are broken.
Another problem:
Records from BBC4 have no soundtrack.
I just noted that my main Windows PC has a BIOS update and followed up to find out that my BIOS will need to be updated to run with Secure Boot after June 2026. I found this site pretty informative https://windowsforum.com/threads/secure-...in.397238/ so if you use Secure Boot you might to read it. The tl;dr version is trying running this in a powershell admin to see if it is True or False.
Code:
[System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023'
False
I confirmed I had a failing string
Code:
[System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Microsoft Corporation UEFI CA 2011'
True
I've now left Win7 (WMC) for my live/DVR TV delivery system of Spectrum cable. I instead now use Spectrum's modern internet-based TV delivery through their Spectrum TV app running on a Xumo streaming device, couple with Spectrum's CloudDVR service for DVR.
I still may continue to use Win7 (WMC) for live/DVR of OTA ATSC 1.0, but I'm at least now free to explore other options.
So I've now brought up a Win11 server machine for HDHR/NextPVR server software and recordings storage. And I'm once again exploring using either or both apps to deliver OTA ATSC 1.0 content to the four TVs around my home, as well as to my phone. I am already using Spectrum's internet-based TV delivery technology to do the same thing for Spectrum cable TV service (delivering to the four Xumo streaming devices I've now installed).
HDHR/NextPVR client apps are running properly on ATV4K and Windows11 machines. Haven't yet tried Roku Ultra for both but I will. I will also try the HDHR client app on my LG TVs (no NextPVR client app for LG). I've also successfully run the HDHR client app on my Samsung Galaxy S21 Ultra phone.
So far the only problem I'm having is running the NextPVR UIDroid client app on my Galaxy S21 Ultra phone. This is the same side-loaded APK I've had on the phone for a while, and it used to work at least for ATSC 1.0. Didn't work fully for ATSC 3.0, but it certainly did start successfully. And it did work for ATSC 1.0.
Well now it launches and appears to start, but never actually completes its startup. It is stuck with the green and white matrix background and white droid over it on the screen. Never moves beyond that. No way to communicate with it, and there's nothing else on the screen.
What have I overlooked or neglected? Version update I didn't see?
APK: NextPVR UI Client 2.1.14, Target version Android 13, minimal SDK 22, last update 3/17/2025
I'm making some organizational changes to my home PC situation.
I'm no longer able to run Windows Media Center (which requires Win7) to support my Spectrum cable TV service (through Ceton cablecard-enabled PCIe tuner card inside my Win7 PC) because Spectrum no longer supports cablecards and tuning adapters (to support their SDV many-to-one unlimited channel delivery method). So I've moved on to an alternative Spectrum cable arrangement, instead using their CloudDVR service and delivering live/DVR output to my four TVs through their Spectrum TV app running on four of their new Xumo streaming boxes. The Spectrum TV app also runs on Android phone, Roku, ATV4K and LG TVs, (all of which are also available to me) among numerous other platforms.
I can still use WMC on my Win7 PC but for OTA ATSC 1.0 only through either my Hauppauge Quad-HD OTA ATSC 1.0 PCIe tuner card, or through my SD Flex-4K (selecting only the ATSC 1.0 channels). However it's a bit of a nuisance out at the client TVs, having to select the WMC "extender" method to watch OTA through WMC and then to switch to the Spectrum Xumo when I want to watch Spectrum cable.
Nevertheless, with my Spectrum cable TV needs now addressed by Spectrum-provided technology, I'm free to explore alternatives to WMC (which requires Win7 on the server PC) since it is now only delivering ATSC 1.0. I have been using the internal Hauppauge Quad-HD OTA ATSC 1.0 tuner forever because it works perfectly with WMC and has 4 tuners and was available 10 years ago. But today, I have the SD Flex-4K as an alternative if I would consider moving to either HDHR or NextPVR software delivery of live/DVR OTA ATSC 1.0 content... via HDHR or NextPVR software client apps running on either (a) my four LG OLED TVs, or (b) Roku or ATV4K streaming devices which are also connected to each TV.
Furthermore, I can finally now move on from Win7 to a Win11 PC for the host to run HDHR or NextPVR server software and hold recordings storage. And I have done that, at least in prototype form as a pilot project. I've taken one of my Win7 WMC (backup) machines and am now booting to Win11 on it (as a second dual-bootable OS). And I've also installed both HDHR and NextPVR "server" on it, utilizing the network-based SD Flex-4K.
I've also stopped both HDR and NextPVR "server" which was running on my other Win7 WMC (primary) machine, which I still have running, continuing to run WMC for OTA (via the Hauppauge Quad-HD card inside it) and delivering to the WMC "extenders" still at the four TVs around the home. So I'm now using the Win11 machine instead of the Win7 machine to feed the HDHR and NextPVR client apps around the house.
And everything is working fine. No problems at all, now operating in my new Win11 server world.
However, although I have theoretically run NPVRSetup.exe on the Win11 machine order to upgrade from the 7.0.2 (which I was last running) to 7.0.3 (which is supposed to be the current version available for download), I cannot see to impact what gets installed. Still shows 7.0.2.
What am I doing wrong, or what else do I also need to do that I'm not doing?
I haven't tried mine yet but I just installed an interesting video capture device https://www.ebay.com/itm/376785020315 with 4 x HDMI hardware encoding ports at a great price. Probably came from a failed IPTV distributor so who know how much life it has.
What it really cool is how NextPVR finds it as a DVB-S device It identifies itself to Window (BDA) and Linux (/dev/dvb).
Expected behavior: Channels appear in NextPVR with the tvg-cho channel numbers
Observed behavior: Channel numbers in NextPVR start at one and increment sequentially instead of using the tvg-cho numbers. They do appear to be sorted by tvg-cho (or maybe just the order they appear in the m3u?)
I have attached logs, though I'm not certain if this is a bug or working as designed. I had assumed the channel numbers would show up because IIRC HDHR channels numbers were mapped correctly when I did that in the past.
table 
![[Image: x432Aw.jpg]](https://imagizer.imageshack.com/v2/1024x768q70/923/x432Aw.jpg)
