From: Connor Behan <connor.behan@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: au0828 errors and mangled video with Hauppauge 950Q
Date: Thu, 06 Feb 2014 11:20:11 -0800 [thread overview]
Message-ID: <52F3E06B.5090702@gmail.com> (raw)
In-Reply-To: <CAGoCfiy-EdA4pbcCB6uLBSp7HUBW+=2vRYG8m+Q8V4tQmGTRag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On 05/02/14 01:46 AM, Devin Heitmueller wrote:
> On Wed, Feb 5, 2014 at 1:05 AM, Connor Behan <connor.behan@gmail.com>
> wrote:
>> Ccing Devin. I'm pretty sure the analog side has a problem at the driver
>> level.
>>
>> On most days, one cannot pickup an ATSC signal where I am, so I am
>> trying to capture analog video with a Hauppauge WinTV HVR 950Q. Whether
>> I use Television, Composite or S-Video, I see the same corrupted video
>> such as this: http://imgur.com/c398F4v
> Looks like insufficient USB bandwidth available to support the 24
> MB/second required for uncompressed analog video.
>
> Is this on an x86 PC? Or some embedded target such as ARM? If the
> latter, then the answer is almost certainly that the USB host
> controller implementation is garbage and cannot handle the throughput.
>
> Devin
>
It's an x86 PC but bandwidth was indeed the problem. I thought I was
having a power issue before. So I started using a Cardbus to USB adapter
that had an external power port. This was a mistake, and I can get the
tuner to work again if I switch back to a built-in port.
Thanks a lot.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
prev parent reply other threads:[~2014-02-06 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 6:05 au0828 errors and mangled video with Hauppauge 950Q Connor Behan
2014-02-05 9:46 ` Devin Heitmueller
2014-02-06 19:20 ` Connor Behan [this message]
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=52F3E06B.5090702@gmail.com \
--to=connor.behan@gmail.com \
--cc=dheitmueller@kernellabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox