On Monday 26 of January 2009, Chris Silva wrote: > On Mon, Jan 26, 2009 at 5:50 PM, Manu Abraham <abraham.manu@xxxxxxxxx> wrote: > > On Mon, Jan 26, 2009 at 8:19 PM, Alex Betis <alex.betis@xxxxxxxxx> wrote: > >>> Latest changes I can see at > >>> http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 > >>> to 10 days ago. Is this correct? If that's correct, then I'm using > >>> latest Igor drivers. And behavior described above is what I'm getting. > >>> > >>> I can't see anything related do high SR channels on Igor repository. > >> > >> He did it few months ago. If you're on latest than you should have it. > > > > It won't. All you will manage to do is burn your demodulator, if you > > happen to > > be that lucky one, with that change. At least a few people have burned > > demodulators by now, from what i do see. > > > > > > Regards, > > Manu > > Manu, would you be so kind to explain why it will burn the demodulator? > It happens only with 30000 transponders? And only with this card? > Does this mean I can't use my card to see channels on 30000 transponders? > > Chris Regarding the documentation the demodulator is designed to run at max. freq. 99MHz. Some series of demods burn when the freq is set above this value. But this value is enough for most of transponders with SR up to 30000. Some Russian transponders have SR 43500 - so the demod is set a little bit above 3x of this value. This could be dangerous. This patch (or change) doesn't solve the problem with SR of 30000 and FEC 3/4 or 5/6. BR, Ales -- 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
