2020-12-15, 08:44 PM
I haven't posted about it just yet (busy on day-job stuff), but I've updated the builds 5.1.0.201216, which is pretty much the same as the last build, but increases a timeout.
2020-12-15, 08:44 PM
I haven't posted about it just yet (busy on day-job stuff), but I've updated the builds 5.1.0.201216, which is pretty much the same as the last build, but increases a timeout.
2020-12-15, 09:02 PM
(This post was last modified: 2020-12-15, 09:05 PM by thecubasekid.)
Thanks Sub
is the docker build updated also? i see in settings it suggests the new version is available to download, but when i pull i still get the old image and the notification that new build is available stays. i tried using both 'stable' and also 'latest' but both give me 5.1.0.201214 (i normally use 'latest') thanks
2020-12-16, 01:33 PM
(2020-12-15, 08:44 PM)sub Wrote: I haven't posted about it just yet (busy on day-job stuff), but I've updated the builds 5.1.0.201216, which is pretty much the same as the last build, but increases a timeout. I've just reinstalled 201216 and repeated the IPTV Import. This now works. However my source M3u file has 177 channels but only 26 of these are imported. Does this suggest that the timeout needs to be increased?
Windows 10 Pro 10.0.19041, 64bit 2.50GHz 8GB RAM
Hauppauge WinTV-dualHD TV T2 IPTV stream NextPVR 5.1.0 (201214)
2020-12-16, 01:50 PM
Guess what I am going to ask for?
Martin
2020-12-16, 02:53 PM
(2020-12-16, 01:50 PM)mvallevand Wrote: Guess what I am going to ask for? Touche! After a Win10 reboot a subsequent delete and M3U reimport collected 454 channels, 117 active. Delete of IPTV device plus rebuild also showed 454 channels. This failed several time previously. Only difference is that I've now done a reboot plus some updates to channels in m3u. So this is a false alarm. Apologies. All looking good now. Many thanks, Paul
Windows 10 Pro 10.0.19041, 64bit 2.50GHz 8GB RAM
Hauppauge WinTV-dualHD TV T2 IPTV stream NextPVR 5.1.0 (201214) |
|