public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ward <david.ward@gatech.edu>
To: Steven Toth <stoth@kernellabs.com>
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 13:16:40 -0400	[thread overview]
Message-ID: <4A2D4778.4090505@gatech.edu> (raw)
In-Reply-To: <4A2D3CE2.7090307@kernellabs.com>

On 06/08/2009 12:31 PM, Steven Toth wrote:
> Your SNR is very low, 0x12c is 30db. I assume you're using digital 
> cable this is borderline.
Oh okay ... I wasn't sure how to translate those values before.

> I like my cable system at home to be atleast 32db (0x140) bare 
> minimum, it's typically 0x160 (36db) for comfort.
In your opinion, would I have enough justification for asking Comcast to 
increase the signal strength coming to my house?  I'd like to avoid 
calling someone to come out to my house to say "your TV works fine, 
what's the problem?" and get slapped with a repair fee.  I wasn't sure 
how well I could trust the SNR values reported by the card either...  I 
wish I had a meter or something to test it on my own.  When I move the 
computer directly to the input for the entire house, I get an increase 
of about 0.1dB.

FYI, the signal strength is about 1dB higher for clear QAM signals.  
(The values I sent are for ATSC.)

> 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.
>
I tuned to the same channel under Windows, and I used the Signal 
Strength Indicator application from Hauppauge (downloadable under the 
Accessories page in the Support section).  It's reporting a SNR of 29-30 
dB, and the value for 'correctable' errors goes to a single-digit value 
about every 5 seconds -- following the same pattern seen with 'azap'.  
However, the difference is that 'uncorrectable' errors stays at 0.  
Under Linux, it seems that all errors are 'uncorrectable'.

Does the error correction occur in the driver or in the chipset?  Seems 
to me like maybe error correction is either not enabled or not 
implemented correctly by the driver?

I agree that the SNR could be better, and if you think it is worth a 
try, I'll see what Comcast will do.  However, because Windows and my TV 
work almost flawlessly, the Linux driver would ideally handle the 
signals at least as well as them...

Let me know what else is helpful from me, and thanks again for your help.

David

  reply	other threads:[~2009-06-08 17:16 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
2009-06-08 17:16         ` David Ward [this message]
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=4A2D4778.4090505@gatech.edu \
    --to=david.ward@gatech.edu \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@kernellabs.com \
    /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