Merge pull request #49583 from wes-b/patch-1

Device Timestamp is always Center of Exposure

Author: ktoliver

articles/kinect-dk/multi-camera-sync.md

@@ -25,7 +25,7 @@ There are many reasons to use multiple Azure Kinect DK devices, including the fo
    Additional synchronized devices can provide the occluded data.
 - Scan objects in three dimensions.
 - Increase the effective frame rate to a value that's greater than 30 frames per second (FPS).
-- Capture multiple 4K color images of the same scene, all aligned within 100 microseconds (μs) of the start of exposure.
+- Capture multiple 4K color images of the same scene, all aligned within 100 microseconds (μs) of the center of exposure.
 - Increase camera coverage within the space.
 
 ## Plan your multi-device configuration
@@ -70,9 +70,6 @@ If you want to control the precise timing of each device, we recommend that you
 
 In the image capture loop, avoid repeatedly setting the same exposure setting. Call the API only one time when it's needed.
 
-#### Timestamp considerations
-Devices that are acting in master or subordinate roles report image timestamps in terms of *Start of Frame* instead of *Center of Frame*.
-
 #### Avoiding interference between multiple depth cameras
 
 When multiple depth cameras are imaging overlapping fields of view, each camera must image its own associated laser. To prevent the lasers from interfering with one another, the camera captures should be offset from one another by 160μs or more.