[mythtv-users] MVPMC

[Nick Craig-Wood]

On Thu, Jan 19, 2006 at 10:42:48AM +0000, Mike Richardson wrote:
> On Tue, Jan 17, 2006 at 10:24:02AM +0000, Nick Craig-Wood wrote:
> > I have all the symptoms you have above, except on CH4 (and CH5 too I
> > think).  I'd be interested if you could try skipping on a CH4
> > recording.  That works absolutely perfectly here.
> 
> Tried it and it still suffers the same problem. However I tried it on a
> non-DVB recording and it worked fine. 

Interesting.

> Tried the tzap stuff and I get lines like this:
> 
> status 1f | signal 002a | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> 
> But I'm not sure how to interpret it, or whether I should have something
> like dvbstream running simultaneously. 

Thats a perfect reception you posted!  The most useful data is
FE_HAS_LOCK - you need that otherwise no picture at all.  "ber" counts
the number of corrected bit errors per second.  This can be up to
about 0x1000 and everything still be fine.  "unc" is uncorrected
errors.  More than a few of these per minute will annoy you with
crackles in the audio and splodge in the video.

BTW you can use "femon" instead of tzap while mythtv is running.

Here is my output from "five" which is about as bad as you'd want to go

status 1f | signal d0d0 | snr fdfd | ber 0000267a | unc 00000000 | FE_HAS_LOCK
status 1f | signal d0d0 | snr fdfd | ber 000026b0 | unc 00000000 | FE_HAS_LOCK
status 1f | signal d0d0 | snr fdfd | ber 00002742 | unc 00000000 | FE_HAS_LOCK
status 1f | signal d0d0 | snr fdfd | ber 00002556 | unc 00000000 | FE_HAS_LOCK
status 1f | signal d1d1 | snr fdfd | ber 000025c0 | unc 00000000 | FE_HAS_LOCK

-- 
Nick Craig-Wood <nick at craig-wood.com> -- http://www.craig-wood.com/nick