I have no idea if the matter was ever discussed here but there is something in the client's UI that always felt wrong to me.

I mean the up/down arrows can mean opposite things.

If you think at the channel number the arrow up button means obviously CH+

But if you think to the general GUI (say EPG or Channel Page) up means moving toward the top of the list, so CH-

This is not only a NPVR thing, Kodi in some skins has the same problem, except that NPVR makes the matter even worse placing the CH+ button on the left, while on everything else when you have a "something+" it is placed on the right.

The result is that on the stock GUI I have always to think twice before realizing "which is which"

So why not just stick with something with a unequivocal meaning like CH-/CH+ pr even just -/+ like in WMC ?

I modded my NPVR4 skin, years ago, I'm not a designer but just to give you the idea I attach a comparative screenshot of my setup

Attached Files

Thumbnail(s)
   

Logs attached for server crash about 9:50pm CDT 7/27/21.  We had a show playing on the server PC with kodi/knewc and my wife went up to bed and tried to start a show on the ODroid N2 upstairs when it crashed.  Server PC playback was still going, but ghosted behind Kodi menu.

Thx,
-Brad

Attached Files

  npvr_server_crash_logs-20210727-2152.zip (Size: 1.07 MB / Downloads: 3)

What ports need to be open for remote access?

Premise:

Win 10 build 10240 is the original Windows 10 released in 2015 in various "flavours" (Home/Pro/Enterprise and so on), it was superseded each six months by new features updates, so most of those "flavors" are unsupported today.

Most except the LTSB2015 edition, where LTSB stands for "Long Term Servicing Branch", which means that the support ends in 2025

LTSB versions were intended for companies that usually likes stability and simplicity over flashy new features, and that are more concerned about privacy than the random average Joe. That made the LTSB releases the  choice of power users, and by anyone hates the METRO/MODERN Apps, which are absent on LTSB.

Premise 2

Back to NPVR5 there is a catch. NPVR5 needs the .NET Framework 4.7.2 or later, but the 4.7x and 4.8 installers are not available for LTSB2015

Although it can be considered a corner case, LTSB2015 is the closest Win10 version to Win7, so a number of older HW setups that work well with LTSB2015 may not like its younger siblings LTSB2016/2019 or any other current edition.

Here comes my minitutorial, which is aimed to people who's facing the situation described above and wants to use NPVR5 anyway.


-------------------------------------------------------------------------------------------

The solution is pretty simple and easy to rollback, so...

#1 Install LTSB2015 (a fresh install is potentially less prone to problems, but you can try on a old installation as well)

#2 download the latest 4.6.x .net framework installer (currently it is 4.6.2), and install it  (reboot to complete the installation) 

#2b If you need it (for programs other than NPVR) install .NET 3.5.x

#3 Create a temporary fresh LTSB2016 W10 installation, you can use either a virtual machine (Hyper-V is included in 2015, but you can use Virtualbox or VMware as well), a second partition, a second HDD or a native .vhdx on the real HW

#4 download the latest .NET 4.8 installer and install it (reboot to complete the installation)

#4b if you followed point #2b do the same here as well, otherwise skip to point #5

#5 install NPVR5 using its setup

#6 Back to 2015 rename the folder C:\Windows\Microsoft.NET to something else like  C:\Windows\Microsoft.NET.462

#7 mount your virtual HDD, or access the partition where you your LTSB2016 resides.

Assuming your LTSB2016 is called D: copy the Microsoft.NET folder from D:\Windows to C:\Windows

Copy also the NextPVR folder from D:\Program files to C:\Program Files

#8 install the NPVR5 services double clicking on C:\Program Files\NextPVR\installservice.bat
on the same folder doubleclick VC_redist.x86.exe as well
don't forget to create a link to the npvrtray.exe to your startup folder to have it starting on each reboot.


You are done, enjoy NPVR5

----------------------------------------------------------------------------------------------------------------------------------------------------

Additional considerations:

This tutorial, as you can see, is pretty simple to follow, but a minimum skill and common sense are required.

For example, if you need to do a sfc /scannow or a dism command to restore the integrity of your installation do it after renaming the Microsoft.NET folder to Microsoft.NET.48 and the Microsoft.NET.462. to Microsoft.NET, then you can switch back the names

The same is valid when and if MS will publish a 4.6.x update like 4.6.3 for example

Normal monthly cumulative updates should be safe to apply w/o the need of the folder swap, as they usually don't touch the .NET part.

For point #3 you should be able to use any Win10 Anniversary Edition aka 1607 (build 14393) install media.
You are not going to use such installation, so unsupported versions are not a problem

I'm working with a .NET/DISM guru for a proper 4.8 installer, which will lead to a philosophically cleaner way. But cleaner is different than easier, as likely it will requires an offline installation. I'll keep you updated on progress anyway.

Last but not least many thanks to @sub who helped me to better understand what was wrong on such scenario.

I currently run NPVR v4, however, I will be building a new PC and am thinking to install v5. I understand that v5 is web based. I am curious if there are plans to make the service available from any internet source. From the  Install Information page:

Windows Client
The windows client, nextpvr.exe, is included in the 'client' subdirectory. At this stage it can only connect to NextPVR running on the same Windows machine.

Or perhaps I don't fully understand the statement...with v4 I can connect remotely (from phone or work PC) via internet to my NPVR and schedule/watch recordings and live TV. However,  I cannot, understandably, make any changes to the settings of NPVR installed on my PC. With v5, if remote access is ever made available would I then be able to access the NPVR settings? Not sure why I would want to do that but am curious.

Also, what would be/is the main advantage to switching to v5, as v4 works perfectly for me?

Thanks!

Is this possible?  I have just added 4 OTA tuners.  I would like to make them be the first priority for recording the main networks here in the states (ABC, CBS, etc).  But, when I merged cable channel '2' with OTA channel '2.1', it appears that it will never use the OTA tuner.  

Is it possible to merge cable channels with OTA since the programming is exactly the same?

EDIT: Actually, now that I look closer, it also appears that even though the OTA tuners have priority in settings, subscriptions that are marked 'Any Channel' still defer to the Cable tuners.  I can only assume that this is because channel 5 comes before channel 5.1.  Is there any way around this?  Without explicitly setting it to channel 5.1 since I want it to fall back to the cable channel 5 if it runs out of tuners.

I understand that some US cable providers have new channels for the Olympics in 4k.  If anyone could provide me with a 2 minute ts recording I'd like to have a sample for my library of formats.

Japanese 8k samples would be neat too.

Martin

In short, i like to use MPC-HC as a quick and dirty additional way to access my TV channels.

It's light, with a nice and clean UI, and it works in a wide range of Windows versions.

The problem is that, for some strange reasons id doesn't play 100% nicely with NPVR4...

It mostly works, but more often than not it starts playing for 2/3 seconds then it stops, switching the channel back and forth usually leads to a stable play.

Now the part that drives me crazy is that

MPC-HC works with everything (including NPVR5) except NPVR4

on the other hand NPVR4 works with everything (vlc, pov player, bsplayer, and so on) except MPC-HC

I guessed it was a sort of timeout problem, but extending the timeout on MPC-HC didn't help at all

So, not the biggest problem of the universe but something I would like to know.

Maybe it's a known problem for you and you have a ready made solution...

Hi I am trying to get the EPG data from this URL
http://127.0.0.1:8866/services/service?m...gs.current

but it gives this response
<?xml version="1.0" encoding="utf-8" ?>
<rsp stat="fail">
  <err code="8" msg="Invalid Session" />
</rsp>


This has only happened after I updated to version 5.1.3.210711. Is there any way to fix this?
I have ticked the options for Allow remote access/Allow unauthenticated access (this is only accessed locally).

In my country we are at the dawn of great changes in communications...

In autumn 2021 all SD channels will be moved from Mpeg2 to Mpeg4/h264.
Then, in 2022, all channels SD/HD (ad higher res) will be aired only using the HEVC/H265 codec and the 800 MHz band will change its usage from TV to 5G telephony.

I think also in the US the ATSC channels will follow a similar path.

We have already a couple of test channels, just a static frame to test the device readiness to the new standard.

Out of curiosity i tested various SW including NPVR4/5.

They seem both working in general, and Kodi, MPC-HC, VLC are working as well. Windows Media Center instead does not undesrtand the HEVC TV, even if it has no problems with HEVC local files.

Also NPVR seem unable to transcode the signal.

Hence I have two questions:

#1 Is NPVR supposed to transcode such channels? I'm facing a bug or a missing/not yet implemented feature?

#2 Is possible (or will be possible) to set NPVR to transcode not just to browsers but also to selected IPTV clients like WMC and any other clients that lacks the native HEVC capability?

There is no urgency, at lest here there is a whole year before the final migration but I think is better to stay ready both uses as coders.