Re: [RFC] White Balance control for digital camera

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Fri, 10 Apr 2009, Dongsoo, Nathaniel Kim wrote:

Hello everyone,

I'm posting this RFC one more time because it seems to everyone has
been forgot this, and I'll be appreciated if any of you who is reading
this mailing list give me comment.

I don't know much about the topic, and I wish I did.

I've got a big question popping up handling white balance with
V4L2_CID_WHITE_BALANCE_TEMPERATURE CID.

Because in digital camera we generally control over user interface
with pre-defined white balance name. I mean, user controls white
balance with presets not with kelvin number.
I'm very certain that TEMPERATURE CID is needed in many of video
capture devices, but also 100% sure that white balance preset control
is also necessary for digital cameras.
How can we control white balance through preset name with existing V4L2 API?

Let's broaden the question to include digital still cameras, which present similar problems. They present data related to this kind of thing, that is obvious. But are there any standard meanings to what is there? Do you know anything about that? Can you help?

Two examples:

The SQ905 and SQ905C cameras in stillcam mode use an allocation table, which presents on each line some data about the given image. In this line, byte 0 is a one-byte code for pixel dimensions and compression setting. Then some more bytes give the starting and ending locations of the photo in the camera's memory (actually irrelevant and superfluous information, because you can only ask for the photos in sequence, and with a command which has nothing to do with its memory location at all). Then some more bytes obviously have something to do with contrast, brightness, white balance, color balance, and so on. But I have no more idea than the Man in the Moon how those bytes are supposed to be interpreted. The SQ905 gives no such equivalent information while in streaming mode, and so there is nothing at all which could be done with the nonexistent information. But the SQ905C does obviously give such information, in a few bytes in the header of each frame.

The MR97310A cameras give similar information in the header of the photo itself (and in this case the camera does the same thing in webcam mode, too). Again, I have no idea either what these mysterious bytes are supposed to mean, and how to use them constructively.

I could mention several other examples, too, but these will do for a start.

Are there any agreed-upon standards about this kind of thing, in the camera industry? Is there any source of information about it?

Theodore Kilgore
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux