There have been several reports that VDR stops recording after
the driver reports an EBUFFEROVERFLOW (which is listed in the log
file as "Unknown error 769" since EBUFFEROVERFLOW is only defined
inside the driver's code).
Taking a close look at DVB/driver/dmxdev.c I saw that the 'buffer.error'
is initialized to '0' in DmxDevBufferInit(), and later set to various
error codes - but NEVER reset to '0'. Apparently this causes the driver
to no longer deliver (useful) data.
Am I missing something?
Shouldn't buffer.error be reset at some point?
Or must the application (VDR) do something special after receiving
EBUFFEROVERFLOW to reset that error condition?
Any hints would be greatly appreciated.
Klaus
--
_______________________________________________________________
Klaus Schmidinger Phone: +49-8635-6989-10
CadSoft Computer GmbH Fax: +49-8635-6989-40
Hofmark 2 Email: [EMAIL PROTECTED]
D-84568 Pleiskirchen, Germany URL: www.cadsoft.de
_______________________________________________________________
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
