Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: cTS2PES got NN TS errors [WAS: Re: Re: switching to channel N (once per second?)]



On Monday 09 June 2003 18:16, Klaus Schmidinger wrote:
> Stefan Lucke wrote:
> > 
> > On Monday 09 June 2003 15:54, Klaus Schmidinger wrote:
> > > Stefan Lucke wrote:
> > > >

[..]

> > > > Jun  9 09:21:45 bodega1 vdr[940]: receiver thread ended on device 6 (pid=940)
> > > > Jun  9 09:21:45 bodega1 vdr[909]: cTS2PES got 30 TS errors, 224 TS continuity errors
> > > > Jun  9 09:21:45 bodega1 vdr[909]: cTS2PES got 1 TS errors, 139 TS continuity errors
> > >

[..]

> All I can say is that the VDR version 1.2.1 and the suggested driver
> from the VDR download area work fine for me. I have no idea what's
> going wrong at your side. I can only repeat that you absolutely, positively
> have to make sure that hw_sections=1. With hw_sections=0 I had completely

hw_sections=X is related to full featured cards right ? So this does not
apply to my configuration. TWO Nova-s.
I did an other test starting a recording (device 1) on the server,
switched to pro7, sat1 on the client (server device 2 was used)
and every thing is fine ;-) no errors on both devices.
After recording finished on dev1, live view of pro7 (now on dev1) is
jerkey again. :-(
Checked with vdr 1.1.30 again live view of pro7 (channel 7) is ok on dev??

client:

Jun 10 23:12:59 bodega1 vdr[538]: switching to channel 7
Jun 10 23:12:59 bodega1 vdr[559]: transfer thread ended (pid=559)
Jun 10 23:13:00 bodega1 vdr[561]: Streamdev: Couldn't read video data: Bad file descriptor
Jun 10 23:13:00 bodega1 vdr[561]: Streamdev: Receiver thread ended (pid = 561)
Jun 10 23:13:00 bodega1 vdr[560]: receiver thread ended on device 6 (pid=560)
Jun 10 23:13:00 bodega1 vdr[538]: cTS2PES got 0 TS errors, 2 TS continuity errors
Jun 10 23:13:00 bodega1 vdr[538]: cTS2PES got 0 TS errors, 1 TS continuity errors
Jun 10 23:13:00 bodega1 vdr[538]: buffer stats: 112272 (10%) used
Jun 10 23:13:00 bodega1 vdr[564]: transfer thread started (pid=564)
Jun 10 23:13:00 bodega1 vdr[565]: receiver thread started on device 6 (pid=565)
Jun 10 23:13:00 bodega1 vdr[566]: Streamdev: Receiver thread started (pid = 566)

server:
Jun 10 23:13:00 farpoint vdr[4686]: Streamdev: Transceiver thread ended
Jun 10 23:13:00 farpoint vdr[4687]: receiver thread ended on device 2 (pid=4687)
Jun 10 23:13:00 farpoint vdr[4679]: buffer stats: 51888 (4%) used
Jun 10 23:13:00 farpoint vdr[4679]: Streamdev: Setting data connection to 192.168.192.129:32774
Jun 10 23:13:00 farpoint vdr[4689]: Streamdev: Transceiver thread started (pid=4689)
Jun 10 23:13:00 farpoint vdr[4690]: receiver thread started on device 2 (pid=4690)
Jun 10 23:13:00 farpoint vdr[4671]: switching to channel 1
Jun 10 23:13:31 farpoint last message repeated 30 times


Any hints to dig further are welcome (driver, hardware).


Stefan Lucke


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.



Home | Main Index | Thread Index