public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: James Board <jpboard2@yahoo.com>
Cc: "Daniel Glöckner" <daniel-gl@gmx.net>,
	"Steve Cookson" <it@sca-uk.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: HD Capture Card (HDMI and Component) output raw pixels
Date: Wed, 19 Jun 2013 16:10:01 +0200	[thread overview]
Message-ID: <87ip1a42fa.fsf@nemi.mork.no> (raw)
In-Reply-To: <1371648937.52293.YahooMailNeo@web163906.mail.gq1.yahoo.com> (James Board's message of "Wed, 19 Jun 2013 06:35:37 -0700 (PDT)")

James Board <jpboard2@yahoo.com> writes:

> You are right.  According to your numbers, this card can't work.  So
> why would BlackMagic design an HDMI capture card with only one PCIe
> lane if it can't possibly work?   It must work somehow.  I must be
> missing some crucial piece of information.
>
> The card doesn't support hardware encoding, right?  If so, raw pixels
> are the only output.  Maybe the card uses more than one PCIe lane? 
> What makes you think the card only uses a single lane?

http://www.blackmagicdesign.com/products/intensity/techspecs/ says so.
It also says

 HD Format Support: 1080i50, 1080i59.94, 1080i60, 1080p23.98, 1080p24,
                    1080p25, 1080p29.97, 1080p30, 720p50, 720p59.94 and
                    720p60.

which makes the 1080p50 calculation a bit irrelevant.

> Are they using lossless compression to get the raw pixels data rate
> under 200-250 MB/sec, which is the PCIe speed?

None of the supported formats need more than ~180 MB/sec.


Bjørn

  reply	other threads:[~2013-06-19 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 14:32 HD Capture Card (HDMI and Component) output raw pixels James Board
2013-06-16 19:15 ` Steve Cookson
     [not found]   ` <1371572315.65617.YahooMailNeo@web163901.mail.gq1.yahoo.com>
2013-06-18 19:38     ` Steve Cookson
     [not found]       ` <1371587831.30761.YahooMailNeo@web163905.mail.gq1.yahoo.com>
2013-06-18 20:55         ` Steve Cookson
2013-06-18 23:06           ` Daniel Glöckner
2013-06-19  0:38             ` Charlie X. Liu
2013-06-19 13:35             ` James Board
2013-06-19 14:10               ` Bjørn Mork [this message]
2013-06-19 23:46                 ` Charlie X. Liu
2013-06-19 14:21               ` Steven Toth
2013-06-19 14:52                 ` Daniel Glöckner
2013-06-19 23:35               ` Charlie X. Liu

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=87ip1a42fa.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=daniel-gl@gmx.net \
    --cc=it@sca-uk.com \
    --cc=jpboard2@yahoo.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