Ask Your Question
1

Capture Properties

asked 2012-07-06 04:34:16 -0600

vhdirk gravatar image

I'm implementing support for camera's I use into opencv itself. Now, it seems that there are lots more properties accessible than is apparent in the documentation. Here's a list if properties I've found (with the obvious ones removed).

CV_CAP_PROP_FORMAT: Pixel format, I suppose.
CV_CAP_PROP_MODE: Capture mode. fixed framerate or external triggers perhaps?
CV_CAP_PROP_CONVERT_RGB: Convert any requested pixel format to RGB24?
CV_CAP_PROP_MONOCROME: Convert to monochrome. Does this take precedence over CV_CAP_PROP_CONVERT_RGB?
CV_CAP_PROP_TEMPERATURE: Colour temperature?
CV_CAP_PROP_TRIGGER: ?
CV_CAP_PROP_TRIGGER_DELAY: ?
CV_CAP_PROP_GUID: ?
CV_CAP_PROP_SETTINGS: ??

Can someone briefly explain what the expected "behaviour" is for these values?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2012-07-09 15:41:51 -0600

Vincent Rabaud gravatar image

My 2 cents: I would guess that if those are not in the docs, they are meant for internal use, maybe for internal optimization sometimes. E.g., if CVCAPPROPCONVERTRGB is doing RGB conversion, it could be used internally to make sure the returned image is RGB.

edit flag offensive delete link more

Comments

For some of these properties that could be a possibility, indeed. However, in that case it seems pretty weird that colour temperature (CVCAPPROP_TEMPERATURE?) is internal, since I would assume that to be something a user should really be able to pick himself..

vhdirk gravatar imagevhdirk ( 2012-07-10 04:16:44 -0600 )edit
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2012-07-06 04:34:16 -0600

Seen: 1,771 times

Last updated: Jul 09 '12