From: Steven Toth <stoth@linuxtv.org>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: David Engel <david@istwok.net>,
linux-media@vger.kernel.org, V4L <video4linux-list@redhat.com>
Subject: Re: PVR x50 corrupts ATSC 115 streams
Date: Wed, 18 Feb 2009 10:16:43 -0500 [thread overview]
Message-ID: <499C265B.9010309@linuxtv.org> (raw)
In-Reply-To: <412bdbff0902171438u7c2ab531y62bb6c717647e917@mail.gmail.com>
Devin Heitmueller wrote:
> On Tue, Feb 17, 2009 at 5:29 PM, Steven Toth <stoth@linuxtv.org> wrote:
>> The driver is probably buggy. Either its really reporting pre-viterbi errors
>> OR it's reporting real post-viterbi errors - but in which case why aren't we
>> also measuring uncorrected blocks?
>>
>> Regardless of Davids actual current problem, this sounds like a secondary
>> unrelated issue.
>>
>> - Steve
>
> Sorry, I didn't intend to suggest that the BER code isn't buggy - just
> that I doubt it has any bearing on his actual problem since they occur
> regardless of whether the other cards are running.
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.
- Steve
next prev parent reply other threads:[~2009-02-18 15:16 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 [this message]
2009-02-19 2:11 ` CityK
2009-02-19 15:26 ` Steven Toth
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=499C265B.9010309@linuxtv.org \
--to=stoth@linuxtv.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.