Re: [vdr] No data in 8 seconds, queuing no signal image

2013-02-27 Thread Lars Hanisch
Am 27.02.2013 16:23, schrieb Peter Münster:
 Hi,
 
 Sometimes, when starting VDR, I get this message:
 [input_vdr] No data in 8 seconds, queuing no signal image
 And no video.
 
 When switching channels of the same transponder, nothing happens. But
 switching to a channel of another transponder (channel 7), video comes
 back.
 
 How could I avoid this problem please, when VDR starts automatically to
 start a recording?

 I don't know if it works, but you can configure vdr to start with always the 
same channel (which you'll never use for a
recording) so that it has to switch explicitly when starting the recording.

Lars.

 
 Here some log messages:
 
 --8---cut here---start-8---
 Feb 25 21:00:03 media vdr: [2916] [input_vdr] No data in 8 seconds, queuing 
 no signal image
 Feb 26 15:14:17 media vdr: [0] [xine..put] cXinelibOsd::CanHandleAreas(): 
 Device does not support ARGB
 Feb 26 15:14:18 media vdr: [0] switching to channel 1
 Feb 26 15:14:18 media vdr: [0] [input_vdr] vdr_flush_engine: playback is 
 paused 0
 Feb 26 15:14:18 media vdr: [11133] TS buffer on device 2 thread ended 
 (pid=0, tid=11133)
 Feb 26 15:14:18 media vdr: [11132] buffer stats: 188 (0%) used
 Feb 26 15:14:18 media vdr: [11132] receiver on device 2 thread ended 
 (pid=0, tid=11132)
 Feb 26 15:14:18 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer
 Feb 26 15:14:18 media vdr: [11145] receiver on device 2 thread started 
 (pid=0, tid=11145, prio=high)
 Feb 26 15:14:18 media vdr: [11146] TS buffer on device 2 thread started 
 (pid=0, tid=11146, prio=high)
 Feb 26 15:14:22 media vdr: [0] switching to channel 2
 Feb 26 15:14:22 media vdr: [0] [input_vdr] vdr_flush_engine: playback is 
 paused 0
 Feb 26 15:14:22 media vdr: [11146] TS buffer on device 2 thread ended 
 (pid=0, tid=11146)
 Feb 26 15:14:22 media vdr: [11145] buffer stats: 0 (0%) used
 Feb 26 15:14:22 media vdr: [11145] receiver on device 2 thread ended 
 (pid=0, tid=11145)
 Feb 26 15:14:22 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer
 Feb 26 15:14:22 media vdr: [11147] receiver on device 2 thread started 
 (pid=0, tid=11147, prio=high)
 Feb 26 15:14:22 media vdr: [11148] TS buffer on device 2 thread started 
 (pid=0, tid=11148, prio=high)
 Feb 26 15:14:27 media vdr: [0] switching to channel 3
 Feb 26 15:14:27 media vdr: [0] [input_vdr] vdr_flush_engine: playback is 
 paused 0
 Feb 26 15:14:27 media vdr: [11148] TS buffer on device 2 thread ended 
 (pid=0, tid=11148)
 Feb 26 15:14:27 media vdr: [11147] buffer stats: 0 (0%) used
 Feb 26 15:14:27 media vdr: [11147] receiver on device 2 thread ended 
 (pid=0, tid=11147)
 Feb 26 15:14:27 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer
 Feb 26 15:14:27 media vdr: [11149] receiver on device 2 thread started 
 (pid=0, tid=11149, prio=high)
 Feb 26 15:14:27 media vdr: [11150] TS buffer on device 2 thread started 
 (pid=0, tid=11150, prio=high)
 Feb 26 15:14:30 media vdr: [0] switching to channel 4
 Feb 26 15:14:30 media vdr: [0] [input_vdr] vdr_flush_engine: playback is 
 paused 0
 Feb 26 15:14:30 media vdr: [11150] TS buffer on device 2 thread ended 
 (pid=0, tid=11150)
 Feb 26 15:14:30 media vdr: [11149] buffer stats: 188 (0%) used
 Feb 26 15:14:30 media vdr: [11149] receiver on device 2 thread ended 
 (pid=0, tid=11149)
 Feb 26 15:14:30 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer
 Feb 26 15:14:30 media vdr: [11151] receiver on device 2 thread started 
 (pid=0, tid=11151, prio=high)
 Feb 26 15:14:30 media vdr: [11152] TS buffer on device 2 thread started 
 (pid=0, tid=11152, prio=high)
 Feb 26 15:14:32 media vdr: [0] switching to channel 5
 Feb 26 15:14:32 media vdr: [0] [input_vdr] vdr_flush_engine: playback is 
 paused 0
 Feb 26 15:14:32 media vdr: [11152] TS buffer on device 2 thread ended 
 (pid=0, tid=11152)
 Feb 26 15:14:32 media vdr: [11151] buffer stats: 0 (0%) used
 Feb 26 15:14:32 media vdr: [11151] receiver on device 2 thread ended 
 (pid=0, tid=11151)
 Feb 26 15:14:32 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer
 Feb 26 15:14:32 media vdr: [11153] receiver on device 2 thread started 
 (pid=0, tid=11153, prio=high)
 Feb 26 15:14:32 media vdr: [11154] TS buffer on device 2 thread started 
 (pid=0, tid=11154, prio=high)
 Feb 26 15:14:34 media vdr: [0] switching to channel 6
 Feb 26 15:14:34 media vdr: [0] [input_vdr] vdr_flush_engine: playback is 
 paused 0
 Feb 26 15:14:34 media vdr: [11154] TS buffer on device 2 thread ended 
 (pid=0, tid=11154)
 Feb 26 15:14:34 media vdr: [11153] buffer stats: 0 (0%) used
 Feb 26 15:14:34 media vdr: [11153] receiver on device 2 thread ended 
 (pid=0, tid=11153)
 Feb 26 15:14:34 media vdr: [11129] [demux_vdr] PMT changed, resetting demuxer
 Feb 26 15:14:34 media vdr: [11155] receiver on device 2 thread started 
 (pid=0, tid=11155, 

Re: [vdr] No data in 8 seconds, queuing no signal image

2013-02-27 Thread Bernard Jaulin
Hi Peter,

Did you change your VDR release ?

Have you the same issue with SoftHDdevice ?

Cheers,

Bernard.


2013/2/27 Lars Hanisch d...@flensrocker.de

 Am 27.02.2013 16:23, schrieb Peter Münster:
  Hi,
 
  Sometimes, when starting VDR, I get this message:
  [input_vdr] No data in 8 seconds, queuing no signal image
  And no video.
 
  When switching channels of the same transponder, nothing happens. But
  switching to a channel of another transponder (channel 7), video comes
  back.
 
  How could I avoid this problem please, when VDR starts automatically to
  start a recording?

  I don't know if it works, but you can configure vdr to start with always
 the same channel (which you'll never use for a
 recording) so that it has to switch explicitly when starting the recording.

 Lars.

 
  Here some log messages:
 
  --8---cut here---start-8---
  Feb 25 21:00:03 media vdr: [2916] [input_vdr] No data in 8 seconds,
 queuing no signal image
  Feb 26 15:14:17 media vdr: [0] [xine..put]
 cXinelibOsd::CanHandleAreas(): Device does not support ARGB
  Feb 26 15:14:18 media vdr: [0] switching to channel 1
  Feb 26 15:14:18 media vdr: [0] [input_vdr] vdr_flush_engine:
 playback is paused 0
  Feb 26 15:14:18 media vdr: [11133] TS buffer on device 2 thread ended
 (pid=0, tid=11133)
  Feb 26 15:14:18 media vdr: [11132] buffer stats: 188 (0%) used
  Feb 26 15:14:18 media vdr: [11132] receiver on device 2 thread ended
 (pid=0, tid=11132)
  Feb 26 15:14:18 media vdr: [11129] [demux_vdr] PMT changed, resetting
 demuxer
  Feb 26 15:14:18 media vdr: [11145] receiver on device 2 thread started
 (pid=0, tid=11145, prio=high)
  Feb 26 15:14:18 media vdr: [11146] TS buffer on device 2 thread started
 (pid=0, tid=11146, prio=high)
  Feb 26 15:14:22 media vdr: [0] switching to channel 2
  Feb 26 15:14:22 media vdr: [0] [input_vdr] vdr_flush_engine:
 playback is paused 0
  Feb 26 15:14:22 media vdr: [11146] TS buffer on device 2 thread ended
 (pid=0, tid=11146)
  Feb 26 15:14:22 media vdr: [11145] buffer stats: 0 (0%) used
  Feb 26 15:14:22 media vdr: [11145] receiver on device 2 thread ended
 (pid=0, tid=11145)
  Feb 26 15:14:22 media vdr: [11129] [demux_vdr] PMT changed, resetting
 demuxer
  Feb 26 15:14:22 media vdr: [11147] receiver on device 2 thread started
 (pid=0, tid=11147, prio=high)
  Feb 26 15:14:22 media vdr: [11148] TS buffer on device 2 thread started
 (pid=0, tid=11148, prio=high)
  Feb 26 15:14:27 media vdr: [0] switching to channel 3
  Feb 26 15:14:27 media vdr: [0] [input_vdr] vdr_flush_engine:
 playback is paused 0
  Feb 26 15:14:27 media vdr: [11148] TS buffer on device 2 thread ended
 (pid=0, tid=11148)
  Feb 26 15:14:27 media vdr: [11147] buffer stats: 0 (0%) used
  Feb 26 15:14:27 media vdr: [11147] receiver on device 2 thread ended
 (pid=0, tid=11147)
  Feb 26 15:14:27 media vdr: [11129] [demux_vdr] PMT changed, resetting
 demuxer
  Feb 26 15:14:27 media vdr: [11149] receiver on device 2 thread started
 (pid=0, tid=11149, prio=high)
  Feb 26 15:14:27 media vdr: [11150] TS buffer on device 2 thread started
 (pid=0, tid=11150, prio=high)
  Feb 26 15:14:30 media vdr: [0] switching to channel 4
  Feb 26 15:14:30 media vdr: [0] [input_vdr] vdr_flush_engine:
 playback is paused 0
  Feb 26 15:14:30 media vdr: [11150] TS buffer on device 2 thread ended
 (pid=0, tid=11150)
  Feb 26 15:14:30 media vdr: [11149] buffer stats: 188 (0%) used
  Feb 26 15:14:30 media vdr: [11149] receiver on device 2 thread ended
 (pid=0, tid=11149)
  Feb 26 15:14:30 media vdr: [11129] [demux_vdr] PMT changed, resetting
 demuxer
  Feb 26 15:14:30 media vdr: [11151] receiver on device 2 thread started
 (pid=0, tid=11151, prio=high)
  Feb 26 15:14:30 media vdr: [11152] TS buffer on device 2 thread started
 (pid=0, tid=11152, prio=high)
  Feb 26 15:14:32 media vdr: [0] switching to channel 5
  Feb 26 15:14:32 media vdr: [0] [input_vdr] vdr_flush_engine:
 playback is paused 0
  Feb 26 15:14:32 media vdr: [11152] TS buffer on device 2 thread ended
 (pid=0, tid=11152)
  Feb 26 15:14:32 media vdr: [11151] buffer stats: 0 (0%) used
  Feb 26 15:14:32 media vdr: [11151] receiver on device 2 thread ended
 (pid=0, tid=11151)
  Feb 26 15:14:32 media vdr: [11129] [demux_vdr] PMT changed, resetting
 demuxer
  Feb 26 15:14:32 media vdr: [11153] receiver on device 2 thread started
 (pid=0, tid=11153, prio=high)
  Feb 26 15:14:32 media vdr: [11154] TS buffer on device 2 thread started
 (pid=0, tid=11154, prio=high)
  Feb 26 15:14:34 media vdr: [0] switching to channel 6
  Feb 26 15:14:34 media vdr: [0] [input_vdr] vdr_flush_engine:
 playback is paused 0
  Feb 26 15:14:34 media vdr: [11154] TS buffer on device 2 thread ended
 (pid=0, tid=11154)
  Feb 26 15:14:34 media vdr: [11153] buffer stats: 0 (0%) used
  Feb 26 15:14:34 media vdr: [11153] receiver on device 2 thread ended
 

Re: [vdr] No data in 8 seconds, queuing no signal image

2013-02-27 Thread Peter Münster
On Wed, Feb 27 2013, Lars Hanisch wrote:

  I don't know if it works, but you can configure vdr to start with always the
 same channel (which you'll never use for a
 recording) so that it has to switch explicitly when starting the recording.

Yes, that should work. That's what I'll do, if there is no other
solution.

-- 
   Peter


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] No data in 8 seconds, queuing no signal image

2013-02-27 Thread Peter Münster
On Wed, Feb 27 2013, Bernard Jaulin wrote:

 Did you change your VDR release ?

Yes. Now it's 1.7.37 and before it was 1.2.6 (several years ago... ;)


 Have you the same issue with SoftHDdevice ?

I don't use this plugin, so I don't know.

-- 
   Peter


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr