Hey guys, I have an issue that I have spent many hours trying to fix (posting here is my lat option)
I have NextPVR and a HDHomeRun - this used to work flawlessly but then recently stopped recording or tuning to a channel.
HDHomeRun successfully detects all channels but when I do a channel scan with NPVR It doesnt scan any channels. The only thing thats changed recently would probably be a software update.
windows 10 on an intel nuc i3.
Some things I have done to try and fix the issue:
I have completely disabled the windows firewall
reset the HDHomeRun, checked for updates, reconfigured the HDHomeRun and rescanned fpr channels
done a fresh install of Windows 10 - reinstalled the software and started again
in the HDHomeRun I changed the 'BDA Compatabiliy mode' to both 'default' and 'NextPVR' but neither worked.
I have attached the log. any suggestions would be hugely appreciated.
I've been using NextPVR for about 6 months and found it an excellent product, primarily recording UK Freesat TV shows and Movies, using a single card with 2 x Black Gold BDA DVBS Tuners (and 2 x DVBT tuners which I don't use).
I then use MCE Buddy to convert the ".ts" files for playback though Plex and have build up about 4TB of TV shows and moves so far. Good support documentation means it has been an easy process to setup and fully automate.
The one problem I have is that about 20% of recordings have a narration - intended for the visually impaired. This narration is played back whether listening directly to the ".ts" files using VLC on the main server, or via Plex on one of the TVs. It does not appear to be limited to a single Freesat TV channel, or logical grouping of channels and does not happen all the time. I have searched and can not find settings, forum articles or guidance on how to fix this.
I'm currently running Next PVR 3.9.2 (161119).
Any what I may have setup incorrectly would be greatly appreciated. I can setup any tests and provide further info if it helps.
I did a new installation last night and everything is working flawlessly in Kodi through Windows 10 but stuck with fine tuning.
A lnk has been created to update the guide automatically twice a day just after webgrab updates the xmltv file programmed on the windows task scheduler.
(nextpvr.exe -UpdateEPG)
The issues I'm having are:
1. When the task is run, after the update the program opens (actually opens minimised). Would be possible to not pop up after EPG update?
2. As I'm on Spanish Tv the scrappers are not good for local content, all the posters are on my Xmltv file, is there a way to load them from there?
This is a minor issue, but I do not know if it is X-New issue or a Nexpvr issue. In any case, over time TV guide listings do not get updated. Say I start the web client on Kodi today, in about two weeks it will show empty listings. I have to go and restart recording service on the server to populate TV Guide. Thanks
Hello, excellent program so far, my to go for all PVR needs.
I was testing KODI 17 RC for android and noticed that when switching channels, some HD channels stay in slow motion. I keep the channel on, but it doesnt change. If I switch channels and go back, it sometimes fixes itself. No specific channel, happens to any HD channel.
I am a running a fork of KODI on the same android system called SPMC by koyting with no issues, it is based om KODI 16. Both deployments are using about the same amount of CPU and memory when browsing the KODI interface.
Is there something I can test to provide further information?
If I run the NextPVR app, recordings with .edl files are respected and the commercials are skipped as they should be. If I playback using the web interface (i.e. http://localhost:8866), the commercials are back. Is this as it should be? Is there a way to configure web interface playback to respect the .edl files?
Time has come for me to move away from NextPVR. It has served me well, getting me in to DVBx viewing, but I've moved my setup now over to TVHeadend. I've saved my entire NextPVR config so that I can always reactivate if need be.
I moved to TVHeadend for a number of reasons, but mostly around the bulk handling of the channels, the idle scanning, the built in Newcamd/DVB-API functionality, the (much) faster channel switching...
I did think long and hard, but it was the right move for me - but I will keep a keen eye on here for the updates to NextPVR. Many thanks to everyone for all your contributions but especially to sub. Good luck and happy 2017.
I had to reinstall my HTPC yet again (finally replace the ailing hard drive).
Everything installed just fine but when I try to bulk map, I now get an exception error. It occurs when I press the bulk map button. I am running 3.9.2 (161119) of Next PVR.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at NShared.SchedulesDirectJSONEPGSource.GetChannelsForLineup(SchedulesDirectLineup lineup)
at NextPVR.Settings.ChannelRemapForm.LoadChannelList()
at NextPVR.Settings.ChannelRemapForm.ChannelRemapForm_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
