2018-06-16, 11:35 AM
sinttesi Wrote:... I cannot find the config.xml file. Can someone tell me where it is located in the current version?
C:\Users\Public\NPVR ... http://www.nextpvr.com/nwiki/pmwiki.php?...alledParts
2018-06-16, 11:35 AM
sinttesi Wrote:... I cannot find the config.xml file. Can someone tell me where it is located in the current version? C:\Users\Public\NPVR ... http://www.nextpvr.com/nwiki/pmwiki.php?...alledParts
2018-06-18, 10:00 PM
Thanks Graham - I didn't know what it was called so couldn't find anything in the Wiki (although, installed parts was quite obvious...)
I've extended the scan time (doubled to 6000) and it now picks up all the correct channel numbers. Thanks folks
2019-04-27, 05:15 PM
I have similar problems with incorrect channel ordering. I located config.xml here C:\Users\Public\NPVR but couldn't find any entry for <ScanDropTime>
I tried adding <ScanDropTime>3000</ScanDropTime> but this had no effect. Am I using the wrong config.xml file or has the parameter been moved or rename? Paul
Windows 10 Pro 10.0.19041, 64bit 2.50GHz 8GB RAM
Hauppauge WinTV-dualHD TV T2 IPTV stream NextPVR 5.1.0 (201214)
2019-04-27, 05:55 PM
Bunkermentality Wrote:I have similar problems with incorrect channel ordering. I located config.xml here C:\Users\Public\NPVR but couldn't find any entry for <ScanDropTime>A config.xml file wouldn't normally have this setting, but instead uses the default drop time of 1000. You can override it by adding the <ScanDropTime> setting in the <General> section. Maybe try 6000, which the user above indicated worked for them when they were having the same issue.
2019-04-28, 12:07 PM
ScanDropTime set at 6000 but still the channel order is wrong. I've appended the log files. If anyone has time to see if these shed any light I'd be very grateful.
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)
2019-04-28, 05:11 PM
Bunkermentality Wrote:ScanDropTime set at 6000 but still the channel order is wrong. I've appended the log files. If anyone has time to see if these shed any light I'd be very grateful.When you're doing these scans after changing values like ScanDropTime, are you deleting the channels before scanning? You'd need to - rescanning wont change the channel numbers of existing channels.
2019-04-29, 11:23 AM
I have twin tuners and I delete both sets of channels before scanning. I also set ScanDropTime to 9000 but I don't notice any significant increase in the channel scan times. This leads me to suspect that the ScanDropTime changes might not be applied.
Windows 10 Pro 10.0.19041, 64bit 2.50GHz 8GB RAM
Hauppauge WinTV-dualHD TV T2 IPTV stream NextPVR 5.1.0 (201214)
2019-04-29, 04:51 PM
Bunkermentality Wrote:I have twin tuners and I delete both sets of channels before scanning. I also set ScanDropTime to 9000 but I don't notice any significant increase in the channel scan times. This leads me to suspect that the ScanDropTime changes might not be applied.If you've got it set to 9000, it should be spending at least 9 seconds on each frequency.
2019-04-29, 04:53 PM
Your last scan logs look like it's getting all the channel numbers. You don't have other channels already in the database, like IPTV? If so, try on deleting all your channels and rescanning.
2019-04-29, 05:17 PM
I was directed to this thread from here https://forums.nextpvr.com/showthread.ph...-any-ideas In there I just came to the same conclusion. The existing IPTV numbers are messing up the DVB-T numbers. I'll exit this thread and conclude the other one.
Thanks for your help with this, Paul
Windows 10 Pro 10.0.19041, 64bit 2.50GHz 8GB RAM
Hauppauge WinTV-dualHD TV T2 IPTV stream NextPVR 5.1.0 (201214) |
|