I have begun using NextPVR V5 that is installed on the same machine with the V4 installation.
I would like to help out with testing V5 but I'm not sure how to proceed. Can I assume that everything that is shown in either the web or desktop app should work? I've tried quite a few operations and I am getting some good results. But not all.
Would you prefer that I simply list the things individually or just send a broadside post? Are there areas of V5 that shouldn't be of concern yet simply because development is ongoing?
For instance:
- Web App - Settings - Devices - Do groups work? I can add a group name but seem unable to add channels to it.
- NPVR Tray - Popup always shows device list collapsed. Would much prefer it to show expanded devices that are active.
- Desktop App - Live TV - Will not show channel list from right-click context menu.
Hi, I'm new here but I use npvr for years.
My question is:
Is there a way to convert c:\users\public\npvr\npvr.db3 to some xml or csv with just ...
channel name, programme title, start time, end time, description
so I can read the resulting file somewhere else?
Much appreciated any kind of help.
Would I be wasting my time by attempting to install NPVR v5 public beta on a PC running Windows Vista? My guess is that Vista is unsupported now due to .NET Core, if nothing else. (In case anyone was wondering, NPVR 4.2.4 works fine on Vista.)
As the title says, are they on your radar? I assume there are significant challenges that explain their absence, ie. if it were easy, they would already exist...
Just updated the guide and wondering if there should be gaps in it
[ATTACHMENT NOT FOUND]
As I use Emby, I updated the guide in Emby using, I presume, the plugin, and the gaps that show in the NextPVR guide have programs in them in the Emby guide. So assuming the programs in the Emby guide weren't left over from a previous update, shouldn't they show up in the NextPVR guide as well.
I did some initial testing with v5 and like what I'm seeing so far. In particular I noticed it automatically creates IPTV Channel groups for me from the channel listings, whereas with v4 I had to create them myself (unless I'm missing something?). One feature request - in the groups list (Channels > Advanced Tools > Channel Groups), would it be possible to add a "hide" feature to hide channels from a particular group? The current option of deleting the group makes it tedious to restore the group at a later date. For example, I'd like to be able to hide sports group channels (NFL, NHL, NBA etc.) during the off seasons, then make them visible at the appropriate time.
Seems quite a new thing, but nothing changed apart from Windows updates?
Code:
[COLOR=#000000][FONT=Verdana][h=1]Server Error in '/' Application.[HR][/h][h=2][I]Unable to initialize the native configuration support external to the web worker process (HRESULT=0x80040154).
nativerd.dll must be in %windir%\system32\inetsrv.[/I][/h][/FONT][/COLOR][COLOR=#000000][FONT=Verdana][/FONT][/COLOR][FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif][COLOR=#000000][B]Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
[B]Exception Details: System.InvalidOperationException: Unable to initialize the native configuration support external to the web worker process (HRESULT=0x80040154).
nativerd.dll must be in %windir%\system32\inetsrv.
[B]Source Error:
[TABLE="width: 100%"]
[TR]
[TD]Line 128: {
Line 129: Logger.Info("Checking default login page configuration setting....");
[COLOR=red]Line 130: Configuration objConfig = WebConfigurationManager.OpenWebConfiguration("~");
[/COLOR]Line 131: AuthenticationSection objAuthSettings = (AuthenticationSection)objConfig.GetSection("system.web/authentication");
Line 132: if (objAuthSettings != null)[/TD]
[/TR]
[/TABLE]
[B]Source File: c:\Users\Public\NPVR\web\Logon.aspx.cs[B] Line: 130
[B]Stack Trace:
[TABLE="width: 100%"]
[TR]
[TD][InvalidOperationException: Unable to initialize the native configuration support external to the web worker process (HRESULT=0x80040154).
nativerd.dll must be in %windir%\system32\inetsrv.]
System.Web.Configuration.NativeConfigWrapper..ctor() +273
System.Web.Configuration.ProcessHostConfigUtils.InitStandaloneConfig() +125
System.Web.Configuration.ProcessHostMapPath..ctor(IProcessHostSupportFunctions functions) +80
System.Web.Configuration.IISMapPath.GetInstance() +89
System.Web.Configuration.HostingPreferredMapPath.GetInstance() +11
System.Web.Configuration.WebConfigurationHost.ChooseAndInitConfigMapPath(Boolean useConfigMapPath, IConfigMapPath configMapPath, ConfigurationFileMap fileMap) +82
System.Web.Configuration.WebConfigurationHost.InitForConfiguration(String& locationSubPath, String& configPath, String& locationConfigPath, IInternalConfigRoot configRoot, Object[] hostInitConfigurationParams) +304
System.Configuration.Configuration..ctor(String locationSubPath, Type typeConfigHost, Object[] hostInitConfigurationParams) +169
System.Configuration.Internal.InternalConfigConfigurationFactory.System.Configuration.Internal.IInternalConfigConfigurationFactory.Create(Type typeConfigHost, Object[] hostInitConfigurationParams) +30
System.Web.Configuration.WebConfigurationHost.OpenConfiguration(WebLevel webLevel, ConfigurationFileMap fileMap, VirtualPath path, String site, String locationSubPath, String server, String userName, String password, IntPtr tokenHandle) +785
System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration(String path) +59
N_EWA.Logon.checkLoginPage() in c:\Users\Public\NPVR\web\Logon.aspx.cs:130
N_EWA.Logon.Page_Load(Object sender, EventArgs e) in c:\Users\Public\NPVR\web\Logon.aspx.cs:53
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +85
System.Web.UI.Control.OnLoad(EventArgs e) +61
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2646[/TD]
[/TR]
[/TABLE]
[/B][/B][/B][/B][/B][/B][/COLOR][/FONT]
The date format everywhere in the Web App on my Windows V5 server is mm/dd/yyyy. I dont know if its a recent change or if its always been like that as mainly use the Web app for Settings. It just seems to be in the web app as dates in the NextPVRServer cmd window are in the correct format. The date format is correct on my Linux V5 server Web App. Is there a setting somewhere that has got changed?
Further to comments over on Emby Forum, and briefly mentioned on this forum, item 'syncing', am finding v5 starts to play channels in Chrome using localhost:8866 in about 17 seconds, while the same starting in vlc take about 9 seconds. Am hopefully attaching a log from NextPVR from the localhost:8866 Settings page.
