This is because many modern tuners will compensate with AGC an offset
like this. If you point them 125000 Hz wrong they will auto-correct to
the correct frequency.
Cool, I hadn't realised that, Rudy.
That also means that the scanning code must be grabbing
the scanned frequency _back_ from the frontend!
(i.e. mythtv-setup says "try 191625000", frontend locks,
fine tunes to 191666000, and mythtv-setup reads
and stores that value in the database)
Of course, the other possibility us that there are integer
math rounding errors in the frontend driver code :-)
I will have try now with my older cards, to see what they do.
--
Nigel Pearson, [EMAIL PROTECTED] | "People say I'm strange, does it
Telstra BI&D, Sydney, Australia | make me a stranger?
Office: 8255 4222 Fax: 8255 3153 | My best friend was born
Mobile: 0408 664435 Home: 9792 6998 | in a manger" -DC Talk
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
