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.
Hey all, I just wanted to ask if it would at all be possible to expose the full mux for applications outside of NextPVR where currently we expose a url directly for a specific channel from the mux, having full access to the raw mux stream would be a dream. I'm still pretty new to the scene so apologies if my request is a load of bollocks, I experimented with TVHeadend which I believe exposes the full mux but it's Linux only I believe and it's pretty iffy. I'd be happy to support the development if this is something that's possible, thanks in advance.
Posted by: Soapm - 2026-01-13, 07:25 AM - Forum: Linux
- Replies (9)
For some reason I can't get Adam 12 and Dragnet to consistently record and I don't know why. Do you see any clues in my logs? I set them for any time any channel and I believe to keep like 12 but I never seem to record new ones and I just deleted old ones going back to November?
I was able to get wake from suspend working with the Hauppauge 2250 on Ubuntu 24.04 Linux.
The driver in use is saa7164.
The driver would lock up once the system went to suspend so resume would result in an unusable system.
I would have to completely power down the system to get it working again.
I thought I had it solved by unloading the driver, but the driver would fail when trying to reload upon resume.
Solution was to clear memory cache before suspend.
Solution:
/usr/lib/systemd/system-sleep/saa7164_driver_handler.sh
Need execute permissions on the script:
(-rwxr-xr-x 1 root root 584 Jan 7 23:23 saa7164_driver_handler.sh)
#!/bin/bash
DRIVER="saa7164" # Replace driver_name with your specific driver
case "${1}" in
pre)
# Actions to take BEFORE suspend
echo "Stopping nextpvr-server..."
systemctl stop nextpvr-server
echo "Unloading $DRIVER modules..."
modprobe -r $DRIVER
sync echo 3 > /proc/sys/vm/drop_caches
;;
post)
# Actions to take AFTER resume
echo "Loading $DRIVER modules..."
modprobe $DRIVER
echo "Starting nextpvr-server..."
systemctl start nextpvr-server
;;
esac
I also required the devices to be loaded before the nextpvr-server would be allow to start
If I try to playback a recording in the client it blinks and does nothing. If I try to watch live TTV it says waiting for awhile and then nothing/ I just installed version 7.0.3 after a computer crash. Before the crash it worked fine. The recordings playback fine in the WEB app.