ACameraCaptureSession_logicalCamera_captureCallbacks

#include <NdkCameraCaptureSession.h>

This has the same functionality as ACameraCaptureSession_captureCallbacks, with the exception that an onLogicalCameraCaptureCompleted callback is used, instead of onCaptureCompleted, to support logical multi-camera.

Summary

Public attributes

context
void *
onCaptureBufferLost
onCaptureFailed
onCaptureProgressed
onCaptureSequenceAborted
onCaptureSequenceCompleted
onCaptureStarted
onLogicalCameraCaptureCompleted
This callback is called when an image capture has fully completed and all the result metadata is available.

Public attributes

context

void * ACameraCaptureSession_logicalCamera_captureCallbacks::context

onCaptureBufferLost

ACameraCaptureSession_captureCallback_bufferLost ACameraCaptureSession_logicalCamera_captureCallbacks::onCaptureBufferLost

onCaptureFailed

ACameraCaptureSession_captureCallback_failed ACameraCaptureSession_logicalCamera_captureCallbacks::onCaptureFailed

onCaptureProgressed

ACameraCaptureSession_captureCallback_result ACameraCaptureSession_logicalCamera_captureCallbacks::onCaptureProgressed

onCaptureSequenceAborted

ACameraCaptureSession_captureCallback_sequenceAbort ACameraCaptureSession_logicalCamera_captureCallbacks::onCaptureSequenceAborted

onCaptureSequenceCompleted

ACameraCaptureSession_captureCallback_sequenceEnd ACameraCaptureSession_logicalCamera_captureCallbacks::onCaptureSequenceCompleted

onCaptureStarted

ACameraCaptureSession_captureCallback_start ACameraCaptureSession_logicalCamera_captureCallbacks::onCaptureStarted

onLogicalCameraCaptureCompleted

ACameraCaptureSession_logicalCamera_captureCallback_result ACameraCaptureSession_logicalCamera_captureCallbacks::onLogicalCameraCaptureCompleted

This callback is called when an image capture has fully completed and all the result metadata is available.

For a logical multi-camera, this callback also returns the result metadata for all physical cameras being explicitly requested on.

This callback will always fire after the last onCaptureProgressed; in other words, no more partial results will be delivered once the completed result is available.

For performance-intensive use-cases where latency is a factor, consider using onCaptureProgressed instead.

Note that the ACaptureRequest pointer in the callback will not match what application has submitted, but the contents the ACaptureRequest will match what application submitted.