You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/kinect-dk/multi-camera-sync.md
+19-39Lines changed: 19 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -149,58 +149,38 @@ If you're connecting the devices in the star configuration, you also need one he
149
149
1. Connect 3.5-mm audio cables to the "split" ends of the headphone splitter.
150
150
1. Plug the other end of each cable into the **Sync in** port of one of the subordinate devices.
151
151
152
-
## Calibrate the devices as a synchronized set
153
-
154
-
In a single device, the depth and RGB cameras are factory calibrated to work together. However, when multiple devices have to work together, they need to be calibrated in order to determine how to transform an image from the domain of the camera that captured it to the domain of the camera you want to use to process images.
155
-
156
-
There are multiple options for cross-calibrating devices. Microsoft provides the [GitHub green screen code sample](https://github.com/microsoft/Azure-Kinect-Sensor-SDK/tree/develop/examples/green_screen), which uses the OpenCV method. The Readme file for this code sample provides more details and instructions for calibrating the devices.
157
-
158
-
For more general information about calibration, see [Use Azure Kinect calibration functions](use-calibration-functions.md).
159
-
160
152
## Verify that the devices are connected and communicating
161
153
162
-
To verify that the devices are connected correctly, use [Azure Kinect Viewer](azure-kinect-viewer.md).
154
+
To verify that the devices are connected correctly, use [Azure Kinect Viewer](azure-kinect-viewer.md). Repeat this procedure as needed to test each subordinate device in combination with the master device
163
155
164
156
> [!IMPORTANT]
165
157
> For this procedure, you need the serial number of each Azure Kinect DK.
166
158
167
-
**To verify a daisy-chain configuration**
168
-
169
-
1. For each subordinate device in the chain, follow these steps. Start with the device furthest from the master device, and work back toward the master device.
159
+
1. Open two instances of Azure Kinect Viewer.
160
+
1. Under **Open Device**, select the serial number of the subordinate device that you want to test.
161
+

170
162
> [!IMPORTANT]
171
-
> To get precise image capture alignment between all devices, you have to start the master device last.
172
-
1. Open an instance of Azure Kinect Viewer.
173
-
1. Under **Open Device**, select the serial number of the device that you want to open.
174
-

175
-
1. Under **External Sync**, select **Sub**.
176
-

177
-
1. Select **Start**.
178
-
> [!NOTE]
179
-
> Because this is a subordinate device, Azure Kinect Viewer does not display an image after the device starts. No image is displayed until the subordinate device receives a sync signal from the master device.
180
-
1. After you have started all of the subordinate devices, open an instance of Azure Kinect Viewer and then open the master device.
163
+
> To get precise image capture alignment between all devices, you have to start the master device last.
164
+
1. Under **External Sync**, select **Sub**.
165
+

166
+
1. Select **Start**.
167
+
> [!NOTE]
168
+
> Because this is a subordinate device, Azure Kinect Viewer does not display an image after the device starts. No image is displayed until the subordinate device receives a sync signal from the master device.
169
+
1. After the subordinate device has started, use the other instance of Azure Kinect Viewer to open the master device.
181
170
1. Under **External Sync**, select **Master**.
182
171
1. Select **Start**.
183
172
184
-
When the master Azure Kinect Device starts, the synchronized image from each of the Azure Kinect devices should appear.
173
+
When the master Azure Kinect Device starts, both instances of Azure Kinect Viewer should display images.
185
174
186
-
**To verify a star configuration**
175
+
## Calibrate the devices as a synchronized set
187
176
188
-
1. For each of the subordinate devices, follow these steps.
189
-
> [!IMPORTANT]
190
-
> To get precise image capture alignment between all devices, you have to start the master device last.
191
-
1. Open an instance of Azure Kinect Viewer.
192
-
1. Under **Open Device**, select the serial number of the device that you want to open.
193
-

194
-
1. Under **External Sync**, select **Sub**.
195
-

196
-
1. Select **Start**.
197
-
> [!NOTE]
198
-
> Because this is a subordinate device, Azure Kinect Viewer does not display an image after the device starts. No image is displayed until the subordinate device receives a sync signal from the master device.
199
-
1. After you have started both subordinate devices, open an instance of Azure Kinect Viewer and then open the master device.
200
-
1. Under **External Sync**, select **Master**.
201
-
1. Select **Start**.
177
+
When you have verified that the devices are communicating correctly, you are ready to calibrate them to produce images in a single domain.
202
178
203
-
When the master Azure Kinect Device starts, the synchronized image from all of the Azure Kinect DK devices should appear.
179
+
In a single device, the depth and RGB cameras are factory calibrated to work together. However, when multiple devices have to work together, they need to be calibrated in order to determine how to transform an image from the domain of the camera that captured it to the domain of the camera you want to use to process images.
180
+
181
+
There are multiple options for cross-calibrating devices. Microsoft provides the [GitHub green screen code sample](https://github.com/microsoft/Azure-Kinect-Sensor-SDK/tree/develop/examples/green_screen), which uses the OpenCV method. The Readme file for this code sample provides more details and instructions for calibrating the devices.
182
+
183
+
For more general information about calibration, see [Use Azure Kinect calibration functions](use-calibration-functions.md).
0 commit comments