public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: David Engel <david@istwok.net>
To: Steven Toth <stoth@linuxtv.org>
Cc: linux-media@vger.kernel.org, V4L <video4linux-list@redhat.com>
Subject: Re: PVR x50 corrupts ATSC 115 streams
Date: Wed, 18 Feb 2009 09:34:22 -0600	[thread overview]
Message-ID: <20090218153422.GC15359@opus.istwok.net> (raw)
In-Reply-To: <499C218D.7050406@linuxtv.org>

On Wed, Feb 18, 2009 at 09:56:13AM -0500, Steven Toth wrote:
>> I then removed the 250 from slot 4 leaving the 115s in slots 1 and 2.
>> The ber was through the roof and the recorded strams were filled with
>> errors and were barely playable at best.
>
> This ^^^^ is bad, you have something wrong with your feeds. They're 
> probably over amp'd and your leaking RF like crazy.
>
> Go back to basics, put the single unsplit and unamped feed into a single 
> 115 and get that working reliably. Then, split (or amp) and try the 
> second 115.
>
> Try to work out what's causing BER to be > 0 and fix that first.
>
> Personally, I wouldn't add the 250/350 back into the system until I had 
> both 115's running flawlessly with 0 BER and 0 UNC.
>
> Chances are, the 250/350 will work correctly after this - unless the 
> drivers really do have a DMA issue. It's too early to say given the 
> BER/UNC issues you're seeing though.

OK.  I've got another window this evening where I can do some testing
without disupting things too much.

David
-- 
David Engel
david@istwok.net

  reply	other threads:[~2009-02-18 15:34 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
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 [this message]
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=20090218153422.GC15359@opus.istwok.net \
    --to=david@istwok.net \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@linuxtv.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