I have two HDHRs - an HDHR3 and an HDHR4. They are in the basement and closer to the antennas than the TV sets.
In my experience, both of my HDHRs are inferior to the tuners in either TV, both of which are significantly more successful at bringing in watchable signals on more distant stations. Further, I have found the HDHR4 to have a lot of trouble with overload, and the HDHR3, generally, to be more capable. This has required a fair bit of fancy footwork to maximize reception, which could still be better.
So, here's my question. anyone out there have experience with either of these as well as a newer HDHR? I would "upgrade" to a newer one if it was, indeed, an upgrade.
I change it in the web page to 1080p or 720p and the next day I see it has switched back to Default.
What is this Default resolution/speed? What setting do I change to adjust the default in the Streaming profile to another resolution permanently in the config file?
Hi there, i have a problem from today, basically i have nextpvr server installed on a mini pc and connecting usually on kodi on my sony android tv with a vpn set on server not the tv but today if the vpn is on, the kodi addon doesn't connect. Thanks. Luca.
I don't use NPVR very often, and it has been working fine for some time. Just now when I tried to access the web server from another pc on my LAN it kept timing out. I tried stopping and restarting the recording service on the pc hosting NPVR, I tried rebooting all machines, but nothing helped.
I know the server is accessible from the other machines because it returns pings. I know the ip address is correct because I set the router to assign the addresses statically so they don't change.
There are two other web servers running on the NPVR machine, one for Agent DVR and one for SABNZBD and they are both accessible at that ip at their respective port numbers.
The server is accessible from the machine it is running on via web browser at both LOCALHOST:8866/index.html and at the assigned IPv4 address of the server.
It is not asking for passwords when attempting to access it from other machines, the connection is timing out.
NPVR version 7.0.1.241229
The server is running on Windows 10 Pro 22H2 build 19045.5371 experience pack 1000.19060.1000.0
Hi! I cannot seem to auto delete the TS. file. I have Recording Auto Transcode set to 1080p (.mp4). I also have Recording Thumbnails set to None but it's not deleting the TS. file.
We just moved into our new, very rural, forever home so we've finally cut the cord and gone full OTA. The transition has been easy, I already had a Flex Duo which pulled in OTA whenever the old cable provider decided to go out. Since we're situated directly between 2 major markets and high on a hill we get 40+ channels, including all the major networks!
This far out cable will never be an option so I now have 2 surplus HDHomeRun primes (HDHR3-CC) that need a new homes.
I'd like to get $45 + shipping for each . One will fit in a a small USPS flat rate box for $10.65 or if you want both they can ship in a medium USPS box for $19.15.
I'm also open to trades for a HDHomeRun Duo or a HDHomeRun FLEX 4K if anyone has one sitting around unused.
I am using a legacy HDHR3-US (HDHomeRun DUAL, 192.168.0.109). I have set the IP ENV and opened the udp ports as described here: https://forums.NextPVR.com/showthread.php?tid=59393. The host firewall is off.
I have run a channel scan with the SiliconDust HDHR setup software from a windows computer and can see my channels. In this setup software, I have set the BDA compatibility to NextPVR.
I have setup an xmltv file for the program guide.
I am accessing NextPVR through the web interface. I have scanned my HDHR3-US device and can see my channels in the NextPVR channel settings and in the guide, and can start and schedule recordings. The second tuner channels were copied from the first.
However, for some reason unknown to me, recordings will 'stop' earlier than scheduled. Although the NextPVR software will claim it is recording and will seem to stop at the desired stop time, the .ts file will be truncated with a shortened length (e.g. expected length 63 min with padding is 45 min). The next recording will seem to start (and stop) with the usual recording indicators in the recording 'tab' and highlighted red in the guide, but the .ts file will be empty.
I will need to restart the NextPVR docker container to get an actual recorded file generated again, but it will again stop at some point. This happens independently with each of the 2 tuners.
For example, from the attached log, a scheduled recording started at 15:31 around log line 16506.
By line 16695, the number of bytes received stopped changing at 3656983708:
2025-01-21 15:32:22.264 [DEBUG][51] Have received 3656921856 bytes from rtp source
The log continues to report this number of bytes received until the recording stops around 16:00. The actual recorded .ts file is only 1 min 23 seconds long (should have been ~29 min).
The next recording started at 4:00pm and reports having received 0 bytes:
2025-01-21 16:00:01.395 [DEBUG][57] Have received 0 bytes from rtp source
I canceled the recording at ~16:17:
2025-01-21 16:17:16.176 [DEBUG][57] Have received 0 bytes from rtp source
The .ts file was empty.
I had the second tuner recording as well, and it stopped recording received bytes at
2025-01-21 15:58:03.184 [DEBUG][55] Have received 2050597780 bytes from rtp source
The .ts file was short. The next scheduled recording (16:00) on the second tuner reports receiving no data until I stopped it at 16:22. The .ts file was empty.
I restarted the NextPVR docker container at ~17:03 and initiated 2 recordings at ~17:05 to show that they start as usual after a restart. I canceled them both about 9 min later. The .ts files are OK at this point, but recordings will surely fail again.
The HDHomeRun DUAL device behaves fine on another system that I am exploring migrating from. I have another device, a non-legacy HDHomeRun CONNECT, that works properly with NextPVR (not connected during the above reported testing results). The tuners are up to date with the current firmware.
I have attached the logs. Any guidance on what I may be doing incorrectly or incompletely would be appreciated. Thank you.
Issue: if you run NextPVR by opening a terminal window (even if automated with a launchagent as previously posted):
you still have nextpvr running in a terminal window, even if the window is hidden
if someone quits terminal, or if nextpvr crashes or is otherwise shut down, you will miss recordings until you detect and correct the problem.
These issues are resolved by using a launchagent or launchdaemon. The following are instructions on how to do it with a launchagent:
unzip and copy the attached launchagent (org.nextpvr.backend.plist) into ~/library/launchagents
set the owner to your username (the name of your home folder). This can be done with this terminal command: chown <username> ~/library/launchagents/org.nextpvr.backend.plist
set the file permissions to 644: chmod 644 ~/library/launchagents/org.nextpvr.backend.plist
this launchagent expects your NPVR folder to be in /applications (specifically, that the path to NextPVRServer.dll is /applications/npvr/NextPVRServer.dll). If you don't want it in /applications, or you want the folder named something other than NPVR, you can edit the launchagent WorkingDirectory and ProgramArguments accordingly, but I have not tested in another directory and there may be bumps due to macOS security issues that will cause the launchagent to fail.
When the above is done, NextPVR will launch automatically when you log into your account. You can launch it by logging out and back in to your account. The keepalive key will keep NextPVR running even if it crashes, etc., until you shut it down manually (as detailed below) or you log out of your account.
You can also manually launch and stop NextPVR with the following terminal commands:
A potentially significant limitation of using a launchagent instead of a launchdaemon is that a launchagent will require that a particular user be logged into the computer and stay logged in. Accordingly, booting up the computer is not enough to launch NextPVR and if, for whatever reason, the user is logged out or the computer restarts (power outage, for instance) NextPVR won't run until the user is logged in again. Also, if there is more than one user who uses the computer, NextPVR will only run when the user whose account has the launchagent is logged in. These limitations would be resolved by a launchdaemon, which has the same function as a launchagent, but runs system wide on boot up. Writing a launchdaemon that will work with NextPVR is more complicated (for me anyway) and I have not yet managed to get it to work. When I figure it out, I will update.
You can see the purpose of each of the keys in the launchagent by checking the manual (in terminal "man launchd.plist", or just google "man launchd.plist".
I'm preparing to replace the computer I use to serve content to Kodi, including videos, pictures, and recorded TV (using NextPVR). As part of that exercise, I'm reviewing my need for disc space, so I scanned my discs for recorded TV programs. I have recorded TV programs spread across four disc drives. I noticed that some of the programs that I have stored on these drives are not showing up as available in NextPVR's web or desktop interface. I'm wondering how I might get them to show up again in the NextPVR interface. Another note: The list of programs that show up on the web interface does not match exactly with those that show up on the desktop interface.
As an example, there is a folder on one of my drives containing recorded episodes of a program called "Outer Limits". I can play these programs using Windows Media Player, but these programs don't show up in either NextPVR's web or desktop interface.
I've attached a current log file and zip files that list the recorded TV content on each of the four drives. Thanks in advance for any help.
I would like the option to not display the OSD when I skip forward (long skip?)
When I'm skipping from play to play watching a football game recording, I don't really need or want to see the OSD (it hides the game clock/score for one).
I can always pause or show the info bar if I need to see the OSD.
With the latest release the OSD is rather large (I've removed the controls to make it smaller).
Thanks,
Art
