Pre-requesites
You need to have the ASP.NET 8 runtime installed. See "ASP.NET Core Runtime" section of https://dotnet.microsoft.com/en-us/download/dotnet/8.0
To watch video in the web app on a mac, you'll also need to have ffmpeg installed on the machine.
To install on macOS
copy binaries to directory an NPVR directory in your home directory.
cd NPVR
dotnet ./NextPVRServer.dll
After installing, NextPVR can be accessed using a web browser at http://127.0.0.1:8866/index.html. The default login is admin/password.
A note about browser choice
If you're using Safari, you'll need to enable auto playback of video, otherwise Safari doesn't allow video to start. Safari is doing this because it assumes the video is an advert or other annoying content the user doesn't want auto playing.
Posted by: sub - 2019-06-15, 05:44 AM - Forum: Docker arm32v7
- No Replies
Installing using Docker
A Docker image is available for users with 32bit ARM devices. The most common device of this type is the Raspberry Pi 3, often running either Raspbian or LibreELEC. Running in this container NextPVR supports IPTV, HDHomeRun, digital tuners (DVB-T, DVB-C, DVB-S, ATSC and QAM), or SAT>IP (DVB-S, DVB-T, DVB-C)
Install the container from Dockerhub using:
Code:
sudo docker image pull nextpvr/nextpvr_arm32v7
Running the application with Docker
For the docker application to be able to stop channel lists and settings, that survive reboots, it needs to store it's use data in a location outside the docker container. It stores this information in the /config directory in the container, which you can map to a location outside of the container. To run the application interactively, so you can see the server output, with the configuration sent to the 'config' directory off your home ("~/config"), run the following command:
--volume /home/pi/config:/config is telling it where to save your configuration --volume /home/pi/videos:/recordings is telling it where to save your recordings --volume /home/pi/videos:/buffer is telling it where to save your live tv buffer files --publish 8866:8866 is telling docker to map port 8866 (on the host machine) to port 8866 inside the the docker container.
If you're using an older legacy HDHomeRun, you'll also need these (with 192.168.1.51 replaced with your host's IP address):
Posted by: sub - 2019-06-15, 05:39 AM - Forum: Docker amd64
- No Replies
Installing using Docker
This method is likely to be used for installation on NAS devices, or distros like LibreELEC. Running in a docker container NextPVR supports IPTV, HDHomeRun and digital tuners (DVB-T, DVB-C, DVB-S, ATSC and QAM).
On 64bit Intel machines, install the container image from Dockerhub using:
Updating to a new release
If you already running NextPVR, and a new release is available, and you'd like to update, you'd typically run the same command again:
Running the application with Docker
For the docker application to be able to stop channel lists and settings, that survive reboots, it needs to store it's use data in a location outside the docker container. It stores this information in the /config directory in the container, which you can map to a location outside of the container. To run the application interactively, so you can see the server output, with the configuration sent to the 'config' directory off your home ("~/config"), run the following command:
--restart unless-stopped is telling docker to restart it if it crashes --volume /home/pi/config:/config is telling it where to save your configuration --volume /home/pi/videos:/recordings is telling it where to save your recordings --volume /home/pi/videos:/buffer is telling it where to save your live tv buffer files --publish 8866:8866 is telling docker to map port 8866 (on the host machine) to port 8866 inside the the docker container. --publish 16891:16891/udp can help with auto discovery from some client applications.
If you're using an older legacy HDHomeRun, you'll also need these (with 192.168.1.51 replaced with your host's IP address):
I have uploaded a new version compatible with v4 and v5 to the repo.
NOTE you will not get this automatically because I changed the name from knew45v to knewc (pronounced "nuke") most testers were calling it the "new client" anyway.
There is another cosmetic name change as sub has changed the protocol name from "web client" to "UI client" for version 5.
Other changes
2.7.0
Kodi Python UI
- most knewc python functions work with new v5 api
UI Client
- prev key broken (v4 and v5)
- need to send certain key to get Nextpvr UI back after playback when OSD is disabled (v5)
Give it a half a minute or so to start, then you should be able to open http://127.0.0.1:8866 in your browser to setup NextPVR. The default login is admin/password.
NextPVR v5 is a large redevelopment of the application, with the goal making it possible to run the backend (recording service / web server) on platforms other than just Windows. Where possible I've reused stuff, so there is a lot of familiar aspects to NextPVR v5, but there is also a lot of new stuff and things that needed to be done different ways...so there is definitely some learning curve for getting started with the new application. This thread aims to help get the user through this.
Unlike previous versions, since the traditional nextpvr.exe frontend application isn't available on non-Windows platforms, the setup and configuration is done using the web application. After installing, open your browser to http://localhost:8866/index.html, enter default "admin"/"password" login credentials, then head to the Settings->Devices page to begin setup. From there you should hopefully see your devices listed. Click a device...
Is NextPVR v5 ready for everyone to install?
Yes
How will I know when new builds are available?
When I post a new build, I'll post release notes in this thread. You can subscribe to this thread to get email notification of new posts.
Is there any documentation available?
Yes! The documentation is still a work in progress, but you can find the wiki here: https://github.com/sub3/NextPVR/wiki
Posted by: sub - 2019-06-14, 09:54 PM - Forum: Windows
- No Replies
Installing on Windows
On Windows NextPVR supports IPTV, HDHomeRun, digital tuners (DVB-T, DVB-C, DVB-S, ATSC and QAM), SAT>IP tuner (DVB-S, DVB-C, DVB-T) and HDPVR style devices (HDPVR, HDPVR2, Colossus, Colossus2, Rocket)
To install NextPVR on Windows, simply run https://nextpvr.com/NPVRSetup.exe. Any time you need to update to a new release, you can just run this again.
This will start a browser pointed at http://localhost:8866. The default login is admin/password.
Windows Client
The windows client, nextpvr.exe, is included in the 'client' subdirectory. At this stage it can only connect to NextPVR running on the same Windows machine.
A tray app is also available, which can give you a visual indication of when the application is recording or idle. This can run using NPVRTray.exe.
Hi, a great inclusion, particularly for UK would be for a lookup of tv shows for air dates as the guide data in UK does not include air dates for programs..
I would find that very useful and I presume this could be done on look ups when getting thumbnails from thetvdb.com etc.
Thanks....
Hi can anyone advise what to do regarding the channels list not showing on nextpvr?
On the right click menu when selecting channels, nothing pops up and yet there used to be a list of channels to easily select a channel.
I have to use the guide to change channels now which can take more time.
Thanks..
1. In Advanced settings --> Live TV Stream; What is are the 3 settings intended to do -- Real Time, Time Shift, & Extended Time Shift?
2. What do the "Live Tv and Recording Chunk sizes" affect?
Reason I am asking is that I noticed that when Extended TimeShift was enabled, I was getting a lot of buffering while watching live TV, but no such buffering with Real Time settig or when using NPVR as client watching same channel. Also, I have had no such issues with K17.
I am trying to understand what is going on with K18 & n4.2.4.
