On 05/18/07 01:24, Petri Helin wrote:
> Klaus Schmidinger wrote:
>> How many DVB devices does your system have?
>> Are you sure there was one free when that timer should have been
>> recorded?
>> What was the priority of that timer?
>
> I tried to recreate the situation by disabling the decrypting for the
> subscription channels. The channel the recording was supposed the take
> place on is encrypted and I though that maybe the decrypting didn't work
> for some reason and therefore the channel was unavailable. I just tested
> this and got the following log entries:
>
> May 18 02:02:56 x vdr: [32337] EPGSearch: timer thread started
> (pid=32258, tid=32337)
> May 18 02:02:57 x vdr: [32258] connect from 127.0.0.1, port 39440 -
> accepted
> May 18 02:02:57 x vdr: [32258] timer 25 (11 0205-0215 'Magnum .44') added
> May 18 02:02:57 x vdr: [32258] closing SVDRP connection
> May 18 02:02:57 x vdr: [32337] EPGSearch: timer thread ended (pid=32258,
> tid=32337)
> May 18 02:03:02 x vdr: [32258] timer 25 (11 0205-0215 'Magnum .44') set
> to event Pe 18.05.2007 01:20-03:20 'Magnum .44'
> May 18 02:04:03 x vdr: [32258] switching device 3 to channel 11
>
> So vdr tried to change to the channel, but couldn't, and therefore the
> recording could be started. Shouldn't this create some entries in the
> log? Like "unable to start recording" or something?
>
> After that I tried to manually wswitch to the channel and got these log
> entries (these entries follow immediately the ones above):
>
> May 18 02:06:52 x vdr: [32258] switching to channel 11
> May 18 02:06:52 x vdr: [32334] transfer thread ended (pid=32258, tid=32334)
> May 18 02:06:52 x vdr: [32258] buffer stats: 87608 (4%) used
> May 18 02:06:52 x vdr: [32258] info: Kanava ei ole käytettävissä!
> May 18 02:06:57 x vdr: [32258] info: Kanavan vaihtaminen ei mahdollista!
> May 18 02:07:02 x vdr: [32258] switching to channel 1
> May 18 02:07:02 x vdr: [32258] buffer stats: 0 (0%) used
> May 18 02:07:02 x vdr: [32397] transfer thread started (pid=32258,
> tid=32397)
> May 18 02:07:02 x vdr: [32258] buffer stats: 0 (0%) used
> May 18 02:07:02 x vdr: [32258] max. latency time 10 seconds
> May 18 02:07:02 x vdr: [32258] switching to channel 11
> May 18 02:07:02 x vdr: [32397] transfer thread ended (pid=32258, tid=32397)
> May 18 02:07:02 x vdr: [32258] buffer stats: 0 (0%) used
> May 18 02:07:02 x vdr: [32258] info: Kanava ei ole käytettävissä!
> May 18 02:07:02 x vdr: [32258] connect from 127.0.0.1, port 60450 -
> accepted
> May 18 02:07:02 x vdr: [32258] closing SVDRP connection
> May 18 02:07:06 x vdr: [32258] info: VPS-tallennus on alkamassa!
> May 18 02:07:13 x vdr: [32258] switching to channel 1
> May 18 02:07:13 x vdr: [32258] buffer stats: 0 (0%) used
> May 18 02:07:13 x vdr: [32400] transfer thread started (pid=32258,
> tid=32400)
> May 18 02:07:13 x vdr: [32258] buffer stats: 0 (0%) used
> May 18 02:07:15 x vdr: [32400] setting audio track to 1 (0)
>
>
> So now there is additional entries telling that the channel is not
> available ("Kanava ei ole käytettävissä!"). But what is that strange
> entry about VPS recording staring ("VPS-tallennus on alkamassa!")? I
> didn't create a VPS timer...
The "Upcoming VPS recording!" message is probably actually wrong, since
your timer doesn't use VPS. Originally switching to the transponder early
was only done for VPS recordings, but beginning with version 1.4.0-3 this
is also done for non-VPS timers, so that the EPG data is up-to-date when
the timer actually starts. I'll change the message accordingly, so in your
case it should just say "Upcoming recording".
As for the actual problem: I assume you're using a heavily patched version
of VDR. Can you try to recreate the situation with an unpatched VDR?
And please switch the OSD language to English while doing so, so that I can
understand the log messages ;-)
Klaus
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
