linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: workshop-2011@linuxtv.org, Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [Workshop-2011] V4L2 API ambiguities: workshop presentation
Date: Fri, 17 Aug 2012 15:23:23 +0200	[thread overview]
Message-ID: <502E45CB.6090103@redhat.com> (raw)
In-Reply-To: <70803480.BV5Mjk80If@avalon>

Hi,

On 08/17/2012 02:57 PM, Laurent Pinchart wrote:

<Snip>

>> Regarding ENUM_FRAMESIZES: it makes sense to add an aspect ratio here for
>> use with sensors. But for video receivers ENUM_FRAMESIZES isn't applicable.
>
> Do we have sensors with non-square pixels ?

Short answer: not that I know of.

Long answer: that depends on the optics (so the sensor pixels may be square,
but the optics could make them non-square from a proper mapping to a real world
picture pov).

As I've done too much with weird old webcams I actually now webcams which do
this, the vicam cameras to be precise. The 3 com HomeConnect (04c1:009) has
a sensor with a native resolution of 512x244, yeah widescreen baby!

But it stems from an area where widescreen was unheard of in computer graphics,
so it actually has optics which force that cool widescreen resolution back into
a 4x3 field of view. So for a proper square pixels image form that camera its
image needs to be scaled from 512x244 to 512x384 (*). But with that one exception
proving the rule (Dutch expression), I think all sensors have square pixels.

Regards,

Hans

*) Really? Yes really!

  reply	other threads:[~2012-08-17 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 10:35 V4L2 API ambiguities: workshop presentation Hans Verkuil
2012-08-17 12:48 ` Hans de Goede
2012-08-17 12:55   ` Hans Verkuil
2012-08-17 12:57     ` [Workshop-2011] " Laurent Pinchart
2012-08-17 13:23       ` Hans de Goede [this message]
2012-08-22 11:09 ` Hans Verkuil

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=502E45CB.6090103@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=workshop-2011@linuxtv.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;
as well as URLs for NNTP newsgroup(s).