[vdr] Problem: Conax not available after VDR startup
Klaus.Schmidinger at cadsoft.de
Sun Aug 7 17:22:15 CEST 2005
Rantanen Teemu wrote:
> Klaus Schmidinger wrote:
>>Strange. My two CAMs (both connected to my third DVB card) are
>>some 15..20 seconds after VDR is started - long before the EPG scan
> kicks > in.
> I didn't have any timers right now, so I could do some timing. The times
> between "VDR version 1.3.23 started" and "CAM: Conax ..." were: 56, 66,
> 66, 67, 67, 67 and 68 seconds (in the same order). Weirdly regular
> times, but cannot (shouldn't) be CPU related as there's lots of idle on
> the CPU.
> Well, it isn't *THAT* long time, but still feels a lot longer as you
> know it *COULD* detect Conax right away, and you know you're missing
> something on live-tv or on recording...
> If I knew what does make driver detect the Conax card, then I could hack
> my VDR to do that on a startup...
I ran a test with only encrypted channels in my channels.conf,
and here's what happened:
Aug 7 17:12:41 video vdr: VDR version 1.3.28 started
[ ... usual loading messages ]
Aug 7 17:12:52 video vdr: switching to channel 1
Aug 7 17:12:52 video vdr: info: Channel not available!
Aug 7 17:12:54 video vdr: switching to channel 1
Aug 7 17:12:54 video vdr: info: Channel not available!
Aug 7 17:12:57 video vdr: ERROR: Channel not available!
Aug 7 17:12:57 video vdr: CAM: Irdeto ....
Aug 7 17:13:10 video vdr: switching to channel 1
Aug 7 17:13:11 video vdr: transfer thread started (pid=31453, tid=147466)
Aug 7 17:13:11 video vdr: receiver on device 3 thread started (pid=31454, tid=163851)
Aug 7 17:13:11 video vdr: TS buffer on device 3 thread started (pid=31455, tid=180236)
So all in all it took 30 seconds.
You could test the following: change the line
newSet.Wait((ciHandler && (time(NULL) - startTime < 20)) ? 100 : 1000);
newSet.Wait((ciHandler && (time(NULL) - startTime < 80)) ? 100 : 1000);
(make the 20 an 80). Does this change anything?
More information about the vdr