Then there must be something ``wrong'' with `w_scan' making
incorrect assumptions about the data which it's parsing.
No - i do not think so.
All of the frequencies found are with 166kHz offset.
w_scan does not use any of these 166k offsets, that means this frequency
data was transmitted as exactly such a number in some NIT w_scan parsed.
w_scan calculates DVB-T center freqs as "center freq = (306000000 +
channel * 8000000) Hz" for this range.
And NIT parsing is the same as dvbscan.
What has disturbed me is how this offset has been applied
across the board by `w_scan',
Again, w_scan does not use these offsets.
Some dvbsnoop output as suggested and additional some scan with service
names (either dvbscan or w_scan), vdr channels.conf would be fine, would
really help to see whats going on here.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
