From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Veda N <veda74@gmail.com>
Cc: video4linux-list@redhat.com
Subject: Re: pixel sizes
Date: Sat, 7 Jun 2008 16:29:23 +0200 [thread overview]
Message-ID: <20080607142923.GA588@daniel.bse> (raw)
In-Reply-To: <a5eaedfa0806070650x5daabac2ia12cdee022aa9f9f@mail.gmail.com>
On Sat, Jun 07, 2008 at 07:20:36PM +0530, Veda N wrote:
> Are the sizes of each pixels same for all the sensor?
No
> Does each sensor
> have its own size description for each pixel.
Yes
You can find the size of a pixel in the datasheet.
> I guess each LCDs/Display Units have their own pixel sizes.
> In which case how the captured pixels are displayed on the LCD?
Depends on the user. Either 1:1 pixelwise or scaled to fit/fill the screen.
> Should the definitions of pixels (sizes & format) of sensor and
> display unit match?
No.
Some cameras capture anamorph images to have less data.
And a pixel that is a few micrometer^2 usually represents a bigger area in
reality due to the optics.
> Do video applications have their own definition of how much size
> each pixel should have?
No.
Video applications don't care about real world dimensions.
They just want to fill the screen.
They do care about the aspect ratio of the pixels, though.
> Does the size of the pixel size change if it is RGB or YUV422?
No.
But in YUV422 there is only one chroma sample for two horizontal pixels.
Daniel
--
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-07 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 13:50 pixel sizes Veda N
2008-06-07 14:29 ` Daniel Glöckner [this message]
2008-06-08 11:07 ` Veda N
2008-06-08 13:04 ` Daniel Glöckner
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=20080607142923.GA588@daniel.bse \
--to=daniel-gl@gmx.net \
--cc=veda74@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox