[mythtv-users] What does ATSC poor signal look like? or is thePCnot up to it?

Andre Newman mythtv-list at dinkum.org.uk
Thu Apr 16 20:33:01 UTC 2009


On 16 Apr 2009, at 19:26, Misty P wrote:
>
> I believe that's correct regarding unc, but don't quote me on it.   
> (It doesn't come with a man page -- garrrgh!)

Comes with a source page though ;-)

I think you've found it, it's poor signal.


status 1e | signal 7f64 | snr 116a | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 8acd | snr 12fa | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 6f98 | snr 0f41 | ber 00000000 | unc 00000098 |  
FE_HAS_LOCK
status 1e | signal 83df | snr 1207 | ber 00000000 | unc 00001c4c |  
FE_HAS_LOCK
status 1e | signal 8513 | snr 1231 | ber 00000000 | unc 000003ab |  
FE_HAS_LOCK
status 1e | signal 96ab | snr 1499 | ber 00000000 | unc 0000127b |  
FE_HAS_LOCK
status 1e | signal 8dac | snr 135e | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 9b18 | snr 1534 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal a4c8 | snr 1687 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal a137 | snr 15fc | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 8dc8 | snr 1362 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal a104 | snr 1603 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 8de3 | snr 13e2 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 9763 | snr 14b2 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 8628 | snr 1257 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal a137 | snr 160a | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 8704 | snr 1275 | ber 00000000 | unc 00000061 |  
FE_HAS_LOCK
status 1e | signal 9c43 | snr 155d | ber 00000000 | unc 00000033 |  
FE_HAS_LOCK
status 1e | signal 9c6e | snr 1563 | ber 00000000 | unc 00000033 |  
FE_HAS_LOCK
status 1e | signal 8bb2 | snr 1319 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1e | signal 8814 | snr 129a | ber 00000000 | unc 00000b6f |  
FE_HAS_LOCK
status 1e | signal 9a20 | snr 1512 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK

It does this every few minutes, approximately corresponding with the  
missing bits, I expect there's a significant streaming delay which  
would explain why it's not direct correlation.

I ran femon while it wasn't recording or viewing and it's behaving the  
same so I think it must be signal rather than any load related issues,  
doubtless that will show through when the signal strength and quality  
is sorted out :-P
>
> Don't know if the HVR-950 reports ber or not.  My Hauppauge 1250,  
> 1600, and 1800 all report both, so I would be surprised if the 950  
> didn't.  (Yes, I have and use all three with myth!)

Looks like it doesn't, can't imagine that a bunch of unc errors like  
that could result in a ber of 0.
>>
>
> Oh yeah, it's much easier in real time!  Besides, if you just look  
> at the resultant transport stream, all you know is that you lost  
> data.  You don't know *where* you lost that data.

Possibly even somewhere mid atlantic in my case :-)
>
> Femon is also really useful for playing around with antenna  
> positioning/aiming, since that's the next logical step if you find  
> you have signal degredation.

Time for that age old ritual of standing on one leg whilst waving an  
antenna around and trying not to fall off the kitchen stool!

Thanks for the help, I'll have a play with femon on my own system as  
well, would be good to get some feel for benchmark values on a system  
with good clean signal. I think I'm helping another friend get over  
the initial MythTV hurdle next week, thankfully he's on a few miles  
away and has the same tuners as me so "should" be easy.

Regards

Andre


More information about the mythtv-users mailing list