From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Andy Walls <awalls@radix.net>
Cc: Hans de Goede <j.w.r.degoede@hhs.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: libv4l2 and the Hauppauge HVR1600 (cx18 driver) not working well together
Date: Thu, 03 Sep 2009 12:23:21 +0100 [thread overview]
Message-ID: <4A9FA729.3010207@onelan.com> (raw)
In-Reply-To: <1251975978.22279.8.camel@morgan.walls.org>
Andy Walls wrote:
> But I suspect no user pays for the extra cost of the CX2341[568]
> hardware MPEG encoder, if the user primarily wants uncompressed YUV
> video as their main format.
Actually, we're doing exactly that. We want a PCI card from a reputable
manufacturer which provides uncompressed YUV and ATSC (both OTA and
ClearQAM cable). As we already buy Hauppauge HVR-1110s for DVB-T and
uncompressed analogue, a Hauppauge card suits us, and the only thing
they have that fits the needs is the HVR-1600; the MPEG encoder is thus
left idle.
--
Simon Farnsworth
next prev parent reply other threads:[~2009-09-03 11:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 16:32 libv4l2 and the Hauppauge HVR1600 (cx18 driver) not working well together Simon Farnsworth
2009-09-02 17:44 ` Hans de Goede
2009-09-03 9:17 ` Simon Farnsworth
2009-09-03 9:28 ` Hans de Goede
2009-09-03 9:44 ` Hans de Goede
2009-09-03 10:21 ` Simon Farnsworth
2009-09-03 10:37 ` Simon Farnsworth
2009-09-03 10:56 ` Simon Farnsworth
2009-09-03 11:16 ` Andy Walls
2009-09-03 11:20 ` Hans de Goede
2009-09-03 11:23 ` Andy Walls
2009-09-04 3:14 ` Andy Walls
2009-09-04 6:22 ` Hans de Goede
2009-09-03 11:13 ` Hans de Goede
2009-09-03 11:45 ` Hans de Goede
2009-09-03 11:06 ` Andy Walls
2009-09-03 11:23 ` Simon Farnsworth [this message]
2009-09-03 11:29 ` Andy Walls
2009-09-03 11:44 ` Simon Farnsworth
2009-09-03 23:34 ` Andy Walls
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=4A9FA729.3010207@onelan.com \
--to=simon.farnsworth@onelan.com \
--cc=awalls@radix.net \
--cc=j.w.r.degoede@hhs.nl \
--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