[dvblast-devel] DVR_BUFFER_SIZE issue
Christophe Massiot
cmassiot at openheadend.tv
Thu Jan 26 22:40:45 CET 2012
Le 25 janv. 2012 à 09:42, Richard Hemzal a écrit :
> I have met issue that getting message from dvblast
>
> error: couldn't read from DVR device (Value too large for defined data type)
>
> in some cases.
> It looks that this message I am getting when szstem has some filesystem activity and it is probbaly related also with driver of
> card, in my case TBS6280. I also cannot exclude that this can affect usage of traffic control rules. In fact problem happens not
> each time, but in same system within few minutes will apear.
>
> Solution, or workaround, is to expand DVR_BUFFER_SIZE in dvb.c
Another possible solution would be to raise DVBlast's priority with nice or schedtool.
> originaly
> #define DVR_BUFFER_SIZE 40*188*1024 /* bytes */
> must change into
> #define DVR_BUFFER_SIZE 200*188*1024 /* bytes */
>
> I can say that also value 100*188*1024 not enough.
>
> Should we do this value controllable from command line?
Do you know if this value as an influence on the latency ? Actually I thought until now that is was of no use at all (wasn't connected to anything behind), but maybe it depends on the driver.
More information about the dvblast-devel
mailing list