[linux-dvb] Re: [PATCH] Small fix for stv0299.c

[Gavin Hamill <gdh@acentral.co.uk>]

On Wed, 2003-11-12 at 16:45, Andrew de Quincey wrote:
> > >
> > FE_READ_BER is more useful for displaying a "signal quality" status
> > bar in a GUI. FE_READ_UNCORRECTED_BLOCKS is not suitable for that
> > because it stays at 0 until the signal is bad enough and then jumps
> > between 0 and some small number.
> >
> > Too bad the stv0299 cannot do both at the same time.
> 
> uncorrected blocks is also very useful for diagnosing problems in transmission 
> equipment, (e.g. logging for a long period to look for periodic 
> corruption)... maybe we need a way to choose which one should be used... 
> perhaps a module parameter?

Just a thought...

Surely one dictates (or at least influences) the other?

I know from my own limited experiences with DVB-T in the UK that you can
have a 'Verror' of as high as 15000 and still have a solid picture,
although this is obviously not a desirable working solution.

Perhaps have a threshold at which the error reporting changes from BER
(Verror) to UNC_blocks..

Or, looking at it another way, how fast (and reliably) can the stv0299
switch between sampling these two values? If it's possible every 5
seconds or less then it might be feasible to still implement both
values?

Just thoughts on a boring Thursday.


What, it's not even Thursday yet? <sigh>

Cheers,
Gavin.



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