Yes I did try to set it to off but didnt seem to work, however if I useSnowLeopard wrote:Set it to MMAL_PARAM_AWBMODE_OFF?
Edit: Nevermind... I'm guessing you've tried that already. I hadn't seen this other thread:
http://www.raspberrypi.org/phpBB3/viewt ... 43&t=56698
Code: Select all
raspivid -t 10000 -awb off
Ok, I'll give that a shot. I have tried setting it to MMAL_PARAM_AWBMODE_OFF before but it seemed to make no difference, will try to set to something else.ethanol100 wrote:You can set it to a fixed awb mode in RaspiCamControl.c
See the function : void raspicamcontrol_set_defaults(RASPICAM_CAMERA_PARAMETERS *params)
and change the default parameter : params->awbMode = MMAL_PARAM_AWBMODE_AUTO;
to i.e. MMAL_PARAM_AWBMODE_SUNLIGHT
The camera needs to use some model for the white balance, but if it is not set to MMAL_PARAM_AWBMODE_AUTO the white balance should be fixed.
(That is my understanding of AWB, hope it is not wrong...)
For some background see i.e. http://cpn.canon-europe.com/content/edu ... balance.do.
Is that AWB or gain control causing the problem? First gives changing colours, second gives changing brightness. You can try a different metering mode to see if that helps.Samy74 wrote:AWB is really a nightmare for me. I'm doing image processing in a mobile robot, image lightning is changing every time it moves...
You are correct in your analysis 4 (although I think I had posted all this before). I'm going to chat with the AWB experts today to find out what is actually supposed to happen vs what is actually happening.paranoidcoder wrote:tl;dr: I think it's safe to say this camera does no support turning AWB off/static at least for the time being, unless anybody knows a library which sends the correct bit string to the camera.
this problem goes deep....
I'm using the userland library instead of the uv4l driver.
Even userland doesnt have it right yet....
Here's what i've found:
I went all the way down to the level where ioctl is called in /userland/interface/vchiq_arm/vchiq_lib.c method vchiq_queue_message, to send the message directly to the camera
the values made in structs and such DO propagate all the way down and attempt to set AWB off, however, as you can imagine, it doesn't work.
I've tried messing around with some of the bits that look like they might be useful to flip, but to no avail.
At this point, the person who made the chip would have to tell me what to do to be able to change this setting.
So this leaves a few possibilities i can think of:
1. the message does change the right value, but is changed later
2. it changes the wrong value and who knows what settings AWB off really does
3. we're sending the wrong setting over for the camera
4. camera doesnt support turning AWB off (built in)
If i'm missing something, feel free to point it out. This is my best shot at figuring out what's wrong. Looks like i'm going to have to get another camera for my mobile robot