Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 60d00de5 authored by Shuzhen Wang's avatar Shuzhen Wang
Browse files

Camera: Clarify interaction between aeTargetFpsRange and minDuration 

Test: Build
Bug: 294619809
Change-Id: I4f37380752c0da8cfd063d95f23af2eeba8aebdd
parent 8b6c71d7

camera/ndk/include/camera/NdkCameraMetadataTags.h

+6 −0
Original line number Diff line number Diff line
@@ -584,6 +584,12 @@ typedef enum acamera_metadata_tag { 
     * <p>Only constrains auto-exposure (AE) algorithm, not

     * manual control of ACAMERA_SENSOR_EXPOSURE_TIME and

     * ACAMERA_SENSOR_FRAME_DURATION.</p>

     * <p>Note that the actual achievable max framerate also depends on the minimum frame

     * duration of the output streams. The max frame rate will be

     * <code>min(aeTargetFpsRange.maxFps, 1 / max(individual stream min durations)</code>. For example,

     * if the application sets this key to <code>{60, 60}</code>, but the maximum minFrameDuration among

     * all configured streams is 33ms, the maximum framerate won't be 60fps, but will be

     * 30fps.</p>

     * <p>To start a CaptureSession with a target FPS range different from the

     * capture request template's default value, the application

     * is strongly recommended to call