Tvheadend

You upgraded from ? (version number)

Try increase buffer in the tuner setup.

Jaroslav Kysela wrote:

You upgraded from ? (version number)

Sorry for not supplying this info. I came from 4.0.5 (I am using the stable debian repository.)

Jaroslav Kysela wrote:

Try increase buffer in the tuner setup.

Increased it and did a restart. Am watching now. Initially after the start I had some errors while epgrab started. I'll report later about the progress.

Iam sorry for hijacking your ticket Karl, but i have seen similar problems with 1 of 3 hauppage dvb-s2 pci cards that i have.
Kysela mentioned this tuner buffer variable, i have been pussled about it for some time and wanted to know what this setting actualy is and what currently is the best setting to use.
PCI/x, usb and satip tuners do they have the same buffer value?

Raymond Paulsen wrote:

Iam sorry for hijacking your ticket Karl, but i have seen similar problems with 1 of 3 hauppage dvb-s2 pci cards that i have.
Kysela mentioned this tuner buffer variable, i have been pussled about it for some time and wanted to know what this setting actualy is and what currently is the best setting to use.
PCI/x, usb and satip tuners do they have the same buffer value?

Take a look at the help pages.

As mine says.

Skip Initial Bytes : If set, the first bytes from the MPEG-TS stream are discarded. It may be required for some drivers or hardware which do not flush completely the MPEG-TS buffers after a frequency/parameter change.

Input Buffer (Bytes) : By default, linuxdvb's input buffer is 18800 bytes long. The accepted range is 18800-1880000 bytes.

Werner Karl wrote:

Jaroslav Kysela wrote:

Try increase buffer in the tuner setup.

Increased it and did a restart. Am watching now. Initially after the start I had some errors while epgrab started. I'll report later about the progress.

For me, the EOVERFLOW has almost gone. I had increased the buffer from 18800 to 37600, i.e. double size. After almost one day without EOVERFLOW I had one today. Now I have increased to buffer to 65536 (64kB) and see how it goes.

@Raymond Paulsen: I don't know if different types of receivers need different buffer sizes. But you should definitely try with larger values. I suppose, this is not a buffer for the dvb data but for the control data. Thus, you don't have to fear an increase in latency. Anyone correct me if I'm wrong.

The value means the input buffer size in bytes for all incoming MPEG-TS data. I suggest to use value like 188000 or even more to flush the whole kernel buffer to the userspace when required. I increased the value to 188000 in the latest source tree for 4.1, too.

Jaroslav Kysela wrote:

The value means the input buffer size in bytes for all incoming MPEG-TS data. I suggest to use value like 188000 or even more to flush the whole kernel buffer to the userspace when required. I increased the value to 188000 in the latest source tree for 4.1, too.

Thank you for that info. Will increase to 188000 and see.