Hi, > It surely only needs to store the frequency that worked ? The scan won't > rescan for transports. It will rescan services on those transports > though.
OK. That seems reasonable. > As far as I understand it. The frequency list, is just a list of > alternatives. So if you get one that works, for a transport that should > be it. (Of course I might not be understanding this correctly). What I > will say is, that I have had reports of this code working, although > Simon did have to increase the tuning timeouts. I've re-read that code....think I understand what it's trying to do now. I'll bump up the timeout a chunk like you suggested and see if that fixes it. I have noticed some pretty odd behaviour tonight. I left the setup program running doing the scan while I went off to do other things...when I came back to it about an hour later it seems to have finished! The frequencies listed in the database are still wrong but the channel list had been filled out and was correct. Myth works fine and I can watch TV just as it used to when I manually filled out the channel definitions...strange. thanks for your help, Dave -- David J. Fiddes <[EMAIL PROTECTED]>
_______________________________________________ mythtv-dev mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
