Autofocus improvements #270
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jun 2, 2025
|
It works great! |
This fixes two small bugs: We previously populated LensPosition's ControlInfo with hard-coded values, ignoring the tuning file. Now we query the AfAlgorithm to get limits (over all AF ranges) and default (for AfRangeNormal). We previosuly sent a default position to the lens driver, even when a user-specified starting position would follow. Defer doing this, to reduce unnecessary lens movement at startup (for some drivers). Signed-off-by: Nick Hollinghurst <nick.hollinghurst@raspberrypi.com>
njhollinghurst
force-pushed
the
af_202506
branch
4 times, most recently
from
9cc9f13 to
5a7fceb
Compare
In getPhase(), stop using different weights for sumWc and sumWcp. This should improve linearity e.g. in earlyTerminationByPhase(). Use AWB statistics, and optionally try to detect IR lighting and suppress PDAF in that case, as IR interferes with PDAF on IMX708. Make earlyTerminationByPhase() harder to trigger; extrapolate less. Improve quadratic peak fitting in findPeak(). The old approximation was good but only really valid when points were equally spaced and the MAX was not at one end of the series. For PDAF-based CAF, suppress lens movement unless "phase" has had the same sign for 4 frames in a row. This suppresses noise/wobble. Change the logic for falling back from PDAF to CDAF, and for re- triggering a CDAF-based scan. It is now triggered by image change (based on both Focus and AWB statistics) followed by stability. Modify CDAF scan pattern so it doesn't always start at the lowest setting, but can sometimes start from the current lens position. (Though in the worst case this requires two coarse scans, if the first one went in the wrong direction.) Shorten fine scan and allow it to be skipped when step_fine == 0 Signed-off-by: Nick Hollinghurst <nick.hollinghurst@raspberrypi.com>
Explicitly add new parameters: "retrigger_ratio", "retrigger_delay", "check_for_ir". Tweak other parameters to suit algorithm changes. (Though existing tuning files should still work acceptably.) Add AfSpeedFast parameters for the Raspberry Pi V3 standard lens. Signed-off-by: Nick Hollinghurst <nick.hollinghurst@raspberrypi.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal is to overhaul the RPI AF algorithm to:
without significant regression or making the code too messy.