All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas <linuxdreas@dslextreme.com>
To: linux-media@vger.kernel.org
Subject: Re: PVR x50 corrupts ATSC 115 streams
Date: Wed, 18 Feb 2009 04:41:40 -0800	[thread overview]
Message-ID: <200902180441.40316.linuxdreas@dslextreme.com> (raw)

Am Dienstag, 17. Februar 2009 21:19:45 schrieben Sie:
[...]
> So what does all of this indicate?  My original hunch was that it's a
> problem with the x50 hardware or driver (at least in combination with
> my motherboard).  I think I'm back to that conclusion.
>
> BTW, in my testing last night, I tried changing the PCI latency timer
> on the x50 cards.  I thought maybe it was holding off access to the
> 115 cards.  Changing that had no effect.

Just to let you know that you're not alone:
I had a simiilar problem with the combination of an AverMedia A180 and 
two Asus Falcon (they use the ivtv drivers and firmware). Whenever one 
of the Falcons was recording, I got blips and dropouts on the 
AverMedia. I chalked it off to a flaky mainboard and seperated the 
Falcons and the Avermedia in two different computers. A while later I 
got a new mainboard and additional ATSC tuner cards. As long as I had 
two of the ATSC tuner cards installed, the recordings were ok, except 
for an occasional dropout. But when I put a third ATSC tuner in, the 
recordings were barely watchable. After I put two ATSC tuners (2x 
Avermedia A180) in a different computer, they *all* are recording 
almost perfectly. Even a HVR-1600 card that I had dismissed as broken, 
delivers very good recordings in the other computer.

-- 
Gruß
Andreas

             reply	other threads:[~2009-02-18 12:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 12:41 Andreas [this message]
2009-02-18 15:39 ` PVR x50 corrupts ATSC 115 streams David Engel
2009-02-19  3:37 ` CityK
2009-02-19 13:30   ` Andreas
  -- strict thread matches above, loose matches on Subject: below --
2009-02-17 15:53 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
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

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=200902180441.40316.linuxdreas@dslextreme.com \
    --to=linuxdreas@dslextreme.com \
    --cc=linux-media@vger.kernel.org \
    /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.