public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jed <jedi.theone@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Hw capabilities of the HVR-2200
Date: Sat, 19 Sep 2009 15:37:28 +1000	[thread overview]
Message-ID: <4AB46E18.7090900@gmail.com> (raw)
In-Reply-To: <4AB3D0BA.1010609@kernellabs.com>

>>>>>>> 2) Component input for the A/V-in
>>>>>
>>>>> Yes, this exists on the HVR2250 product only.
>>>>
>>>> Ah shite, are you sure?
>>>> If you look at the specs for the reference card it was there, did they
>>>> take it out at the last minute?
>>>
>>> It's not feature Hauppauge supports on the HVR2200 today. I have a
>>> suspicion this may change but I'm neither confirming, denying or
>>> announcing anything. It would make sense to officially support
>>> component cables on the HVR2200 since the silicon supports it. If/when
>>> it does I'm sure it will be mentioned in the forums or on the HVR2200
>>> product packaging.
>>
>> So I garner from that, that you don't intend to add support for anything
>> (including extra encoding abilities that they don't support in Windows)
>> unless Hauppauge officially does?
> 
> No, I was referring specifically to your component 'are you sure?' 
> question.
> 
> I've said many times on and off this mailing list that I'd like to add 
> support for all of the encoder a/v codecs, regardless of the windows 
> driver and it's capabilities. Timeframe for this is unknown.

Okay thanks Steven for taking some time to address these Qns, I'm done.



  reply	other threads:[~2009-09-19  5:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  8:55 Hw capabilities of the HVR-2200 Jed
2009-09-16 17:23 ` Jed
2009-09-18 16:24 ` Jed
2009-09-18 16:45   ` Steven Toth
2009-09-18 17:21     ` Jed
2009-09-18 17:52       ` Steven Toth
2009-09-18 18:13         ` Jed
2009-09-18 18:26           ` Steven Toth
2009-09-19  5:37             ` Jed [this message]
2010-03-09 17:16           ` Jed
2010-03-11 15:38             ` Steven Toth
2010-03-11 16:46               ` Jed
2010-03-12 17:26               ` Jed
2010-03-12 17:39                 ` Devin Heitmueller
2010-03-10  4:22           ` Jed
2009-09-18 16:24 ` Jed
2009-09-18 16:27   ` Jed

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=4AB46E18.7090900@gmail.com \
    --to=jedi.theone@gmail.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