Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AE exposure time limit, OV9282/OV9782 image quality and FPS improvements #926

Merged
merged 7 commits into from
Nov 24, 2023

Conversation

alex-luxonis
Copy link
Contributor

Added CameraControl API:

  • setAutoExposureLimit(uint32_t maxExposureTimeUs);
  • setAutoExposureLimit(std::chrono::microseconds maxExposureTime);

Set a command to specify the maximum exposure time limit for auto-exposure. By default
the AE algorithm prioritizes increasing exposure over ISO, up to around frame-time
(subject to further limits imposed by anti-banding)

Can be applied both using initialControl, and at runtime.

Other FW changes: improved OV9282 and OV9782 image quality under low-light scenarios - high ISO (over 1300).
It got degraded (more noise) for the 800p/720p resolutions after the switch to the max-120fps configs: #620, was introduced with depthai v2.20.0 (and v2.21.0 for socket CAM_A).

Also improved maximum FPS, with new ranges per resolution of:

  • THE_800_P: 1.687 .. 129.6 fps
  • THE_720_P: 1.687 .. 143.1 fps
  • THE_400_P: 1.687 .. 255.7 fps
    (For the latter to be achievable, will need to be paired with .setIsp3aFps(some_lower_rate) for which some further stability fixes are needed)

Related: luxonis/depthai-shared#153

Base automatically changed from ir-intensity to develop November 23, 2023 21:55
@alex-luxonis alex-luxonis merged commit 7b6f022 into develop Nov 24, 2023
24 of 30 checks passed
@alex-luxonis alex-luxonis deleted the ae_exp_limit branch November 24, 2023 00:52
This was referenced Dec 13, 2023
jakgra pushed a commit that referenced this pull request Mar 20, 2024
@patripfr
Copy link

Hi,
On my OAK-1 MAX I am limiting the maximum autoexposure time using setAutoExposureLimit(limit)

However, every now and then (especially after large view point changes) the camera seems to ignore this and uses a longer exposure time. After a few seconds it jumps back to the commanded limit.
The observed behaviour can be seen in the following video:
exposure_flicker
The darker images are using the correct, low exposure time and you can see a bright flickering from time to time where the camera switches to a longer exposure time.

Any ideas how to address this issue?

@alex-luxonis
Copy link
Contributor Author

Hi @patripfr , yeah we found this bug after the feature was introduced, it should have been fixed in v2.25.0 release. The auto-focus algo caused this problem when it ran again at a scene change, or periodically.
Could you try the latest release at the moment v2.25.1, or develop.

@patripfr
Copy link

that fixed it, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Trying to limit the maximum exposure time in auto-exposition (better IQ with low blur for SLAM)
5 participants