Quote:
|
Originally Posted by pictureon
I think network search would also find transponders that belong to network like Globecast. So if a network transponder has changed, network search would find the new transponder.
Example: recently globecast (IA5) changed TP 11929 channels to 12083. If you perform a network search, it would update 11929 to 12083 and find moved channels.
|
At least on the Fortec, the Network search requires that you scan on a transponder, so if you tried to scan the 11929 TP in your example, nothing would be found. However I don't know what would happen if the 12083 TP was scanned.... ie perhaps it would replace the previously saved channels from the 11929 TP, rather than creating NEW channels, which is what a TP scan does ??? Unfortunately, I don't have the 11929 TP saved on my receiver, or I'd give that a try. I'll have to watch for another TP change on
IA5 and see if that happens.
This does introduce another question though, and that is, just where is this "network info" stored on the receiver. Ie I was thinking about loading in an old channel list that I saved using the PC channel editor, which might contain the 11929 mux you mention, however the saved channel list doesn't contain any info other than the Freq/Sr channel names, channel numbers, and the PIDs, so I don't know how a network search would identify the channels, other than by the name, which isn't a very reliable method.
Anyway, I've experimented with a few cases where network info changed on a channel, but wasn't able to see any difference between network and TP scans, but next time I hear about a change on IA5 I'll try again. However, I guess that means I should scan in all the IA5 muxes, since I haven't done that, as I don't watch that sat much.