I've had my setup working perfectly for about 1 year. This week though, my EPG stopped working (blank data). I went to the Channels menu to manually update them but all the channels were gone. So I went into the Devices menu and my tuner card was missing. I looked into the Device Manager on my PC and I could still see the card.
So I...
Restarted the PC = no difference
Reinstalled NextPVR = no difference
Uninstalled/reinstalled the tuner card and made sure the drivers were up to date = no difference
Installed some other capture software = which CAN see the tuner card
I'm currently going through a process of converting from WMC to an Emby/NextPVR set-up and have found the latter much more flexible. I have come across one challenge that I was able to create/follow a work-around for but it seems like something that was addressed for Guide population in NextPVR but not for setting up recording entries. I haven't been able to find any relevant prior entries in the forum for this.
The problem first manifested itself to me as the Emby/NextPVR plug-in not being able to import any Pending Recording (Schedule in Emby terms) data from NextPVR though this seems to be a side-effect of the set-up of the Pending Recording entry itself in NextPVR. Checking the Emby logs it seems NextPVR just returns an error that halts the Schedule import process in Emby and no Schedule entries are imported. The NextPVR web log, as attached, indicates it encounters an invalid hexadecimal value while processing the Pending Recording entry to send to Emby. The Guide import into Emby worked fine. This situation also seems to be reflected in how the NextPVR GUI does, or doesn't, display the information - screenshots also attached.
To work around this I edited the XML column in the SCHEDULED_RECORDING row for the program in the npvr.db3 database to remove the area where the invalid characters seemed to be and everything started working fully again - the Pending Recording entry in the NextPVR GUI now showed a description/etc. and Emby was able to get a full import for its Schedule. Guides in both applications continued to display information as expected. As I have my guide acquisition set to 8 days this started a week before the program was due to show and I had to perform the work-around each time NextPVR refreshed its EPG data (scheduled once a day via OTA). As this Pending Recording entry was being generated by a Keyword-based Recurring Recording entry I tried alternatives such as using a "Record Once" set up and also a "Record All Episodes..." set up but the same symptoms emerged for both the NextPVR GUI and the Emby Schedule import.
I appreciate that any similar problem for Guide import into Emby may have been resolved by an update to the NextPVR plug-in for Emby and, if so, will raise this issue there but thought that as there is also an upstream impact with NextPVR itself that this may be the most appropriate place to start.
I'm a newbie to Next PVR, but I'm a long time user of WMC and I have OTA setup running side by side with Next PVR on a Win 7 computer. I'm planning on shutting down the WMC as soon as I get NPVR doing everything I want. Here's one thing I have not been able to figure out how to do yet.
Concerning EPG on WMC - With Schedules Direct; I'm using OTA only, and I can manually add what I call a phantom station, such as ESPN, on an unused channel such as 50.1. Then the EPG will add it to the TV Guide listings. The whole idea was to be able to see what is playing, when, on ESPN or any other streaming tv channel (ESPN is just an example). I can add as many different phantom listings as I want. If you're wondering why I do this, It makes it convenient to see what is playing so I can switch to my smart tv and watch streaming channels there.
I have not been able to find a way to do this with NEXTPVR. I have the OTA channels working just fine with Schedules Direct EPG. Can someone point me in the right direction?
Good day...Well first off I had received this problem initially some time ago. That is, the problem of not finding an available capture device with a 403 error code. It was fixed back then through this forum by installing an updated/fixed Nshared.dll file. Everything has been working fine for several months until today. This area experienced an electrical shortage which obviously shut everything down. Once I was back up I returned to watch my programs in NPVR just as prior to the shortage. Which is when I received the error telling me that NPVR was unable to find....
I need your help on this. I have attached the logs as well. Cheers...
I noticed that if I have two monitors and my configured "main display" is monitor #2, NextPVR will start on it ok, but it use the setting from monitor 1
2018-12-11 15:22:30.366 [DEBUG][1] Rendering for screen size: 1680x1050
If I change the NextPVR setting to use my "secondary" monitor
2018-12-11 15:26:42.662 [DEBUG][1] Rendering for screen size: 2560x1440 (seems to be adjust using the Font Scaling)
So this is what I would like to do. Use Kodi to stream live tv on my phone out side my network. I have it configured correctly in my router and Kodi. loads the guide. When playing a channel Kodi tells me that it can't find my Colossus 2 card. I know its working because I can use it in NextPVR android app. Dose any know what is going on here? Do I need to configure some networking options in Kodi?
Hi, I have used NextPVR for a few years now, upgraded to windows 10 a couple of years ago without any difficulty, but recently reset my Windows 10 after it became unstable. Consequently had to reinstall NextPVR and now I can't get it to work right.
I have a TBS 6220 DVBT/T2 tuner, which prior to the reinstall was working fine, and picking up HD channels fine (like yesterday...).
Today, after reinstalling everything NextPVR refuses to admit its a T2 tuner and only turnes in the SD channels.
I've checked the driver for the tuner card, and its the most up to date, so does anyone have any suggestions about what I can do to convince NextPVR that it's a T2 tuner?
4.2.3. If I disable a recurring recording on the host computer, it takes about seven seconds to execute (i7 laptop, SSD). The same command on a client locks up the client and it has to be killed with task manager. Oops, while typing this post, 3-4 minutes after issuing the command, the client finally finishes executing the disable command.
