[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Camera module change proposal
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Camera module change proposal
- From: Alexandre Quessy <alexandre@xxxxxxxxxx>
- Date: Mon, 18 May 2009 17:29:36 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Mon, 18 May 2009 17:29:38 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=gRDSIz1m3wcNEc2aPhhBMKUO5J64ThNbdp/9Rl9IQ5s=; b=hH9EakbbKRSFERFwN3ztmWFnVx83Q1K/Yj6alc64mutRDJIFifF0qK6zTA1N0j5Emm 1b/cvCbElIOELuCNQnHoeR+ueSoThetF0968QYaWlUmFxzezQaLNyImLlTEc2jetD3CB 3cYV04mK8iQ6UJDebQzhnmjc1WgXsCqkSoNjE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=Lczxg5gfyvHzzkjc6D8i1XyM8wCJgNB3gZrDfUBoNINdFIqwRGYAtQf9nNx9ALDjH9 9tmFhFm9nQ+7MADvWHx3cuoiYBpxoSvraG+COe1CzX3SM5fvBkSrmfRSlSkV0zB6lxNx whlLJ2O7TseaOHwWeYNLgUdKoewO7O5G+VBw4=
- In-reply-to: <a7215bb70905181226k4f5be336w677438b48acd025e@xxxxxxxxxxxxxx>
- References: <a7215bb70905181226k4f5be336w677438b48acd025e@xxxxxxxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
Hello Nirav,
For #1, I can say that YUV colorspace is much faster than RGB to
upload to the graphic card when using OpenGL. If for now it is only
RGB that is implemented, it would surely be nice to have the
possibilty to use YUV directly in a near future.
For #2, on Mac OS X, there is at least the "Quicktime Dialog" that can
offer a lot of fine controls on the image source and quality. It
surely should be implemented in the first place.
Regards,
a
2009/5/18 Nirav Patel <olpc@xxxxxxxxxxxxxx>:
> Hello all,
>
> With 1.9 coming out soon, I think it is best that we decide on a final
> API for the camera module to use going forward. The current module
> was designed largely for v4l2 on low performance fixed point CPUs, and
> the API reflects that. With OS X support coming this summer from
> Werner, and Windows support coming soon, we should decide on something
> that works well across all platforms.
>
> 1. Remove colorspace conversion from the camera module:
> Currently, the camera module can "capture" images as RGB, YUV, or HSV.
> There are a lot of conversion shortcuts going on under the hood to
> get the quickest path from raw pixel data to the desired colorspace.
> Unfortunately, this also multiplies the amount of code and work
> necessary to bring the camera module to other platforms. The use
> cases for this feature are also fairly limited, since anyone doing
> serious computer vision is better off using OpenCV. I propose having
> the camera module do the more relevant task of just capturing RGB
> images, and have a seperate colorspace conversion function, either the
> transform or the color module, which takes any RGB surface and outputs
> an HSV or YUV surface.
>
> 2. Camera controls:
> I'm not sure what to do here. V4l2 controls are very useful to have,
> but there doesn't seem to be a Windows or OS X equivalent as far as I
> can tell.
>
> Any ideas on either?
>
> Nirav
>
--
Alexandre Quessy
http://alexandre.quessy.net/