mirror of
https://git.libcamera.org/libcamera/libcamera.git
synced 2025-07-13 15:29:45 +03:00
android: camera_device: Return AE FPS range
The result metadata reports an arbitrary {30, 30} FPS range for the AE algorithm. The actual FPS range should be returned in the Request::metadata, but as libcamera currently does not support that feature temporarily work around the issue and return the FPS range requested by the camera framework. Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
This commit is contained in:
parent
238fb27911
commit
d150860129
1 changed files with 8 additions and 3 deletions
|
@ -2070,9 +2070,14 @@ CameraDevice::getResultMetadata(Camera3RequestDescriptor *descriptor,
|
|||
value = ANDROID_CONTROL_AE_MODE_ON;
|
||||
resultMetadata->addEntry(ANDROID_CONTROL_AE_MODE, &value, 1);
|
||||
|
||||
std::vector<int32_t> aeFpsTarget = { 30, 30 };
|
||||
if (settings.getEntry(ANDROID_CONTROL_AE_TARGET_FPS_RANGE, &entry))
|
||||
/*
|
||||
* \todo Retrieve the AE FPS range from the libcamera metadata.
|
||||
* As libcamera does not support that control, as a temporary
|
||||
* workaround return what the framework asked.
|
||||
*/
|
||||
resultMetadata->addEntry(ANDROID_CONTROL_AE_TARGET_FPS_RANGE,
|
||||
aeFpsTarget.data(), aeFpsTarget.size());
|
||||
entry.data.i32, 2);
|
||||
|
||||
value = ANDROID_CONTROL_AE_PRECAPTURE_TRIGGER_IDLE;
|
||||
found = settings.getEntry(ANDROID_CONTROL_AE_PRECAPTURE_TRIGGER, &entry);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue