Skip to content

Commit f34c765

Browse files
committed
Line break fix
1 parent c4c8bd8 commit f34c765

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This article introduces some of the benefits of synchronizing multiple devices,
2020
There are many reasons to use multiple Azure Kinect DK devices. Examples include the following:
2121

2222
- Fill in occlusions. An occlusion occurs when a foreground object blocks the view of part of a background object for one of the two cameras. In the resulting color image, the foreground object appears to cast a shadow on the background object. Although the Azure Kinect DK data transformations produce a single image, the two cameras (Depth and RGB) are actually a small distance apart. The offset makes occlusions possible.
23-
For example, in the following diagram, the left camera sees the grey pixel "P2." However, the white foreground object blocks the right camera IR beam. The right camera has no data for "P2."
23+
For example, in the following diagram, the left camera sees the grey pixel "P2." However, the white foreground object blocks the right camera IR beam. The right camera has no data for "P2."
2424
![Occlusion](./media/occlusion.png)
2525
Additional synchronized devices can fill in the occluded data.
2626
- Scan objects in three dimensions.

0 commit comments

Comments
 (0)