From: Sam Logen <starz909@yahoo.com>
To: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Cc: video4linux-list@redhat.com
Subject: Re: Question - Component input via software card
Date: Wed, 4 Jun 2008 15:33:45 -0700 (PDT) [thread overview]
Message-ID: <43192.2143.qm@web35602.mail.mud.yahoo.com> (raw)
In-Reply-To: <loom.20080603T211838-212@post.gmane.org>
--- Daniel Gimpelevich
<daniel@gimpelevich.san-francisco.ca.us> wrote:
> Sam Logen <starz909 <at> yahoo.com> writes:
>
> > Would it be possible to connect component cables
> from
> > a high def. video source to the video and audio
> > composite plugs of the capture card, and have a
> > program process the three streams together as
> video
> > streams instead of video and audio streams, then
> save
> > the result in a file?
>
> That would not be possible with any off-the-shelf
> composite capture card, but it
> would be possible to design your own capture
> hardware that could use the same
> plugs for either audio or component video. Just
> getting a Hauppauge HD-PVR would
> likely be cheaper.
I hadn't heard of that. I haven't been paying
attention to latest hardware releases. But can you
explan why my suggestion wouldn't be possible? I've
no doubt you're right, I'd just like to hear why.
That HD-PVR looks the way to go, but adding that thing
looks like it will up my cabinet temp by 20 degrees.
Sam
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-06-04 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 20:55 Question - Component input via software card Sam Logen
2008-06-03 21:22 ` Daniel Gimpelevich
2008-06-04 22:33 ` Sam Logen [this message]
2008-06-04 23:15 ` Christoph Willing
2008-06-03 21:49 ` Daniel Glöckner
2008-06-05 21:25 ` Sam Logen
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=43192.2143.qm@web35602.mail.mud.yahoo.com \
--to=starz909@yahoo.com \
--cc=daniel@gimpelevich.san-francisco.ca.us \
--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 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.