[vdr] Re: CAM Aston 1.05 workaround

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Antonino Sergi wrote:
> 
> On Mon, 2003-08-11 at 09:36, Klaus Schmidinger wrote:
> > Antonino Sergi wrote:
> > >
> > > On Sun, 2003-08-10 at 11:06, Klaus Schmidinger wrote:
> > > > Antonino Sergi wrote:
> > > > >
> > > > > I also tried the -icam firmware and, for my setup, it works exactly as
> > > > > any other "NEWSTRUCT" firmware (except ll, of course):
> > > > > it produces "outcommand error" till I make it reveal my CAM (by
> > > > > unplug-plug).
> > > > >
> > > > > Anyway, when it is working, I have no access to second language, as with
> > > > > any other firmware.
> > > > >
> > > > > A new thing:
> > > > > I recorded programs form this channel
> > > > >  Jimmy:11843:V:0:27500:2453:2454:0:1:3560
> > > > > for a year; now I can't see it any more and I do not understand why.
> > > > > I can see any other channel in my bouquet, but not this. I can see it
> > > > > only under windows and, of course, by official decoder; I checked PIDs
> > > > > SID and frequency and they are correct.
> > > > >
> > > > > Is it possible they change something in CA_PMTs only for one channel?
> > > >
> > > > I don't think so.
> > > >
> > > > Please check your chanenls.conf entry for that channel.
> > > > The fourth parameter should tell VDR which satellite this
> > > > channel is on. In your case it is '0', which has no meaning.
> > > >
> > > > Klaus
> > >
> > > This is extracted from channels.conf of vdr-1.0.4, which I use for
> > > production, so that 0 is DiSEqC; the entry is OK, in fact, one that
> > > works is
> > > FOX:11842:V:0:27500:2440:2441:0:1:3550
> > > Sorry to have been not clear, but the problem seems really to exist.
> >
> > Strange... DiSEqC is handled quite differently in VDR 1.2, so you
> > really should try to adapt your channels.conf accordingly.
> >
> > Klaus
> 
> Now they changed PIDs for that channel and it works again; I noticed
> that they change PIDs frequently now. Could it be a way to "fight"
> unofficial decoders? (like VDR?)

Well, maybe, maybe not.
You may want to try the autopid patch (from Andreas Schultz) if you
often watch channels that frequently change PIDs.

> I'll keep trying to understand why vdr-1.2 and ll-firmware is not able
> to decrypt.

You're confusing me - didn't you just write "Now they changed PIDs for that
channel and it works again"? You need to be a lot more clear about _exactly_
what you are experiencing with which version of the driver and/or VDR.

Klaus


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.