I recently installed the latest NextPVR on my Windows10 machine. I noticed I can not update the EPG if a program is being recorded. It fails, but works fine when nothing is being recorded.
I had the same problem in old V19 NextPVR, but was able to get around it with the initial install by scanning the 4th HDhomerun tuner first for channels and then copying the channels into tuners 1-3. This assigned the backend to 4th tuner for EPG. Apparently the backend isn't smart enough to pick a free tuner.
On the latest NextPVR scanning the 4th tuner first for channels does not assign the backend to the 4th tuner for EPG scanning. When you are recording on 1st tuner and try to update the EPG it fails because it isn't smart enough to look for a free tuner.
Martin
Most channels uses the Freesat EPG but unable to detect the few clear channels on SKY transponders so have to use DVB-T version. However recently NextPVR has occasionally not done a DVB-T update but now just does the Freesat Scan. Under "EPG Sources" the DVB EPG source is listed!
Enclosed is log file created after a EPG Update.
Hi,
In Kodi Omega, with the standard NextPVR Client 21.3.2 installed, if I schedule a recording from the guide using the Record option on the context menu or hitting record on the remote I get a single recording request. A timer is correctly setup and the recording entry appears as a one-time recording in the NextPVR scheduler tab.
If I then try to change the timer in Kodi to a series, by using the Edit Timer context menu option, a Kodi dialog opens allowing me to change the option to a series, and if I do so the existing timer (and Scheduled entry in NextPVR is deleted but the replacement recurring timer does not get created.
Here is a short youtube video recording of the steps I am taking:
There is no discernable error in the Kodi logs, and I have attached the NextPVR logs as is typically requested.
If I use the create timer function when there isn't already a recording in NextPVR, no error occurs and the correct recurring recording is created.
This seems to be an issue with the delete/recreate workflow.
I would like to know if there is a way that NEXTPVR would be able to record on my SSD drive which also runs COMSKIP in parallel processing to speed up things and then automatically move the recording to an external (slower) one ?
The previous version of NextPVR was fine with Jellyfin. I recently updated NextPVR (around 2 weeks ago) and today I suddenly noticed this in Jellyfin's logs:
Hello, I am switching my NPVR server from a decade + old PC (i5 processor, Windows 10) to a Raspberry Pi 3B+ (stripped down current Raspberry Pi OS - Bookworm, I think). I am continuing to use an HDHR dual tuner, and I am recording OTA programs, a mixture of HD and SD shows. I've only recorded a few shows on the RPi so far (shoulda read the instructions more closely about disk access by the nextpvr user, too way to long to figure out why access to the mounted NAS drive was denied) so I don't have a great comparison of how these recordings look compared to the ones off of the PC (I'm viewing the RPi recordings using Kodi on a new Mac Mini, on an old Dell monitor, compared to a large LG TV for the PC).
My question is, should I expect the quality of the recordings on the RPi to be equal to the recordings on the PC, especially when two shows are being recorded at the same time? The RPi currently is booting with the user interface (I've deleted just about everything extraneous from it, and once everything is running smoothly I'll switch it to booting to the command line interface to save resources).
When using the 'import using M3U' function for an IPTV provider, I immediately get an http 401 unauthorized error. When I try that same m3u url in the browser, if I set a generic User-Agent http header value of VLC, it works.
What User-Agent value is being sent by nextpvr when doing 'import using M3U' and can it be customized?
Also, when using the 'import using m3u' function, how many requests is nextpvr making at that time to the url? Is it just one or does it attempt to make multiple requests within a second for that function?
I'm running nextpvr Version: 7.0.3.250920 on ubuntu
Just noticed that on the client side on Roku the current time and guide times are off (+5 hours). However in KODI and webui they are the correct current time. I checked my Roku and Hisense tv and time settings are correct which is EST. I suspect it is getting its epg time from the NextPVR server and not client device? Server time is set to EST as well, plus when logging in to use webui, it displays correct times.
Running on Windows 11, latest version, other recordings have been fine.
Love the app - had an issue with a scheduled recording - see log below. Seemed the "name" contained a tab \t and it caused an issue.
Quote: "reason": "The filename, directory name, or volume label syntax is incorrect. : 'C:\\Users\\Public\\NPVR-recordings\\Premier League\tLIVE\\Premier League\tLIVE_20250929_01000330.ts'",
Would be great to either have the option to edit the name/filename in webUI of the recording or for these types of characters to be removed before attempting to record.
Extract from the log:
Code:
"recordings": [
{
"id": 859,
"name": "Premier League\tLIVE",
"desc": "On Super Sunday, Newcastle host Arsenal at St James' Park in the Premier League.",
"subtitle": "",
"group": "Premier League\tLIVE",
"startTime": 1759071600,
"duration": 9000,
"firstrun": true,
"epgEventId": 2026293,
"status": "failed",
"size": 0,
"quality": "QUALITY_DEFAULT",
"channel": "SKY SPORTS MAIN EVENTS \u2074\u1D4F",
"channelId": 35702,
"blue": false,
"green": false,
"yellow": false,
"red": false,
"prePadding": 0,
"postPadding": 0,
"reason": "The filename, directory name, or volume label syntax is incorrect. : 'C:\\Users\\Public\\NPVR-recordings\\Premier League\tLIVE\\Premier League\tLIVE_20250929_01000330.ts'",
"recurring": false,
"recurringParent": 0
},
I have 2 tuners and I was expecting to be able to view TV on 2 separate clients, for example, view channel 85 on Kodi and channel 76 on Jellyfin. My understanding was that NextPVR would switch to tuner 2 if tuner 1 was in use, but this does not seem to be the case. Is my assumption correct or is the use of dual tuners only applicable to viewing one channel with one tuner and recording with another tuner?
