[vdr] timers issue

Cristiano Bozzi c.bozzi at nextworks.it
Fri Feb 8 12:21:17 CET 2008


Hi all,
I would need your help for a strange problem :-(

I have a gentoo client-server VDR architecture 
server side: only a PVR150 card (no DVB, only analog channels), VDR 1.4.3, 
pvrinput-1.0.0, xine 0.7.9.
client side: VDR xine-lib-1.1.2_pre20060328.

this is an example of my channels.conf:
COMPOSITE 1:100:C23D12:C:0:301:300:305:A1:64001:0:0:0
ANALOG D:175250:C12D12:C:0:301:300:305:A1:64002:0:0:0
ANALOG H2:224250:C12D12:C:0:301:300:305:A1:64003:0:0:0
ANALOG 21:471250:C12D12:C:0:301:300:305:A1:64004:0:0:0
ANALOG 22:479250:C12D12:C:0:301:300:305:A1:64005:0:0:0
ANALOG 23:487250:C12D12:C:0:301:300:305:A1:64006:0:0:0
ANALOG 24:495250:C12D12:C:0:301:300:305:A1:64007:0:0:0
ANALOG 26:511250:C12D12:C:0:301:300:305:A1:64008:0:0:0

All the sistem work well except the recordings part.

if I try to set a timer or to start an istant recording on the COMPOSITE 1 
channel (in any position of the channels.conf) it works.
If I try to set a timer or an istant recording on a different ANALOG channel 
the screen show me the "NO SIGNAL black screen" with a continuos "channel not 
available" message. 
I can't see any live streaming image during the record time but, at the end of 
the timer, live tv return ok and the recording has been completed correctly 
(replay is ok)

The log file show me that, during the recording time, VDR is trying to change 
channel:

Feb  7 10:29:56 192.168.33.136 LiveServer-203401 vdr: [6895] switching device 
2 to channel 2
Feb  7 10:29:56 192.168.33.136 LiveServer-203401 vdr: [6895] timer 1 (2 
1030-1032 'ANALOG D') start
Feb  7 10:29:56 192.168.33.136 LiveServer-203401 vdr: [6895] waiting for EPG 
info...
Feb  7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] no EPG info 
available
Feb  7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] 
executing '/usr/lib/vdr/bin/vdrrecord-gate.sh 
before "/mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec"'
Feb  7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] 
record /mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec
Feb  7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] creating 
directory /mnt/vdr/video/ANALOG_D
Feb  7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] creating 
directory /mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec
Feb  7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [6895] recording 
to '/mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec/001.vdr'
Feb  7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [32065] file writer 
thread started (pid=32065, tid=32065)
Feb  7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [32066] recording thread 
started (pid=32066, tid=32066)
Feb  7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [32067] receiver on 
device 6 thread started (pid=32067, tid=32067)
Feb  7 10:30:02 192.168.33.136 LiveServer-203401 vdr: [6895] switching to 
channel 3
Feb  7 10:30:02 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not 
available!
Feb  7 10:30:02 192.168.33.136 LiveServer-203401 vdr: [32068] Text2Skin: 
message display update thread started (pid=32068, tid=32068)
Feb  7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [32068] Text2Skin: 
message display update thread ended (pid=32068, tid=32068)
Feb  7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [6895] switching to 
channel 2
Feb  7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not 
available!
Feb  7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [32069] Text2Skin: 
message display update thread started (pid=32069, tid=32069)
Feb  7 10:30:06 192.168.33.136 LiveServer-203401 vdr: [32069] Text2Skin: 
message display update thread ended (pid=32069, tid=32069)
Feb  7 10:30:06 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel 
not available!
Feb  7 10:30:06 192.168.33.136 LiveServer-203401 vdr: [32072] Text2Skin: 
message display update thread started (pid=32072, tid=32072)
Feb  7 10:30:08 192.168.33.136 LiveServer-203401 vdr: [32072] Text2Skin: 
message display update thread ended (pid=32072, tid=32072)
Feb  7 10:30:08 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel 
not available!
Feb  7 10:30:08 192.168.33.136 LiveServer-203401 vdr: [32073] Text2Skin: 
message display update thread started (pid=32073, tid=32073)
Feb  7 10:30:10 192.168.33.136 LiveServer-203401 vdr: [32073] Text2Skin: 
message display update thread ended (pid=32073, tid=32073)
Feb  7 10:30:21 192.168.33.136 LiveServer-203401 vdr: [6895] switching to 
channel 3
Feb  7 10:30:21 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not 
available!
Feb  7 10:30:21 192.168.33.136 LiveServer-203401 vdr: [32100] Text2Skin: 
message display update thread started (pid=32100, tid=32100)
Feb  7 10:30:23 192.168.33.136 LiveServer-203401 vdr: [32100] Text2Skin: 
message display update thread ended (pid=32100, tid=32100)
Feb  7 10:30:23 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel 
not available!
Feb  7 10:30:23 192.168.33.136 LiveServer-203401 vdr: [32101] Text2Skin: 
message display update thread started (pid=32101, tid=32101)
Feb  7 10:30:25 192.168.33.136 LiveServer-203401 vdr: [32101] Text2Skin: 
message display update thread ended (pid=32101, tid=32101)
Feb  7 10:30:25 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel 
not available!
Feb  7 10:30:25 192.168.33.136 LiveServer-203401 vdr: [32114] Text2Skin: 
message display update thread started (pid=32114, tid=32114)
Feb  7 10:30:27 192.168.33.136 LiveServer-203401 vdr: [32114] Text2Skin: 
message display update thread ended (pid=32114, tid=32114)
Feb  7 10:30:38 192.168.33.136 LiveServer-203401 vdr: [6895] switching to 
channel 3
Feb  7 10:30:38 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not 
available!
Feb  7 10:30:38 192.168.33.136 LiveServer-203401 vdr: [32129] Text2Skin: 
message display update thread started (pid=32129, tid=32129)

any ideas? 
  
thanks in advance
Cristiano


   



More information about the vdr mailing list