[mythtv-users] Remote Mythfrontend Problem

[Jarod Wilson]

On Jul 15, 2009, at 10:36 AM, Steve Milner wrote:

> On 15/07/09 15:26, Nick Morrott wrote:
>> On 15/07/2009, Steve Milner<mythtv at stephen-milner.me.uk>  wrote:
>>
>>>  Reboot and then as user mythtv
>>>
>>>  xine dvb://"BBC ONE"
>>>
>>>  Will work, although viewing that at 384KBi/s  isn't what you  
>>> would call a
>>> working experience, but at least tonight I can get straight into  
>>> checking
>>> things out.
>>
>> If you run tzap with the channels.conf file (you could symlink xine's
>> copy to ~/.tzap/channels.conf) you should be able to see signal, SNR
>> and BER numbers on the console without needing the GUI..
>>
>> Nick
>>
>
> Nick, what a great idea.
>
> Here are a few of the typical results for:
>
> tzap -a 0 -r "ITV4"
>
> status 1f | signal b87a | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b82d | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b84b | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b85c | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b851 | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b81b | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b83e | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b832 | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b83e | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal b840 | snr 0000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
>
> I will spend some time watching this but it seems like things are ok.

Nb: not all drivers actually support snr/ber/unc properly, so its  
possible things look rosier than they really are there, but at least  
you have a lock and fairly constant signal level...

-- 
Jarod Wilson
jarod at wilsonet.com