I think that this is a known "feature"/issue. I think that I recall somewhere sub mentioned looking into trying to better distinguish the different types of HDHR devices to more intelligently copy configurations, but I'm not sure if he's done anything about that yet. I'm also wondering if there is any sort of work-around at the moment.
On my test v5 system, I've got three HDHRs (1 Quatro using ATSC for OTA, but using the NextPVR HDHR device and 2 Primes using CableCards).
For my initial testing, I had all 4 of the Quatro's tuners configured and 1 of the tuners on one of the Primes. I wanted to add the other 5 Prime tuners. I started by configuring tuners 1 then 0 on the Prime which was already being used. And I selected the option to copy the configuration from the similar device already configured. Seemed to work great for those 2 tuners. Then when I went to tuner 2 on the first Prime, it copied the configuration from the Quatro rather than the other Prime.
I know this is still beta, but I've seen a few issues with v5 that I would like to help correct, but not sure if you are needing/asking for help/contributors or not. (I don't see a link to a GIT repo anywhere...) If so, I would love to help. If not, is there anything I can do to make your lives easier?
These are the minor issues that I've seen (I imagine you are aware of them, but here they are anyway):
Recording on "All Channels" doesn't work. The recording schedule only shows up for a single channel even if the "All Channels" option is selected. All the normal symptoms are there to indicate something that is still being worked on (e.g. the "All Channels" value isn't selected when re-opening the schedule, actually pending recordings only are for a single channel, etc.)
In the Schedules screen, when using the "Default" value for the padding values, the drop-downs just show up as blank.
If you accidentally try to create a schedule for a show that already exists, a new schedule is created instead of editing the existing one. Perhaps this is intended behavior, but it would be nice to recognize an existing schedule for the recording and just change the existing schedule.
Anyway, I'd love to help, if you need/want it.
By the way, I'm on the docker image on v5.0.0.191006 with a HDHomeRun tuner.
When I click on the Record Series button after selecting a show in the Guide in the web app, it is now generating a Manual Recordings for Daily, Any Channel with the Advance Rules "title like 'show name'" rather than a normal recurring recording for that show on that channel. (Which I'm pretty sure is what it was doing back in the beginning.) Is that change intended behavior?
I wanted to do my first steps with NPVR in order to compare it performance wise with TVHeadend.
To do so, I set up a Docker instance on my Synology NAS. The container is running well and is using the same net as the host.
Unfortunately, I do not have access to my Kathrein EXIP 414E (Sat>IP) device.
Due to the settings, it should be accessible via the host net - but it isn't.
So, what can I do - or how can I add what kind of information?
I tried to include the log files as attachment - but this is seemingly not allowed.
Thank you for your feedback and support,
best regards,
I downloaded the latest NPVR.zip file this morning since I saw that there was a new one.
Since then it always fails to record with the following error:
Have received 0 bytes from rtp source
There is an error on startup, but I don't know what might have changed to cause it.
Also, even after downloading and unzipping the latest zip, the UI still shows: Version: 5.0.0.190916(5.0.0.191006 is available for download)
Attached logs. I don't see anywhere it connecting to the actual IP of my tuners, but I don't have the old logs to compare to when it was working. May have to revert to see what changed.
I was out of town when sub first did the release with the installservice.bat to create the Windows service, so didn't try it right away. Yesterday, I upgraded to the latest 20191005 version, and tried to use the installservice.bat. It seemed to create the service OK, but when it tried to start it, I got the error
Code:
The NextPVR Service service is starting........
The NextPVR Service service could not be started.
The service did not report an error.
I did not find any entries in the Windows logs. And no NRecord.log got created. When I manually killed the process for the "starting" service, I could manually run the NextPVRserver.exe like I've been doing all along just fine.
Today, I shut down the server, removed the service which had been created, installed the 20191006 version, and again ran the installservice.bat (in an Administrator command prompt window). I got the same results. The service gets created, but apparently "hangs" during startup. I'm not sure what else to do to try troubleshooting this.
Trying to update to the latest version. Followed the instructions but I'm getting this error. All the files seem to be there. Thanks for the help!
Code:
sudo dpkg -i nextpvr-helper.deb
(Reading database ... 175135 files and directories currently installed.)
Preparing to unpack nextpvr-helper.deb ...
prerm called with args= upgrade 1.0
Linux
linux-arm
Archive: /tmp/NPVR.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of /tmp/NPVR.zip or
/tmp/NPVR.zip.zip, and cannot find /tmp/NPVR.zip.ZIP, period.
useradd: user 'nextpvr' already exists
Unpacking nextpvr-helper (1.0) over (1.0) ...
postrm called with args= upgrade 1.0
Setting up nextpvr-helper (1.0) ...
Regardless of the client I use, be it kodi of the NextPVR client itself the following happens - I switch to an IPTV channel, it starts playing then loops back to the start of when it started playing, this happens randomly with the loop happening at anything from 10sec to over a couple of minutes. I have tested the same M3U file in both VLC player and Kodi and this does not happen at all. At this point I can only think that its something to do with NextPVR. I have attached the logs and the system it is running on is as follows:
Intel Core i3 4130
6GB RAM
240GB SSD System Drive (C
1TB SSHD Data Drive For Recordings (D
Intel HD 4400 On-Board Graphics
Intel Gigabit NIC
Clean Install Of Windows 10 Pro x64 With All Updates , Latest Drivers & LAV Filters, NextPVR v4.2.4
