public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@kernellabs.com>
To: David Ward <david.ward@gatech.edu>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
	linux-media@vger.kernel.org
Subject: Re: cx18, s5h1409: chronic bit errors, only under Linux
Date: Mon, 08 Jun 2009 12:31:30 -0400	[thread overview]
Message-ID: <4A2D3CE2.7090307@kernellabs.com> (raw)
In-Reply-To: <4A2D3A40.8090307@gatech.edu>

David Ward wrote:
> On 06/08/2009 10:17 AM, Devin Heitmueller wrote:
>> On Mon, Jun 8, 2009 at 10:14 AM, Steven Toth<stoth@kernellabs.com>  
>> wrote:
>>   
>>>> Please let me know how I should proceed in solving this.  I would be 
>>>> happy
>>>> to provide samples of captured video, results from new tests, etc.
>>>>        
>>> When you tune using azap, and you can see UNC and BER values, what is 
>>> the
>>> SNR value and does it move over the course of 30 seconds?
>>>
>>> -- 
>>> Steven Toth - Kernel Labs
>>> http://www.kernellabs.com
>>>      
>> Also, I believe UNC and BER display garbage when signal lock is lost,
>> so do you see the "status" field change when the BER/UNC fields show
>> data?
>>
>> Devin
>>
>>    
> Steven, Devin,
> 
> Thanks for your replies.  The signal and SNR are usually in the range 
> 0x0128 - 0x0140.  They may increment or decrement on a per-second basis 
> but otherwise remain steady.  The status field does not change most of 
> the time when bit errors occur, but it does lose the lock from time to 
> time for a second.  Here is a representative sample:
> 
> david@delldimension:~$ azap -r RTN
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> tuning to 555000000 Hz
> video pid 0x0051, audio pid 0x0052
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 1f | signal 012e | snr 012e | ber 00001b04 | unc 00001b04 | 
> FE_HAS_LOCK
> status 1f | signal 012c | snr 012e | ber 00000000 | unc 00000000 | 
> FE_HAS_LOCK

Your SNR is very low, 0x12c is 30db. I assume you're using digital cable this is 
borderline.

I like my cable system at home to be atleast 32db (0x140) bare minimum, it's 
typically 0x160 (36db) for comfort.

It's possible that the tuner and 1409 driver are a little more optimized under 
windows.

How much attenuation can you add under windows with signal loss? It's probably 
reasonably close to the edge also.

-- 
Steven Toth - Kernel Labs
http://www.kernellabs.com

  reply	other threads:[~2009-06-08 16:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 10:31 cx18, s5h1409: chronic bit errors, only under Linux David Ward
2009-06-08 14:14 ` Steven Toth
2009-06-08 14:17   ` Devin Heitmueller
2009-06-08 16:20     ` David Ward
2009-06-08 16:31       ` Steven Toth [this message]
2009-06-08 17:16         ` David Ward
2009-06-08 20:20           ` Steven Toth
2009-06-08 20:36             ` Devin Heitmueller
2009-06-08 21:03               ` David Ward
2009-06-08 21:09                 ` Devin Heitmueller
2009-06-09 14:23                 ` Steven Toth
2009-06-09 14:21               ` Steven Toth
2009-06-09 14:23                 ` Devin Heitmueller
2009-06-09 14:24                   ` Steven Toth
2009-06-09 18:52                     ` David Ward
2009-06-09 18:55                       ` Devin Heitmueller
2009-06-09 19:04                         ` Steven Toth
2009-06-09 19:07                           ` Devin Heitmueller
2009-06-09 19:26                             ` Steven Toth
2009-06-10  8:11                               ` David Ward
2009-06-10 14:32                                 ` Steven Toth
2009-06-11 21:27                                   ` David Ward
2009-06-09 19:05                         ` Steven Toth
2009-06-09  2:44             ` Andy Walls

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A2D3CE2.7090307@kernellabs.com \
    --to=stoth@kernellabs.com \
    --cc=david.ward@gatech.edu \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox