On Tuesday 02 March 2004 14:25, Johannes Stezenbach wrote: > Andrew de Quincey wrote: > > The frontend on mine can get a lock at 27500, but I'd noticed when I read > > the values back from the hardware that it had actually detected 27504.. > > Sounds like the broadcaster has a problem. > > > Another thing is that 11747000 is _really_ close to the lnb switch > > frequency of 11700000.. could that have something to do with it I wonder? > > The switch frequency is chosen somewhat arbitrarily. Does it work better > if you change your switch freq to 11750000?
Yeah, I've already tested that: I can lock on, but the VERROR rate is 65550 ish. Whereas, the VERROR with the frequency inversion on is 0 always. > > Is there any actual point in being able to specify the inversion then? It > > sounds like we should always be using INVERSION_AUTO to ensure we don't > > get these problems. > > IMHO the intention was that the application finds out the actual inversion > during scan, so that later it can specify the correct inversion to speed > up tuning. Ah right. Hmm, thats not how it is being used in the apps I checked. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
