motioneye icon indicating copy to clipboard operation
motioneye copied to clipboard

No auto exposure with OV5647 at high resolutions

Open jrhansen opened this issue 3 years ago • 4 comments

Hi

MotionEye and Pi camera newbie here :)

I bought a bunch of OV5647 cameras and Raspberry Pi Zero 2 W's, and it seems that the auto exposure function stops working (the exposure doesn't change according to overall light level) when I set the resolution to anything over 1280x720 (BTW: I am not using the "Automatic Brightness" function in MotionEye). Is this a known "feature" with the particular camera or MotionEye?

In general, I don't understand the camera settings that is shown in MotionEye (Auto Exposure, Auto Exposure Bias, etc.), because they don't seem to do anything. Also, when using the v4l2-clt command the settings are not synchronized to the ones in MotionEye. Can anyone explain the relationsship between the camera settings in MotionEye and the ones listed by the v4l2-clt command?

Finally, the camera is connected to the CSI connector of the Raspberry Pi, but I can only add it to MotionEye as a "Local V4L2 Camera" and not "MMAL". Is that ok, or is this related to some of my problems?

Thanks in advance Hansen :)

jrhansen avatar Jul 16 '22 10:07 jrhansen

AFAIK the MMAL driver isn't available any more in newer distros like Bullseye, it's been replaced by a new V4L2 driver/software stack and the brightness problem seems to relate to this new driver. I've seen the problem talked about elsewhere but haven't come across any real solutions. The same module works fine with MotioneyeOS that still uses the old MMAL driver.

harakka avatar Aug 06 '22 10:08 harakka

AFAIK the MMAL driver isn't available any more in newer distros like Bullseye

It is, but legacy display drivers need to be enabled, e.g. via raspi-config or by removing the vc4-(f)kms-v3d overlay from /boot/config.txt.

Basically it is all discussed here: #2425

MichaIng avatar Aug 06 '22 13:08 MichaIng