Hallo,
On seldom occations I still (again) get the VDSB error :(
This time I saw some cVideoRepacker infos in the Syslog that might help clear up some things !? See attached logfile.
Unfortunatly I first saw this error yesterday evening and already had deleted the recording (if that would be of any use).
System : Suse 9.1 Vanilla Kernel 2.6.11.7
2 x DVB-s (rev. 1.6-4mb + 1.3) vdr-1.3.29 with several patches and several plugins. dvb-kernel-20050826 dvb-kernel-20050324 fw-261e to 2620
Here a grep "video data stream broken" on all syslogs of this year - you see it did not happen between February and June (added the vdr version used at that time) :
Jan 27 06:58:55 vdr vdr[12622]: ERROR: video data stream broken vdr-1.3.17 or 18 Jan 27 06:59:42 vdr vdr[14387]: ERROR: video data stream broken Jan 29 00:13:42 vdr vdr[22619]: ERROR: video data stream broken Feb 26 21:55:44 vdr vdr[27103]: ERROR: video data stream broken vdr-1.3.20 or 21 Jun 3 22:02:13 vdr vdr[20782]: ERROR: video data stream broken vdr-1.3.25 (since 2. jun) Jul 11 18:54:14 vdr vdr[8022]: ERROR: video data stream broken Jul 22 10:28:31 vdr vdr[27589]: ERROR: video data stream broken vdr-1.3.27 Jul 29 19:43:57 vdr vdr[25319]: ERROR: video data stream broken Jul 29 19:51:36 vdr vdr[5760]: ERROR: video data stream broken Aug 4 18:43:32 vdr vdr[16205]: ERROR: video data stream broken Aug 8 22:30:23 vdr vdr[27564]: ERROR: video data stream broken Aug 8 22:30:54 vdr vdr[27564]: ERROR: video data stream broken Aug 8 22:31:25 vdr vdr[27564]: ERROR: video data stream broken Aug 10 00:31:38 vdr vdr[31800]: ERROR: video data stream broken Aug 10 00:32:09 vdr vdr[31800]: ERROR: video data stream broken Aug 21 20:17:09 vdr vdr[9679]: ERROR: video data stream broken vdr-1.3.29 Aug 28 00:44:23 vdr vdr[31163]: ERROR: video data stream broken vdr-1.3.30 Sep 7 18:43:36 vdr vdr[18036]: ERROR: video data stream broken vdr-1.3.29
And I did some research ;)
Kernel used : 2.6.10-rc1 since 15. Dec. 2004 2.6.10 (final) since 2. feb 2.6.11.8 since 8. May.
Firmware used : 261c(+261d shortly) - used since vdr-1.3.17 261d - used since vdr-1.3.19 261e-1.4 - Around 31. may I (togehter with vdr-1.3.24) started using the New Firmware (1.4 !? IIRC the first of the 261e - from 26. may) that no longer needed FW_NEEDS_BUFFER_RESERVE_FOR_AC3. 261f - might be that I tried that since 22. august - can't say for sure. 2620 - since 29. Aug. - with vdr-1.3.30 + 29
Here a list of the DVD drivers I used, I allways started using them on the Day that I downloaded them : Up till vdr-1.3.17 - dvb-kernel-20041221 vdr-1.3.19 - dvb-kernel-20050118 vdr-1.3.23 - dvb-cvs-kernel-20050324) vdr-1.3.25 - dvb-kernel-20050617 vdr-1.3.27 (20. June) - back to dvb-kernel-20050324 (more stable) vdr-1.3.29 - dvb-kernel-20050826 (together with FW 2620)
So if I see this right it comes down to that it probably is caused by the New Firmware or maybe something that was changed in VDR >= 1.3.25 ?
Greetings Christian Jacobsen
Hi,
christian jacobsen wrote:
2620 - since 29. Aug. - with vdr-1.3.30 + 29
Here a list of the DVD drivers I used, I allways started using them on the Day that I downloaded them : Up till vdr-1.3.17 - dvb-kernel-20041221 vdr-1.3.19 - dvb-kernel-20050118 vdr-1.3.23 - dvb-cvs-kernel-20050324) vdr-1.3.25 - dvb-kernel-20050617 vdr-1.3.27 (20. June) - back to dvb-kernel-20050324 (more stable) vdr-1.3.29 - dvb-kernel-20050826 (together with FW 2620)
So if I see this right it comes down to that it probably is caused by the New Firmware or maybe something that was changed in VDR >= 1.3.25 ?
cVideoRepacker was introduced. But it was wrong to reset it's scanner and drop any buffered data when it discovered a system start code. This resulted in putting incomplete PES packets into result buffer and later, it was possible that cRemux::Get() couldn't return any remaining data of result buffer. The result was that the receiver's ringbuffer filled up and caused an overflow as the recording thread could no longer feed cRemux due to the almost full result buffer. And finally, the recording thread caused an emergency exit as it didn't see any further data for 30 seconds.
Since VDR-1.3.25 there have been many fixes and improvements. The attached files will soon be released in VDR-1.3.32.
A further change happend in VDR-1.3.31: waiting for the tuner to get locked on the signal before attaching the receiver was removed. Several versions ago, this waiting was introduced to fix the VDSB error. But it was removed now as no driver should need this waiting besides it is buggy.
Bye.