From: "Charlie X. Liu" <charlie@sensoray.com>
To: "'Daniel Glöckner'" <daniel-gl@gmx.net>,
"'Steve Cookson'" <it@sca-uk.com>
Cc: "'James Board'" <jpboard2@yahoo.com>, <linux-media@vger.kernel.org>
Subject: RE: HD Capture Card (HDMI and Component) output raw pixels
Date: Tue, 18 Jun 2013 17:38:00 -0700 [thread overview]
Message-ID: <012601ce6c85$40930470$c1b90d50$@com> (raw)
In-Reply-To: <20130618230655.GA23989@minime.bse>
Right -- not practical, since you need 1920*1080*3*50 = 311.04MB/s bandwidth
to transfer from PCIe and save the raw date onto a SSD, at which the PCIe
1.x link x1 (max 250MB/s) can not really meet such requirement.
Well, PCIe 2.x link x1 can meet since its max is 500MB/s. Or, using YUYV, a
more common format, would be fine, since it requires 207.36MB/s and reduces
the storage requirement from 1.119744GB (1920*1080*3*50*60*60, with RGB
format) to 0.746496GB (1920*1080*2*50*60*60, with YUYV format).
Best,
Charlie X. Liu
-----Original Message-----
From: linux-media-owner@vger.kernel.org
[mailto:linux-media-owner@vger.kernel.org] On Behalf Of Daniel Glöckner
Sent: Tuesday, June 18, 2013 4:07 PM
To: Steve Cookson
Cc: 'James Board'; linux-media@vger.kernel.org
Subject: Re: HD Capture Card (HDMI and Component) output raw pixels
On Tue, Jun 18, 2013 at 05:55:15PM -0300, Steve Cookson wrote:
> > I don't want to configure a RAID either, but if I purchase one SSD
> > with
> 400 MB/sec write speeds, that might be good.
>
> Hmm... nice idea. Did you have any particular model in mind? If you
> had a link, I might be interested. I wouldn't know about sizing. I
> don't know how much space HD raw video takes up per hour, say.
That's easy. My current video mode is 24 bit 1920x1080 at 50 fps.
So there are 3*1920*1080*50 bytes per second or about 1.1TB per hour.
But you won't be able to capture all frames with that card. The single lane
PCIe 1.x bus will max out at 200~250MB/s.
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-19 1:34 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 [this message]
2013-06-19 13:35 ` James Board
2013-06-19 14:10 ` Bjørn Mork
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='012601ce6c85$40930470$c1b90d50$@com' \
--to=charlie@sensoray.com \
--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