public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Connor Behan <connor.behan@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: au0828 errors and mangled video with Hauppauge 950Q
Date: Tue, 04 Feb 2014 22:05:11 -0800	[thread overview]
Message-ID: <52F1D497.4010509@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

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

It is supposed to be a hockey game. When the broadcast cuts to a
commercial, I still see frames of the game for about 5 seconds, then the
fuzzy stuff on the screen contains some images from the game and some
images from the commercial, then it fully switches over to the
commercial. Frames that are supposed to be seen at different times are
being mixed together.

When I enable debugging for all of the media modules, my dmesg is
dominated by au0828 calls to print_err_status:
http://pastebin.ca/2628011 When I enable debugging on all modules except
the au0828, what I see is:

Insert tuner: http://pastebin.ca/2628012
mplayer tv:///2: http://pastebin.ca/2628017

Does this shed light on the problem? I'd be happy to test patches.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

             reply	other threads:[~2014-02-05  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  6:05 Connor Behan [this message]
2014-02-05  9:46 ` au0828 errors and mangled video with Hauppauge 950Q Devin Heitmueller
2014-02-06 19:20   ` Connor Behan

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=52F1D497.4010509@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