[vdr] Re: since vdr-1.0.x a lot of restarts in record mode

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Otto Felbecker wrote:
> 
> Klaus Schmidinger schrieb:
> 
> > Here's an updated compilation of the reports on this subjecFinally, I have gone through
> > the 'diff' between version 1.0.0pre4 and 1.0.0pre5
> > of VDR/dvbapi.c and the only difference that is in the area of the "data stream
> > broken" error message is the handling of the cFile::FileReady() call. In version
> > 1.0.0pre4 this function was simply called, while in 1.0.0pre5 the return value
> > of this call is checked and a read() is only done if it returns 'true'. Although
> > I hardly believe that this would cause the observed problem (since the timeout
> > for the "video data stream broken" error is 30 seconds!), people observing this
> > problem might want to try the cRecordBuffer::Input() function from version 1.0.0pre4
> > with version 1.0.0pre5. For your convenience here's a small patch that, if applied to
> > dvbapi.c of version 1.0.0pre5, will revert the cRecordBuffer::Input() function to
> > the way it was in version 1.0.0pre4:
> >
> > ---------------------------------------------------------------
> > --- dvbapi.c    2002/03/29 11:32:47
> > +++ dvbapi.c    2002/03/16 14:20:47
> > @@ -525,7 +527,6 @@
> >    time_t t = time(NULL);
> >    recording = true;
> >    for (;;) {
> > -      if (cFile::FileReady(videoDev, 100)) {
> >           int r = read(videoDev, b, sizeof(b));
> >           if (r > 0) {
> >              uchar *p = b;
> > @@ -546,12 +547,12 @@
> >                    }
> >                 }
> >              }
> > -         }
> >        if (time(NULL) - t > MAXBROKENTIMEOUT) {
> >           esyslog(LOG_ERR, "ERROR: video data stream broken");
> >           cThread::EmergencyExit(true);
> >           t = time(NULL);
> >           }
> > +      cFile::FileReady(videoDev, 100);
> >        if (!recording)
> >           break;
> >        }
> >
> > ---------------------------------------------------------------
> >
> > Please let us know if this changes anything.
> >
> > Klaus
> >
> 
> Hallo Klaus,
> 
> after the patch to pre5 no more restarts. But strange messages like pre1 to pre4:
> 
> May 20 12:30:34 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:30:34 vdrR vdr[707]: ERROR: skipped 64 byte to sync on TS packet
> May 20 12:30:44 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:30:44 vdrR vdr[707]: ERROR: skipped 168 byte to sync on TS packet
> May 20 12:31:14 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:31:14 vdrR vdr[707]: ERROR: skipped 92 byte to sync on TS packet
> May 20 12:31:29 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:31:29 vdrR vdr[707]: ERROR: skipped 64 byte to sync on TS packet
> May 20 12:31:44 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:31:44 vdrR vdr[707]: ERROR: skipped 120 byte to sync on TS packet
> May 20 12:32:09 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:32:09 vdrR vdr[707]: ERROR: skipped 64 byte to sync on TS packet
> May 20 12:32:14 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:32:14 vdrR vdr[707]: ERROR: skipped 64 byte to sync on TS packet
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 76%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 78%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 79%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 80%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 81%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 83%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 84%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 86%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 88%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 89%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 91%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 92%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 94%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 95%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 97%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 99%
> May 20 12:32:21 vdrR vdr[708]: buffer usage: 100%
> May 20 12:33:12 vdrR vdr[708]: ERROR (dvbapi.c,541): DVB driver buffer overflow
> May 20 12:33:12 vdrR vdr[707]: ERROR: skipped 128 byte to sync on TS packet

There must still be something wrong on your system.
Are you sure your signal is strong enough? With DVB it may take a while
before you see actual distortions, but for a program parsing the data
it may already be faulty.

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________