4.2.1 available (3rd June)

[sub]

You can download 4.2.1.180602 from http://nextpvr.com/NPVRSetup_4_2_1_180602.exe

Please post any support issues in the support forum. Support questions posted in this thread will be deleted.

Changes:

- now bunding VS2017 runtime with installer
- added an 'Advanced DVB/ATSC EPG Settings' button to allow more control over the broadcast EPG is received
- HDHR device type now using http instead of udp
- HDHR device type now available for HDHomeRun device. Previously it was only shown for HDHR Prime devices. For other device types, you can continue to use the existing BDA drivers, or the 'HDHR' device type.
- Added support for CordCutter TV network tuners
- Added support for ATSC SAT>IP network tuners
- fixed issue where Channels Details screen could sometimes show wrong channel mapping with XMLTV
- added new 'Name - Icon' mode for guide channel names
- more IPTV improvements (stability, support for more IPTV providers)
- fixed issue where sometimes channel logos weren't being downloaded from IPTV service
- fixed issue where IPTV recordings could continue to say they were recording, after they had really finished.
- improved automatic IPTV xmltv channel mapping for providers not using the 'tvg-id' tag
- added support for IPTV m3u tvg-chno tag (for channel numbers)
- fixed issue with digital signal lock/quality/strength info shown with Ctrl-I.
- added ability to specify prefer DVB EIT language, for countries that are transmitting EIT in multiple languages
- fixed issue where sometimes when skipping back during playback, it could start fast forwarding very quickly to the end of the file
- fixed a bug that could cause an invalid characters in <UniqueID> during an export.
- fixed issue where NPVRTSReader4.ax could crash when playing back files with reception issues.
- fixed bug where 'watched' indicator was not showing up on a client PC.
- fixed issue with EPG-Based timeshifting with Analog and HDPVR style devices.
- added option to sort both directories and files in alphabetical order in the library screen (previously, and still the default, is to shows directories first, followed by files)
- fixed issue where installer could try to start the recording service twice, resulting in an error message, even though the recording service was successfully started

[scJohn]

So, if I have a SD Connect device. Do I have to perform a rescan in Settings => Devices to start using http? Or is the switch to udp automatic with the update?

[sub]

So, if I have a SD Connect device. Do I have to perform a rescan in Settings => Devices to start using http? Or is the switch to udp automatic with the update?

With a HDHomeRun, when you visit the Settings->Devices screen, you basically have the choice of two different types of device. You'll see the same ATSC/QAM devices listed that you've had before, but you'll also now see a 'HDHR' device. Previously this 'HDHR' device type was only shown to users of HDHR Prime devices. Now it'll show for all HDHR devices.

The 'QAM'/'ATSC' devices are the same as they always have been, using the SiliconDust BDA drivers (which behind the scenes uses UDP).

The 'HDHR' device uses HTTP. (In previous builds the 'HDHR' device type used UDP, but now updated to use HTTP)

You have to choose one or the other. For existing users, unless you're having problems, you're probably better off just sticking with the existing QAM/ATSC setup (so you don't have to delete your channels and effectively start over setting up). For new users, you're probably better off using the HDHR option.

One advantage with the QAM/ATSC BDA device types, is that it can do multiple channels at a time from the same frequency. The HDHR device can't do that. The HDHR device does have the advantage of using less network bandwidth though, and is able to retry when any lower level IP packets are lost.

[JP23]

Can confirm that the watched indicator is now showing up on my client PC - thanks for the speedy fix!

[bicbasher]

For the first time in months, no issues at all with this update. Well done sub.

[koijh65]

Will the HDHR device setting that uses HTTP ever have the ability to tune multiple channels from the same frequency?

[koijh65]

Can the CordCutter TV network tuners use multirec/tune multiple channels from the same frequency while only using 1 tuner?

[sub]

Will the HDHR device setting that uses HTTP ever have the ability to tune multiple channels from the same frequency?

I suspect not - it's a limitation of the device, not NextPVR. You do have the option of using the BDA drivers though if you need this feature.

Can the CordCutter TV network tuners use multirec/tune multiple channels from the same frequency while only using 1 tuner?

No, this is a limitation of the device.