On 05/04/08 10:34, Pierre-Yves Paranthoen (PERSO) wrote:
> I also increased values in
> #define TS_SCRAMBLING_CONTROL 0xC0
> #define TS_SCRAMBLING_TIMEOUT 5 // seconds to wait until a TS
> becomes unscrambled
> #define TS_SCRAMBLING_TIME_OK 15 // seconds before a Channel/CAM
> combination is marked as known to decrypt
> still the same.
> May 4 10:33:34 localhost vdr:  info: Channel not available!
> May 4 10:33:45 localhost vdr:  switching to channel 21
> May 4 10:33:45 localhost vdr:  transfer thread started (pid=1348,
> May 4 10:33:45 localhost vdr:  receiver on device 1 thread
> started (pid=1348, tid=1536)
> May 4 10:33:46 localhost vdr:  TS buffer on device 1 thread
> started (pid=1348, tid=1537)
> May 4 10:33:48 localhost vdr:  ERROR: CAM 2: session for resource
> identifier 00400041 already exists (1/1)
This is getting stranger by the minute...
Why would the CAM try to establish another MMI resource?
Are you sure this is an unpatched version of VDR 1.7.0 (except for
the patch to device.c I gave you)?
vdr mailing list