From: Steven Toth <stoth@linuxtv.org>
To: CityK <cityk@rogers.com>
Cc: Devin Heitmueller <devin.heitmueller@gmail.com>,
V4L <video4linux-list@redhat.com>, David Engel <david@istwok.net>,
linux-media@vger.kernel.org
Subject: Re: PVR x50 corrupts ATSC 115 streams
Date: Thu, 19 Feb 2009 10:26:08 -0500 [thread overview]
Message-ID: <499D7A10.8080709@linuxtv.org> (raw)
In-Reply-To: <499CBFCA.6040108@rogers.com>
CityK wrote:
> Steven Toth wrote:
>> Agreed, probably a secondary issue - which probably needs some
>> attention regardless.
>>
>> I don't follow kworld products so I don't pretend to know which demod
>> they're using. I guess my question to the wider audience is, do people
>> with this same demod on other cards experience similar BER issues.
>
> The KWorld 11x uses the Nxt2004 demod ... and "Zoinks!", upon checking,
> I find that my single 11x card is now exhibiting BER too ! This is
> something new to me, as previous femon output was always free of such
> errors.
The numbers are suspicious, (presumably) post-viterbi errors without UCB
shouldn't happen, unless the driver isn't properly querying the demod stats. I'm
not sure of the nxt2004's history so maybe this has always been an issue, maybe
BER and UCB were never properly implemented? If I had a card I'd take a look. I
don't so I can't help.
Clearly, I wouldn't trust that driver or its numbers right now.
- Steve
next prev parent reply other threads:[~2009-02-19 15:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 15:53 PVR x50 corrupts ATSC 115 streams David Engel
2009-02-17 16:05 ` Steven Toth
2009-02-17 20:17 ` David Engel
2009-02-17 20:29 ` Steven Toth
2009-02-17 20:56 ` David Engel
2009-02-17 21:05 ` Devin Heitmueller
2009-02-17 22:29 ` Steven Toth
2009-02-17 22:38 ` Devin Heitmueller
2009-02-18 15:16 ` Steven Toth
2009-02-19 2:11 ` CityK
2009-02-19 15:26 ` Steven Toth [this message]
2009-02-18 5:19 ` David Engel
2009-02-18 8:25 ` Rudy Zijlstra
2009-02-18 15:29 ` David Engel
2009-02-18 14:56 ` Steven Toth
2009-02-18 15:34 ` David Engel
2009-02-19 16:28 ` David Engel
2009-02-19 16:44 ` Steven Toth
2009-02-22 19:35 ` CityK
2009-02-23 18:39 ` David Engel
2009-02-23 19:06 ` Steven Toth
2009-02-23 20:10 ` David Engel
2009-02-23 21:53 ` Steven Toth
2009-02-23 22:03 ` Devin Heitmueller
2009-02-23 22:48 ` David Engel
2009-02-23 22:58 ` Devin Heitmueller
2009-02-24 1:38 ` pat-lkml
2009-02-24 16:40 ` David Engel
2009-02-24 0:05 ` Andy Walls
2009-08-07 2:50 ` David Engel
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 12:41 Andreas
2009-02-18 15:39 ` David Engel
2009-02-19 3:37 ` CityK
2009-02-19 13:30 ` Andreas
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=499D7A10.8080709@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=cityk@rogers.com \
--cc=david@istwok.net \
--cc=devin.heitmueller@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=video4linux-list@redhat.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