Open fredsonnenwald opened 6 days ago
Hi, and thanks for the comments. I'm sorry that it's a bit misleading, but actually, when AE/AGC is off, quite a lot of it still runs to convert things like the exposure time you set into the internal units (lines) the camera wants. So it's never really "off", for what it's worth, though it does ensure to give you any "manual" values that have been set.
Actually AeLocked needs some work in general (it doesn't work as well as it should), at which point we can consider what it should report in the manual case (if anything).
But in any case, always check the exposure/gain values in the metadata from the request that you capture - these values should be correct.
Description When specifying
picam2.set_controls({"AeEnable": False})
to disable auto exposure, the request metadata dict contains anAeLocked
key. This suggests that auto exposure is still running, despite it being specifically disabled.To Reproduce Capture a still with auto exposure disabled:
Expected behaviour The assertion in the example code passes and the
AeLocked
is not present in request metadata.Console Output, Screenshots
Hardware : A Raspberry Pi 5 with a Raspberry Pi Camera v1.3 and the latest packages as of last month.
Additional context I am working on capturing raw images so I wanted to be sure what I was receiving was actually raw. I think it is, but the presence of
AeLocked
is very misleading.