Hi, Prog, i have scanning problems with the last versions. When i scan a satellite, it looks repetead frequencies, but with the other polarity. For example I want 4000,H, 27000 but it scan this and 4000,V, 27000 which is not present in my frequencies list.
Then, scan saves many wrong channels (H or V) not present in satellite.
I see that the NIT search is doing bad things, too, as many times scan ends with repeated chanels, but with small diference frequencies (2-3 MHZ). Couldn´t scanner be more smart, or turned off and dont save these repeated? I find it is worst with poor signals.
What to do, so?

Do you need options for disable NIT scanner?

Yes, think it would be nice feature, for poor signal satellites scan.
Thank you.

If NIT frequencies differ from the transponder list database, that lists should better be corrected by the author.
Perhaps a minimum spacing between transponders might be implemented with the software, below of which the closest existing value would be used, instead of assuming a new transponder. Same symbol rate and FEC used would be good additional criteria, to avoid errors.
What is the minimum possible distance between active SCPC DVB signals (on the same polarisation), perhaps 2 MHz?
Less than that should be within AFT range anyway...

If NIT frequencies differ from transponders found on a blind scan, the LOF(s) used should be corrected by the user, to tune to the true centre frequency as close as possible and get the best possible lock.

Juergen, thanks. You are correct. But my point is that i´m havinq these problems about 3 or 2 past versions released. I have not noted this before.
I´m now scaning C band, but with strong Ku signals problem does not happen. Other thing noted, locking seems harder now, takes longer to occur. Let´s keep observing.