I was doing some testing and i noticed that when I have 3 TV's tuned to the same channel lets say a sports broadcast, NextPVR generates 3 seperate files in the temporary storage location for playback. I thought that it detected that if i channel was already tuned, it would just play the same file stream (i hope this correct terminology) to save on system/disk resources. Is this possible?
I maybe remembering this from back in when serverwmc worked with windows 7, but I could be mistaken.
I have been using zap2it for years. Now that it has changed, I was going to use Schedules Direct as I have a sub. I have been unable to add the local channels lineup to NextPVR.
When I go to add lineup and enter zip nothing happens. I had everything setup and working for so long that I am rusty working on this and might be missing something obvious.
I’m a bit of a newbie, so I apologize if this has already been answered elsewhere.
Some of my playback files freeze, and the audio skips back a few seconds. I’ve tried playing the files through different players, and they all behave strangely, which led me to believe that the issue might be with the encoding itself. I noticed that FFmpeg was from 2023, so I updated it to the latest version.
I also wanted to tweak the TranscodeArgs since my hardware is fairly powerful (Core i9, RTX 4090, 128GB RAM), but I don’t think the settings are taking effect.
When I check the log (nrecord.log), the only parameters I see are as follows (i replaced the name of the show):
C:\Program Files\NextPVR\Other\ffmpeg.exe -re -y -i "M:\PLEX\_TV_\SomeTVShow_2025-04-04_22350030.ts" -vf fps=1/10,scale=220:124 -f mjpeg -flush_packets 1 "M:\PLEX\_TV_\SomeTVShow_2025-04-04_22350030.thumbnail"
here are the changes directly from the config.xml that I made -
<TranscodeHLS>
-y -v error -hwaccel cuda -hwaccel_output_format cuda -i [SOURCE] -f mpegts
-c:v h264_nvenc -preset p5 -rc vbr -cq 19 -b:v [BITRATE] -maxrate [BITRATE] -bufsize 2M
-c:a aac -b:a 128k -ar 48000 -ac 2 -s [RESOLUTION] -aspect [ASPECT] -g 60 -sc_threshold 0 [TARGET]
</TranscodeHLS>
Well its time for my big upgrade V4 to V7. New hardware after 8 Years.
I have been setting up the new box over the last few weeks. So I have a few questions, on some of the things I am stuck on.
First trying to run NextTool I get -
NextPvr - Version: 7.0.1.241229
NextTool -from wiki 2.5.0
and this error
C:\Users\Public\NPVR-data>dotnet NextTool.dll
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\Users\Public\NPVR-data\'.
Failed to run as a self-contained app.
- The application was run as a self-contained app because 'C:\Users\Public\NPVR-data\NextTool.runtimeconfig.json' was not found.
- If this should be a framework-dependent app, add the 'C:\Users\Public\NPVR-data\NextTool.runtimeconfig.json' file and specify the appropriate framework.
I'm building a new server for NextPVR recording UK Freeview (terrestrial). So far the Hauppauge WinTV quadHD PCIe internal card looks like a good choice though there are various external/USB boxes available. To be honest I'd prefer an internal card rather than a bunch of USB devices hanging off the back. Any alternatives to the Hauppauge carfd out there?
I'm using NextPVR with the Kodi client. It works great inside my house on my home network, but I'd like to be able to use it from remote locations, through the internet.
So I set up the Port Forwarding through my router to the computer that is serving the NPVR, and I'm pretty sure I've got that right, because I got a Port Forwarding tester, and it finds the port through the internet (and if I turn off the Port Forwarding, it fails). Yet when I point my Kodi NextPVR client to the external IP address and port, I get no response, like there is nothing there. Pointing to the server directly at its internal address, it works fine.
Am I missing something else here that needs to be set up? Or how can I diagnose this? fall guys
I am starting to be a big fan of your software and appreciate your support.
I am having some issues with live IPTV playback. Playback stops on most channels within a few minutes and requires to start playing stream over again. Are there any settings for adjusting re-buffer or timeout as it seems like there may be an issue when the stream is temporarily interrupted? I have tried adjusting timeshift properties to test if length is a factor but it does not seem to make a difference (tested different times ranging from 1 minute, default 20 minutes, 120 minutes, 360 minutes..)
Recording channels seems to be a bit more stable but there have still been issues noticed. Not sure if there are more settings for timeout or recovery from an interrupted steam during recording vs live streaming but it seems that way from my testing. I have tried setting <M3U8DownloadTimeout>30000</M3U8DownloadTimeout> which seems like too much for timeout of the channel loading but not sure if this also applies for re-buffer.
NextPVR Version: 7.0.1.241229
M3U playlist import, not XC. Ubuntu server 24.04.2 LTS Kodi client w/ NextPVR addon using Timeshift
Full set of log files if anyone can take a look and let me know what you think. I do not have this issue playing channels or VOD titles from whatever VPN server choice I use and an IPTV client so I do not believe the issue is with my VPN provider or IPTV provider. logs-20250401-1536 .zip
Please let me know if you need other information provided.
I know that V4 is obsolete but it still has value for me and I use it every day in addition to V6.
I'm getting errors while updating the EPG and would like to know if I can do something to prevent them from recurring. I manually updated the EPG this afternoon and the NPVR.log.1 at record 2108 shows the following:
{
"stationID": "96299",
"serverID": "20141201.web",
"code": 7020,
"response": "SCHEDULE_RANGE_EXCEEDED",
"minDate": "no_db_mindate",
"maxDate": "no_db_maxdate",
"requestedDate": "2025-04-01",
"message": "Date requested (2025-04-01) not within no_db_mindate -> no_db_maxdate for stationID 96299."
}
2025-04-01 15:12:39.691 [ERROR][188] (798 - Uplift HD): Date requested (2025-04-01) not within no_db_mindate -> no_db_maxdate for stationID 96299.
2025-04-01 15:12:39.691 [DEBUG][188] 798 Uplift HD
{
"stationID": "96299",
"serverID": "20141201.web",
"code": 7020,
"response": "SCHEDULE_RANGE_EXCEEDED",
"minDate": "no_db_mindate",
"maxDate": "no_db_maxdate",
"requestedDate": "2025-04-02",
"message": "Date requested (2025-04-02) not within no_db_mindate -> no_db_maxdate for stationID 96299."
}
2025-04-01 15:12:39.691 [ERROR][188] (798 - Uplift HD): Date requested (2025-04-02) not within no_db_mindate -> no_db_maxdate for stationID 96299.
2025-04-01 15:12:39.691 [DEBUG][188] 798 Uplift HD
Can you offer some tips I can use to prevent these errors?