Hi Guys. so today I have installed NextPVR 5.0.8.200823 on my Raspberry pi 4 using the XBOX One Tv tuner. I have scanned for channels and have 141 listed but when I try to play a channel I just get the message on the bottom of the screen Starting Device please Wait.. In the Devices Tab it says DVB-T unavailable. Can anyone help.?
Is there a way of updating the EPG more often?
In Australia, the free to air channels publish a weeks worth of TV Guide data on the over the air guide. When first published it is fairly inaccurate, it can be up to 20 minutes out, but it is updated close to the actual air time to be extremely accurate.
I'd love to be able to update the EPG on a spare tuner shortly before a recording is due.
Alternatively, is it possible to import an EPG from another system like TVHeadend ?
*Running in a docker container with 2 x dual HDHomeRun tuners
I'm installing the latest release of NextPVR on a new build of a windows 10 64 bit machine. When it comes time to set up the EPG, I try to connect to my (active) Schedules Direct account and I get "Failed to login to Schedules Direct. Confirm you've entered your correct username and password, then try again."
I can log into my SD account just fine on their site with these same credentials. Why wont NextPVR connect properly? I've tried editing the channel parameters to use SD, but it hangs up after putting in my zip code and just says "...loading" in the next field forever.
Hello, some months ago I posted an issue regarding IR Blasting using Hauppauge Colossus card with my Set Top Box. (MySkyHDi)
Basically, have been using NextPVR v4 without issue, and IR Blasting working fine.
However, when using NextPVR 5, I get no IR Blasting inside the Web App, or the Desktop NPVR app, or indeed any client connected to the server.
I thought I would wait and see if it was an issue with the earlier V5 build I was using at the time, but the current build has the same issues for me.
With V4, I am using the built in IR Blaster supplied with the Hauppauge Colossus card.
There is an exe called 'Haupblast.exe' in the C:\Program Files (x86)\NPVR folder.
When I installed NextPVR 5, I copied the above exe into the same folder, along with blaster script which I can optionally use to add delay, tho it works just using the HaupBlast exe.
I created an environmental path variable, which points to the c:\Program Files (x86)\NPVR folder.
If I open a command prompt and type 'HaupBlast.exe 1' then it blasts IR and changes to channel 1 on my Set Top Box.
But if I try changing channels in Next PVR5, it does not blast any IR.
The channel change command in settings for NextPVR5 is set as 'HaupBlast.exe' in the first field of the channel setting in devices, and '{channel}' in the second field.
Also tried the full path of C:\Program Files (x86)\NPVR\HaupBlast.exe for first field, and '{channel) for second field.
It plays the current channel in the web app or desktop app, but does not IR blast.
If I leave the video playing, and open a command prompt and type 'HaupBlast.exe 1' it IR blasts to channel 1, and the channel does change in NextPVR, so I assume the environmental path is
working.
I tried changing to the same STB channel in NextPVR several times, and have attached logs. The Channel Name is 'Sky TV1'
I've been running NextPVR 5 on Windows 10 Pro for several months, after I tired of re-installing Windows Media Center with every update. Although NextPVr has been working well, I recently discovered that it has been filling my drive with .ts files that seem to have been created while watching live TV. Although I've set my Live TV buffer at 20 minutes, these are all 6:39 or less in length. I'd expect these to be deleted when exiting the program, if not sooner. When I found several months worth of these files, I upgraded to version 5.0.8 last week, but the problem continues. Google found some mentions of similar problems, but they were several years old and mention changing a setting from Timeshifting to EPG, which I cannot find in version 5 settings, client or server.
Anyone have suggestions I can use to correct this problem, short of manually deleting the files?
I had NextPVR up and running with rare failed recordings on Linux Mint. However, somehow my Mint user and administrator passwords were corrupted and I was locked out. I had backed up important files including NextPVR files so I reinstalled Mint then copied nextpvr files to /var/opt/nextpvr. Lastly, I reinstalled nextpvr. This setup works but daily or every other day I have failed recordings. Some shows record properly everyday just not all of them.
What is the best way to preserve my recordings if I ever need to reinstall Linux in the future? Are nvpr.db3 and recording-backup.xml enough? I reinstalled everything in the nextpvr directory/sub-directories which may be good or bad I don't know.
What do I need to do to prevent more failed recordings? Logs attached.
On my Docker setup at some point the maintenance to clear recordings that don't have a file associated with them stopped running (or at least it stopped cleaning up recordings). If I reboot the Docker container, the maintenance works at startup, but apparently never again after that. I want to take a look at the logs, but it would help narrow things down if I knew when it was suppose to run.
With the IPTV tuner and kodi as the client, some channels show two embedded CC options. The first one always doesn't work, and the second one always works.
I have been having some troubles recording shows using NextPVR. I use Kodi as a frontend with the NextPVR client add-on if that matters.
When I record a show, usually sports programs, I set them to record (usually around 3 hours for most sports games) and then usually add a post-padding of around 60 minutes in case it goes into overtime. The recording seems to go fine, the NextPVR Tray application shows it is recording for the full time I have it set to, but when I go to watch the recording it is very short and inconsistent. Some recordings that should be 3-4 hours play fine for the first 1:30, some only play for 10-15 minutes, before stopping and closing the recording. When I check the .ts file for the recording, it usually shows the file is around the size you would expect (~9gb for 3 hour recording, from my experience I've been getting 2-3gb per hour recording or so), but the "length" of video shows the 1:30:00 minutes or the 15:00 minutes.
However, some days the recordings work flawlessly, and I have 3-4 hours of recording that plays back with no issues. I have had this problem the last few weeks, but can't seem to figure out what happens to some of the recordings and why its so inconsistent.
Last night, I set up a test. I simply recorded a 1 hour show (from 01:00-02:00), and asked it to post pad 2 hours (should end at 04:00). This recording shows to be 7.31gb, but the length says 00:05:50. What is even stranger is if I play this recording, it works well for the first 10 or so minutes (using skip ahead buttons or fast forward buttons just to skim through) before it closes.
If someone could provide some insight onto what is happening as I don't really understand the log files. I don't have a lot of experience with IPTV either but I'm hoping to find some kind of solution to this inconsistency.
I have included a screenshot of the file from my test recording as well as the logs from Kodi and NextPVR.
