On 04/20/08 11:31, Pierre-Yves Paranthoen (PERSO) wrote: > Hi Klaus and thanks for getting back to me. > > I tried my orginal (ver 1.4.7) channels.conf under the new installation > using this syntax : > > TF1;CSAT:11895:vC34:S19.2E:27500:171:124=fra,125=eng:53:500,100:8371:1:1074:0 > > As it was not working i've generated a new channels.conf : > > TF1;CSAT:11895:vO0S0:S19.2E:27500:171:124=fra,125=eng:53:0:8371:1:1074:0 Looks good. > I also tried to manually edit the channel info under the OSD and put the > FTA value as described in the changelog. Then change to another channel > and came back to the modified one. > > No result at all. > > > I'm still investigating and i've also remarked that VDR was randomly > accessing correclty to the CAM module : > > first case : > > Mar 31 07:49:04 localhost vdr: [18366] CAM 1: no module present > Mar 31 07:49:05 localhost vdr: [18366] CAM 2: module present > Mar 31 07:49:06 localhost vdr: [18366] CAM 2: module ready > Second case : > Mar 31 08:42:07 localhost vdr: [18366] CAM 1: no module present > Mar 31 08:42:10 localhost vdr: [18366] CAM 2: Aston Module 1.0300, 01, > 0100, 0100 > > > I came back once more under 1.4.7 and the second case always runs OK. I'm not quite sure what you mean with "first" and "second" case. What's the difference between these two cases? You could try changing #define MODULE_CHECK_INTERVAL 500 // ms to a higher value (like 1000 or so). Klaus _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
