summaryrefslogtreecommitdiffstats
path: root/camera/docs/docs.html
diff options
context:
space:
mode:
Diffstat (limited to 'camera/docs/docs.html')
-rw-r--r--camera/docs/docs.html9
1 files changed, 5 insertions, 4 deletions
diff --git a/camera/docs/docs.html b/camera/docs/docs.html
index d898729..bda9616 100644
--- a/camera/docs/docs.html
+++ b/camera/docs/docs.html
@@ -32898,10 +32898,11 @@ start-of-exposure time.<wbr/></p></span>
<tr class="entry_cont">
<td class="entry_details" colspan="6">
<p>The accuracy of the frame timestamp synchronization determines the physical cameras'
-ability to start exposure at the same time.<wbr/> If the sensorSyncType is CALIBRATED,<wbr/>
-the physical camera sensors usually run in master-slave mode so that their shutter
-time is synchronized.<wbr/> For APPROXIMATE sensorSyncType,<wbr/> the camera sensors usually run in
-master-master mode,<wbr/> and there could be offset between their start of exposure.<wbr/></p>
+ability to start exposure at the same time.<wbr/> If the sensorSyncType is CALIBRATED,<wbr/> the
+physical camera sensors usually run in leader/<wbr/>follower mode where one sensor generates a
+timing signal for the other,<wbr/> so that their shutter time is synchronized.<wbr/> For APPROXIMATE
+sensorSyncType,<wbr/> the camera sensors usually run in leader/<wbr/>leader mode,<wbr/> where both sensors
+use their own timing generator,<wbr/> and there could be offset between their start of exposure.<wbr/></p>
<p>In both cases,<wbr/> all images generated for a particular capture request still carry the same
timestamps,<wbr/> so that they can be used to look up the matching frame number and
onCaptureStarted callback.<wbr/></p>