[vdr] Re: unknwon picture type / error in data stream

["Christian Jacobsen" <christian.jacobsen@stageholding.de>]

Hallo,

>Usually this kind of error occurres if the recording is broken due to 
>ring buffer overflows or bad signal quality. If this happened there 
>should be some error messages in the syslog while recording:
>- ring buffer overflow

when reading this thread i thought I was lucky not to have this problem.
But as I came home yesterday I found that the bug hit me too :( 
Two recordings made yesterday was broken.

I can't remeber that I had any broken recordings before (except for other
reasons), but there was several entries in the syslogs. 

The first one (a singel entry) I had on the _25. Nov 2002_ !!! (don't have
any older syslogs)
After that I had about 6 more days with entires. I can provide the exact
dates/numbers if needed !

I also found several entries with ringbuffer overflow - but I did not
notice that in the logs for yesterday when this problem arised.

I tried doing a recording on the system as it was still running and that
one was broken too. After reloading DVB driver and VDR everything was OK.
The problem did not arise after running for long time tough ! The system
was started by nvram before doing the first recording so it was only
running for about 5 min. !

For a long time I had 1 DVB-s and 1 Nova-s but then decided to buy a
second DVB-s (rev. 1.6). Unfortunatly my old DVB-s then broke and I kept
on using the nova. The second DVB-s (rev. 1.3) was reinserted on thursday
as Second card. I am not perfectly sure but could it be that it has
something to do with the Rev. ? or only appearing on Full DVB cards ? 

What cards do you have as first and Second ?

My first is a Rev. 1.6 and the Second is a Rev. 1.3


>Same here, but I don't think it's a DVB driver problem. Since it does
>not occur on all systems, I believe that it is a hardware dependant PCI
>timing problem.


My system is a P3 933 with Intel Chipset (i810 i think) and latency timer
is set to 128 (you have to do that after loading the driver as it sets it
to 64) So it seems to be chipset independant.


>I don't think so. There was no problem upto about version 1.21 of the
>vdr (and the driver used for it, of course). I didn't change anything in
>the hardware setup, the linux kernel etc. and had absolutely no 
>glitches while recording before. My wife suspects, it occurs with 
>a very high chance, when doing two recording at the same time. 
>Both recordings used a different transponder.


The system was doing the two recordings after each other so on my system
it has nothing to do with recording on both cards. And I have entries from
before 1.2.1 so this might have been there for some time !

Greetings
Christian Jacobsen



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