summaryrefslogtreecommitdiffstats
path: root/camera/docs/metadata_definitions.xml
diff options
context:
space:
mode:
Diffstat (limited to 'camera/docs/metadata_definitions.xml')
-rw-r--r--camera/docs/metadata_definitions.xml9
1 files changed, 5 insertions, 4 deletions
diff --git a/camera/docs/metadata_definitions.xml b/camera/docs/metadata_definitions.xml
index 28b7afe..ca35e8d 100644
--- a/camera/docs/metadata_definitions.xml
+++ b/camera/docs/metadata_definitions.xml
@@ -11280,10 +11280,11 @@ xsi:schemaLocation="http://schemas.android.com/service/camera/metadata/ metadata
<description>The accuracy of frame timestamp synchronization between physical cameras</description>
<details>
The accuracy of the frame timestamp synchronization determines the physical cameras'
- ability to start exposure at the same time. If the sensorSyncType is CALIBRATED,
- the physical camera sensors usually run in master-slave mode so that their shutter
- time is synchronized. For APPROXIMATE sensorSyncType, the camera sensors usually run in
- master-master mode, and there could be offset between their start of exposure.
+ ability to start exposure at the same time. If the sensorSyncType is CALIBRATED, the
+ physical camera sensors usually run in leader/follower mode where one sensor generates a
+ timing signal for the other, so that their shutter time is synchronized. For APPROXIMATE
+ sensorSyncType, the camera sensors usually run in leader/leader mode, where both sensors
+ use their own timing generator, and there could be offset between their start of exposure.
In both cases, all images generated for a particular capture request still carry the same
timestamps, so that they can be used to look up the matching frame number and