From: David Ward <david.ward@gatech.edu>
To: Steven Toth <stoth@kernellabs.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: cx18, s5h1409: chronic bit errors, only under Linux
Date: Wed, 10 Jun 2009 04:11:31 -0400 [thread overview]
Message-ID: <4A2F6AB3.7080406@gatech.edu> (raw)
In-Reply-To: <4A2EB75A.4070409@kernellabs.com>
On 06/09/2009 03:26 PM, Steven Toth wrote:
> 30db for the top end of ATSC sounds about right.
>
> David, when you ran the windows signal monitor - did it claim QAM64 or
> 256 when it was reporting 30db?
Steven and Devin,
All the digital signals are 256 QAM.
> 39 is very good, exceptional.
>
> And did they do as I suggested, which is measure db across the high
> channels? ... and ideally against your problematic channel?
>
> I assume not.
Comcast checked the outlet on channels 2 (41 dB) and 83 (39 dB). I
looked afterwards and saw that the first of those is analog programming,
but the second just appears as analog noise on my TV set. (??) I asked
them to check a specific ATSC channel, but it seems that their meter was
fixed to those two frequencies, which doesn't really help. The ATSC
rebroadcasts by Comcast are on high frequencies; the program I am
testing primarily is on channel 79 (tunes at 555 MHz).
Under Windows I'm now seeing 34.5-34.8 dB for lower frequency QAM,
32.5-32.7 dB for higher frequency QAM, and about 30.5 dB for ATSC.
Under Linux with azap, the corresponding BER/UNC values are 0x0140,
0x0134, and 0x0132. I'm not exactly sure what numbers I should be going
by here...again, wish I had my own meter.
I admit that I ruled out the idea of RF issues too soon, which I really
should know better than. After reading the thread at
http://forums.gbpvr.com/showthread.php?t=36049 I'm now realizing why
reception on the TV and tuner card isn't going to be equal, due to
limited size and shielding of tuner circuitry on a PCI form factor card
vs. on a TV set. Makes sense.
Still, I am continuing to see uncorrectable bit errors at the same rate
as before under Linux, while Windows sees errors but corrects them. I
would think that both drivers should be receiving identical streams of
data from the chipset, and should be able to process them the same way?
That's what is confusing me.
Ideally I would like to have access to a lot more equipment to control
all the variables and make it easier to reproduce what I am seeing...but
I don't here...
Or do you guys think that this is still primarily an RF problem? I
don't know what else I could do about that though. Since the SNR did
not improve when I hooked the tuner card directly into the cable input
from the street, I'm concerned that putting an amplifier would not help
and could just make things worse. And clearly Comcast now considers me
to be within their quality thresholds.
I really appreciate your help and patience with me, especially to the
extent that this is going outside the realm of DVB drivers.
David
next prev parent reply other threads:[~2009-06-10 8:11 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
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 [this message]
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=4A2F6AB3.7080406@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