I'm new to NextPVR (very long term tvheadend user looking for more stability...) so forgive what maybe a stupid question.
I have set everything up correctly using the direct .exe, all works well. I've since watched the youtube video and realised I should use the service. After installing the service Kodi and the ios app work correctly, but trying to access the web UI via IP:8866 fails. Stopping the service and going back to the .exe and it works fine.
Posted by: Peter - 2020-01-26, 02:26 AM - Forum: macOS
- Replies (10)
Hi,
After a 6 month break from playing with NPVR I recently reinstalled NextPVR on a new Mac mini with the latest OS Catalina 10.15.2, using dual HDHomeRun tuners. After a few hiccups installing the app (mainly code signing issues much discussed elsewhere in this sub forum) it is working pretty well. I got a free month subscription to iceTv for the TV guide and I installed ffmpeg and am able to watch live TV and record as well. This is great and thank you! So far so good.
There are a few small bugs which I will submit reports for in a few days.
However unfortunately I can’t get the AppleTV app to work at all. I downloaded it the morning and started it up but it crashed multiple times - searching for NPVR server… crash. The Mac terminal logs show:
[10] Unexpected error getting IP address: System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (00000005, 0xFFFDFFFF): nodename nor servname provided, or not known at System.Net.Dns.InternalGetHostByName(String hostName) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at NShared.LocatorService.DetermineIPAddress()
each time I restart the ATV app.
I have rebooted the ATV and the NextPVR app on the Mac mini but the problem persists. I have enclosed the logs.
Now that I have a functional NPVR setup on my development machine, I'm finally in a place I can help with documentation. I see there's some stuff on Github already. Is it best to just fork that and then put in pull requests, or is there some other process in place?
I made a lot of changes/updates on my NextPVR setup and I'm not getting something weird. All my recordings are great, as usual. However, I am also getting a <tvshow_name>-0.ts file on pretty much every (it might be every) recording that gets made that's 0 bytes long. I get a corresponding <tvshow_name>-0.xml file. None of the "<tvshow_name>-0" files show up in the log file.
I think this must have something to do with a permission, since I am recording to a network share, but I don't know. It's obviously not a big deal because I'm still getting everything recorded It's more of a curiosity for me at the moment. I attached this morning's log for reference.
AT SOME POINT THE DEFAULT IMAGE STARTING COMING WITH PYTHON3
I'm leaving all this here as a historical artifact mainly. At some point the default image started shipping with Python3. As of July 23, 2023 it's Python 3.9.2. That's a hair out of date, but not horribly so. I won't be updating the image referenced below any longer. It's not worth the time to me for a slightly newer version of Python3.
Two things to note. If you want to install any Python modules, you'll have to install pip3 by doing:
Code:
apt update
apt install python3-pip
No need for sudo, as the image seems to default to the root user. If you ever update the image, you need to reinstall pip3, but ONLY if you need to install modules again.
Which leads me to the other trick. If youmap the Python userspace to an external volume and then install modules in the userspace, you can avoid having to reinstall your python modules every time you update the image. To do that, you need to add a line to your Docker run or compose:
Code:
- '/volume1/configs/nextpvr/local:/root/.local'
Then install Python modules using:
Code:
pip install --user <item>
ORIGINAL POST
For anyone who wants to run NPVR5 from a Docker container and also would like to use Python scripts for things like Parallel or Post Processing (or Extra tuners), I've published a Docker container based on nextpvr/nextpvr_amd64table. There are two different ways you can run this Docker.
The stable tag includes NextPVR, Python 3.9.6, and the following modules:
requests
xmltodict
websocket-client
opencv-python
These are included so two Python scripts I wrote (trigger.kodiscan and iguana-blaster) will work properly in a NextPVR docker container.
The pub tag includes NextPVR and Python 3.9.6. It is setup so that you can map a directory to user level python module installs and install them outside the Docker container. This provides more flexibility if you want to install other modules but don't want to have to redo it every time the image is updated.
Both tags also includes NTP and a couple options to set the timezone for your container. This was added because on certain platforms Docker containers don't seem to be able to get the time/timezone from the host OS. And having accurate times seems important for a DVR. If your Docker container is getting the time correctly from the Host OS, you don't need to include those options.
There's complete information both options (including sample run commands) at:
NOTE ABOUT COMSKIP:
With the release of 6.x, the NextPVR image is based on Bullseye. I can't seem to get any of the current(ish) Comskips to build with this, and the version of Comskip included in the apt package manager for Bullseye is pretty old. So I DID NOT update the two Comskip tags. They will remain at the last 5.x version of NextPVR, but may not ever be updated again.
Using NextPVR V5 I have not been able to get SAT>IP to scan for channels correctly. I started off several months ago using Minisatip with a DVB-T tuner and TVheadend and TVMosaic and NextPVR V4 found all DVB-T channels but V5 only found channels on 1 or sometimes 2 MUX.
I just bought a Digibit R1 SAT>IP DVB-S2 tuner and enabled just tuner 1 for testing. TVheadend, TVMosaic and NextPVR V4 scan all the specified transponders and find around the expected number of channels. However NextPVR V5 seems to find channels on around 1 in 4 transponders. A very noticeable thing is that while V5 is scanning using Tuner 1 all 4 tuner lights on the Digibit R1 come on and occasionally one goes out although Tuner 1 is the only one enabled. Each later scan seems to find fewer MUX/Transponders.
Enclosed are logs of a scan starting 11:15 of 49 Free To Air Transponders at 28.2E by the Digibit R1 and a later scan by Minisatip with DVB-T tuner starting 13:38 of 9 local MUX (3 DVB-T2) but only finds channels on one MUX. I get similar results using two other computers.
All the Minisatip channels were watchable on other devices. The Digibit R1 satellite receiver is working correctly as when using Kodi with TVheadend and TVheadend client add-ons it becomes an easy to use Free To Air satellite receiver especially if you select your local regional setting.
I just started using the iOS app, and I'm running into a few problems.
1) TV Guide tab: the data loaded always seems to be incomplete. When I first select that tab, the table presented is fully populated. However, if I scroll a couple of hours in either direction, everything is blank. Specifics seem to depend somewhat on the time of day, but the main thing is that data is never complete. For example, it is now about 10:20pm. I have full data going back to about 6:30pm tonight, and up through midnight. But when I looked earlier this evening, data did not go all the way through midnight - it cut off some time before that.
The really strange thing is, if I pick any future day, it's the same thing. That is, if I now choose any upcoming day from the dropdown list, I get listings for 6:30pm through midnight - and nothing for the rest of any of the days.
2) The Search feature crashes the app. If I tap on the Search tab, I can enter a string in the Keyword box. Then once I hit "Go", the app crashes (I get bounced back to the home screen).
3) There's odd behavior on the startup screen...not really a problem, but worth mentioning. I have two entries in my list - one for when I'm at home on my LAN, and one for outside (using a No-IP address). But the app seems to create a third entry, which is a corruption of the local IP. Just using some fake numbers - if the entry for my server on the LAN is 1.2.3.4:8866, the app also adds 1.3.2.4:8866 (and this entry doesn't work). If I delete the bad entry, it will return the next time I start the app.
Overall though, the app is great. In particular, the feature I most wanted it for (playback of recordings) seems very solid.
I'm running NextPVR 5.0.1.200103 on a Synology DS418play using Docker. For iOS, I'm using an iPhone 7 and iPad Pro 10.5", both with iOS 13.3. All of the things I mentioned above behave the same way on both devices, and it doesn't seem to matter if I'm on my LAN or connecting remotely.
I'm continuing to plug along on testing of my NPVR5 setup running in Docker. Here's my latest snag. When I point KNEWC at my NPVR5 instance running on Docker on the same machine, I can't start the Client UI. I know the connection is OK because I can look at the guide in the KNEWC interface. Here's the Kodi debug log:
You can see at 10:25:49 it tries to open the URL to instantiate the UI client, but then a 404 error is returned. I tried with the admin username and password in the username/password fields for KNEWC and without. I also confirmed the PIN is correct, although I suspect either of those problems would generate a different error, not 404 not found.
I'm not able to find a version number in the web pages for NPVR5, but I just built this image from sub's Docker image earlier this week, so I can't be *that* far behind.
New NextPVR user here, version 5.0.1.200103 through the official nextpvr amd64 docker image.
I am using an enigma2 set-top cable box as a tuner source. The channels are shared in the local network via m3u8 playlists and imported into NextPVR. The STB just passes on the unprocessed transport stream.
When I start a recording, the CPU usage of my Xeon E3-1225 v6 boosts to 100 %, the source being ffmpeg treating the "buffer" file (not the actual recorded file).
How do I get rid of this? Can/should I set buffer time to 0? Or is it related to the recording in general?
I read here about substituting a .dll file, something I probably cannot do in the docker container.
table. There are two different ways you can run this Docker.