I am a new user to NextPVR (latest ver. 4) and am trying to set up a Nexcomm R5000-HD usiing the NetworkRecorder plugin. The R5000-HD is already configured and working with SageTV. I disabled SageTV and am tring to get the Network Recorder plugin working now. I can't find very detailed instructions for using the Network Recorder as it relates to the R5000. I have it configured from the NetworkRecorder wiki. When I try to tune a channel I see in the R5000 app GUI that it is opens a stream but then then I get an error that says it can't open c:\users\Public\recordings even though that directory exists on the R5000 server. I have the R5000 on the same server as NextPVR for initial testing. Spent all weekend trying to get it to work. Anyone have any thoughts on what I need to do to make this work?
BTW, here is my networkrecorder.xml file contents:
Overnight I lost both ESPN and ESPN2 for some reason. They tune but all I get is a black screen and no audio. System is a small HTPC that has been running 24/7 without any major issues for the last few years.
Using an HDHR Prime 3-tuner cable card tuner. All channels subscribed channels are working fine. But not those two.
I do not think this is a NextPVR issue ..
I have the same problem when using the HDHR live view program (silicon dust's program). All channels work but not ESPN or ESPN2. Same thing .. no error but just a black screen w/no audio.
Now here is the strange thing. We also have an Xfinity (Comcast) DVR and that DOES display and record ESPN and ESPN2 just fine. So I'm thinking there has to be something going on with Comcast and their line up ?? I am using Schedules Direct for my EPG and that checks out okay. I checked the channel numbers against the Xfinity DVR lineup and all the channel numbers are the same. It looks like my cable card for some reason just decided to not decode those two channels any more? I have started a thread on the Silicon Dust support forum also. Waiting to hear from them before I submit a support ticket to Comcast.
Everything worked last night .. I first noticed the problem earlier this afternoon.
did not complain with anything obvious, have log of it if you'd like to see it.
however, the server did not start. syslog reports
Nov 3 14:16:32 nvr systemd[1]: Starting NextPVRServer... Nov 3 14:16:32 nvr server.sh[8988]: Starting server../opt/nextpvr/shell/server.sh: line 27: /opt/dotnet/dotnet: No such file or directory Nov 3 14:16:34 nvr server.sh[8988]: Done. PID= Nov 3 14:16:34 nvr systemd[1]: Started NextPVRServer.
and indeed /opt/dotnet does not exist, and it is not referenced in the install anywhere (but /opt/nextpvr is)
Appreciate any assistance. Apologies if this is covered in an existing thread. I searched site:forums.next.pvr /opt/dotnet and found nothing relevant via google.
I'm having issues in V5 with the Blaster Executable Path. I'm recording from a Dish STB using a Hauppauge Colossus 2 card, and it doesn't always accept the IR signal the first time. For example, if the STB was in "sleep" mode, it appears that the first part of the IR signal wakes the STB and then the STB is awake but does not select the right channel. This apparently is not that uncommon, and I found a fix to it online that worked with NextPVR V4. Basically, the fix was to call a cmd file, instead of HaupBlast.exe, and the cmd file ran HaupBlast.exe, waited a few seconds, then called it again, then waited a few seconds, then called it again. With this fix, the STB became 100% reliable on a channel change.
When I upgraded to V5, inputting the name of the command file instead of the .exe file doesn't appear to work. Should it work? If so, is there different syntax I need to use within the NextPVR V5 UI? If this is not something that currently works, is there a way to add it to NextPVR V5? Thanks!!!!
I changed my setup by attaching my antenna/hdhomerun directly to my router. Nextpvr finds the device on the network. When i run the HDHomerun app on my ipad and pick up the stream, the channels look great. When i do it through nextpvr, they come up very choppy and degraded. Any ideas why that is?
I've offered to help with skins, and I'd like to have a conversation with whoever is interested...
As I see it presently, we have a selection of skins that are all good, and they each have their purpose, but it's confusing for someone just getting started. I think the skin choice kind of mixes up two concepts, "how I want Knewc to look", and "which skin matches my Kodi skin", which is just a byproduct of the skin architecture. Then we also have the Web Client UI, which seems mostly the same idea, sort of different, but seems to me like it could be part of the same choice.
So here are a couple of proposals to ponder:
1) Make the skin choice one of 3: "Classic", "Match Kodi Skin", and "Web Client UI". If MKS is selected, automatically choose the correct skin (assuming we can detect the Kodi skin, of which I'm not sure, but I think we can). If MKS is selected, but we have no compatible skin, bail out to Classic (preferably with a message). Default could either be Classic, or MKS, falling back to Classic if no matching skin is available.
2) Add an "Auto" choice to the existing selections, which would choose the matching skin, or Classic if we have none compatible. Otherwise, leave it the same, maybe move the "Autostart Web Client" choice into the dialog. If user doesn't choose Auto, their choice overrides, and they get what they get (perhaps with a warning message that the skin may not be compatible).
We'll probably make an Estouchy skin in the relatively near future, so it should be considered how the skin choice is reflected for Touch. I think it becomes more important because if you're on Touch and get in a non-Touch skin, it just seems broken. Kodi has too many broken add-ons, it's very easy for people to conclude that this is just one of them.
Hello! Sometime ago I loaded up nextpvr on a windows 10 laptop and set it to run as a client (by checking the special box and adding an address) on my LAN connecting to the main version running elsewhere on the premises.
After some time I deleted the program as I recall there was some issue with how the client behaves when the main unit is sleeping or off. It got stuck in a state where it keeps demanding that the .db3 file at the server main unit be available or it wont run... and there was no way to stop it from this mad cycle.
So a year later (now) I decided to reload Nextpvr on this same laptop. During the install process the installer reports that same exact server/main unit is currently not available and then completes the install. see this: https://imagebin.ca/v/50KisUV3Wuql I guess the previous install left some garbage pointing to the year old server which does not exist anymore.
I have tried entering only via the task bar and the settings.. same message.. starting the nextpvr program itself also returns the same maddening message.
So my question is where does nextpvr store such pointers on a windows 10 64 bit pc? Would like to get rid of it so nextpvr runs standalone on this laptop.. not as a client? This must be some sort of oversight in the coding process?
