Thanks for all your hard work creating this PVR. I can’t imagine the amount of work that has gone in to making this.
I am running a Synology DS918+ NAS with Docker which I installed from the Synology Packages app.
I have downloaded the latest image of NextPVR through the Docker app, by searching through the Registry.
I have launched a container using this image and set my Network settings to ‘Use the same network as Docker Host’.
I run the container and navigate to the web interface.
I log in to the web interface and click the Settings icon. I click Devices then Rescan for Devices, but only the IPTV device is shown.
I have tried adding the ‘SATIP_DEVICES’ option to the Environment tab in Docker. I used TV Headend to find what I think is the url to discover my device, which I believe is: http://192.168.0.31:8000/description.xml
Unfortunately it still isn’t able to find my SAT>IP Server.
Not sure if you can offer any help or advise please. I have attached a download of my logs.
I followed the instructions for using Curl to install the beta. When I check the status of nextpvr I get the following:
Code:
Oct 18 15:32:45 quad systemd[1]: Starting NextPVRServer...
Oct 18 15:32:45 quad server.sh[21553]: Starting server..Error:
Oct 18 15:32:45 quad server.sh[21553]: An assembly specified in the application dependencies manifest (NextPVRServer.deps.json) was not found
Oct 18 15:32:45 quad server.sh[21553]: package: 'Microsoft.ApplicationInsights.AspNetCore', version: '2.1.1'
Oct 18 15:32:45 quad server.sh[21553]: path: 'lib/netstandard1.6/Microsoft.ApplicationInsights.AspNetCore.dll'
Oct 18 15:32:45 quad server.sh[21553]: This assembly was expected to be in the local runtime store as the application was published using the
Oct 18 15:32:45 quad server.sh[21553]: aspnetcore-store-2.0.0-linux-x64.xml;aspnetcore-store-2.0.0-osx-x64.xml;aspnetcore-store-2.0.0-win7-
Oct 18 15:32:47 quad server.sh[21553]: Done. PID=
Oct 18 15:32:47 quad systemd[1]: Started NextPVRServer.
Does the deb package include all necessary installation files?
Hi I am looking for some volunteers to help inaugurate a wiki for V5. I think it will be a great time saver for new users and those of us on the forum that want to help new and old users alike. I'd rather post a link then retype something and I am sure some users would like to RTFM which we don't have.
The new proposed wiki will use the markdown language a really simple way of formatting text I find easier then forum post formatting. Here is an intro https://guides.github.com/features/mastering-markdown/ hyperlinks.
I suggest that users use a free text editor like VS Code with a markdown plugin on any platform, or Notepad++ and the Markdown Viewer plugin.
It's going to pretty free form for a while as the section and sub sections get worked on but I think it will settle down into a usable style soon enough.
We can worry about how to submit the .md (that is the typical markdown extension) later.
****THIS IS NOW SOMEWHAT OBSOLETE AS SUB HAS PROVIDED A WINDOWS INSTALLER.
I WILL DO SOME UPDATING AT SOME POINT IN THE FUTURE****
This is a guide to getting NPVR V5.0.0.191018 running for testing based on my experience.
It will coexist with NPVR V4 except you cannot use the same tuner with both at
the same time. At some point, this guide will become obsolete once V5 is in
"production". The point in posting this is to perhaps help others try out V5. It is
not meant as a definitive guide.
This guide assumes:
- you do not have V5 installed
- you are running Windows 10 1903. Other versions of Windows 10 should be more or less the same.
- you are using Schedules Direct for guide data
- you are using "HDPVR" type device for data (Colossus, Colossus 2, HDPVR, etc.)
- you have NPVR V4 installed. If you don't, you'll need to get HaupBlast.exe installed
from someplace in order to change channels
- NPVR Version is 5.0.0.191018
2. Unzip the files to a folder. In my case, E:\Downloads\NextPVR_V5\NPVR. This
will be called "NPVR Folder" from here on.
3. Navigate to the above folder and double click on NextPVRServer.exe. Don't
worry about errors related to duplicate ports.
4. Navigate to folder C:\USERS\PUBLIC\NPVR-data (created by previous step).
5. Open config.xml with Notepad. Use Edit>Find to locate <port>
6. Change port number to 8867 (or something other than 8866).
7. Save the changed file as config.xml to the same folder.
8. Navigate to NPVR Folder.
9. RIGHT click on installservice.bat and click on "Run as Administrator". Service should start. Close the web app when it opens.
10. Navigate to NPVR Folder\Client
11. Double click on nextpvr.exe. Client should launch.
12. Right click someplace in client window and select "settings"
13. Click on "Devices & Channels"
14. Default username/pass is "admin" and "password"
15. Click on "Guide" to the left.
16. Enter Schedules Direct Login Info
17. Click "Add SD Channel Lineup"
18. Enter zip, region and click Search
19. Select correct lineup
20. Click "Add Lineup"
21. Click on "Devices" to the left
22. You will see your devices. Click on "HDPVR".
23. You will get "This device currently has no...". Click on "Import Channels"
24. In the "Import Channels" box, select your video/audio setup (HDMI/SPDIF for me).
25. Blaster executable path is "C:\Program Files (x86)\NPVR\HaupBlast.exe", assuming V4 is installed.
26. The argument is "{channel}". Note it is "greyed out". YOU MUST RETYPE IT as "{channel}"
for it to work.
27. Leave the top right box as "...Add Schedules Direct Lineup..."
28. Click "Import"
29. This will bring up the "Import Channels" screen. Click the top box to check/uncheck all.
Click individual boxes to check/uncheck that channel.
30. When done, click on "Save".
31. Update the EPG when asked.
32. Close browser
33. Click Cancel in Client Settings
34. Click Exit in the Client.
To test:
1. Go to NPVR Folder and double click on NPVRTray.exe to get the tray
icon in your system tray.
2. The icon will not be visible without using the "up arrow" at left of
system tray. You can change this by right clicking in the taskbar and
selecting taskbar settings.
4. Right click the taskbar icon (green) and select "Desktop App" to run
the desktop app ala V4. IF THE ICON IS NOT GREEN, THE SERVICE
IS LIKELY NOT RUNNING.
5. Right click the taskbar icon and select "Web App" to run the web app in
your browser. This will require username and pass.
Notes:
1. As noted above, you must type in {channel} for HaupBlast even though it
appears to be already there.
2. If you have a custom scale factor set, you may have issues with the appearance
of the desktop client app. If you have these issues, go to
Windows 10 Settings>System>Display. Under "Scale and Layout" you will see a
red notice "A custom scale factor is set". I was not able to work
around this. You can take the option that says "Turn off custom scaling
and sign out". After logging back in, you will have a different scale factor
set and the red notice will be gone. I changed the factor to 125 which works
fine and does not produce the red message.
3. There appears to be some odd behavior with Firefox and live TV that will
prevent videos from playing. You will need to keep trying till you get a
video that either freezes on startup or just gets a blank screen. You SHOULD
see a peculiar little symbol next to the "i" symbol in Firefox. If you do,
click the "i" symbol and you can change this particular URL to "Allow Audio
and Video". This will not make a global change, but only for the web client
URL. Your mileage may vary!
4. If you want to put V5 into pseudo normal use, you can startup the
tray app by adding it to
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run in
the registry. I won't go into how to do that.
5. If the web app does not work correctly, try pressing F5 which should cause
you to have to login again. This will get it going.
6. I ran into security issues trying to use C:\Program Files\NPVR for the NPVR
folder even though I am "admin".
Kodi v19 is introducing a new feature that matches the New indicator in NextPVR. https://github.com/xbmc/xbmc/pull/16645 Unfortunately they aren't using a flag at this point they are going to be basing it on the original air date. There are a couple of things that we need to do. First I'd to confirm that you pass it as is, which we can assume to be local time (appears to be the case with Schedules Direct) Kodi needs it converted to UTC
There are lots on anomalies with the SD data (more than half of my database)
- it is the production year for movies (first run meaning first TV broadcast)
- for imported shows like Coronation Street they can be marked new but the original broadcast date could be two weeks earlier in the UK.
- varies for live events empty for sports, the first broadcast date for many news and talk shows
I think it will be easy enough to fake the original_air_date to be the start_date to handle some issues, If we don't things like a new episode of "Saturday Night Live" might show 1975-10-11.
My first question is should we clean up these dates? If so should it be done in Kodi or NextPVR? I think Kodi unless you plan on showing this date in your apps.
My second question is after your trip could you add the Live indicator from SD (it might be liveTapeDelay) as a significance. For me it is much nicer to present live events as new not live. Emby supports it now (I am faking it for some sports) and I mentioned it to ksooo too and Kodi will likely have new and live flags. If we don't fake the date in Kodi then they won't show as new so we'd need this as an indicator in the web app to show why
I'd like to do some work on the Knewc skins... there are a few issues there that I believe I could contribute to.
Specifically, I can't make any of them work on Android/Touchscreen, though I can get around it by using a keyboard. It seems like it's close to working, but there are bugs that defeat every combination of Kodi and NextPVR skin that I have tried.
The skin selection in NextPVR also seems like it could use some work. It's just opaque to the user what that selection does and how it's used, what should work and what shouldn't. At least, it confused me as a user, and it took quite a bit of forum conversation to figure out what was going on there.
Tried the latest build but the service was not created when I ran installservice.bat as admin and got this message...
C:\WINDOWS\system32>echo OFF
adding firewall rules... starting service... The service name is invalid.
More help is available by typing NET HELPMSG 2185.
will start web app setting soon...please wait
For one thing, in the bat file part of line 8 has a syntax error which creates an incorrect firewall rule
program="installpath%Client\NextPVR.exe" enable=yes > nul
So I changed it to...
program="%installpath%NextPVR.exe" enable=yes > nul
The firewall rule was fixed but it still gave me the error message.
After messing with the bat file I got it to work by changing the last bit of line 12 from ">nul" to "> nul"