Azure Kinect cameras
Azure_Kinect_camera.tox
Layer: sensing
In: none
Out: one TOP per sensor
This component gives the live image streams of the lab's three Azure Kinect sensors as TouchDesigner TOPs, one per sensor. It is for work that uses the camera image itself, such as live video in a projection, image analysis, or material for compositing. Skeleton data is not included: for body positions, use Azure Kinect sensors.
Role in the setup
The camera and the sensor component use the same hardware, but they keep image and position data apart. The camera's TOPs normally go to image processing and then to Wall projection or Floor projection.
Technical specification
- Source. The video comes from the Azure Kinects calibration as NDI streams, one per sensor (
<host> (AK1),(AK2),(AK3)), and not from the workstation itself. This spreads the processing load: the high-bandwidth camera streams do not compete with rendering on the workstation. The component lists the NDI sources it finds on the network when the project starts. - Viewpoint. The sensors are mounted on the ceiling grid, so all images are high-angle views looking down into the room.
- Stream selection. Image sets which stream is delivered (for example colour). The choice is sent to the host as an OSC broadcast (UDP 27), and the host switches what it publishes. Other stream types the sensor provides, such as depth or infrared, can be selected here if the host publishes them.
- Outlets. There is one outlet per sensor in a fixed order (1, 2, 3), which matches the physical sensors. To find out which outlet is which corner, wave at a camera.
- Resolution and frame rate are set by the sensor and the stream configuration, not by the component. Fit or resample downstream to match the target resolution of a projection component.
Parameters
| Parameter | Function |
|---|---|
| Image | the stream delivered (colour, …) |
| Configure | rebuilds the outlets after Image changes |
Outputs
- Outlets 1–3: one TOP per sensor, in fixed order.
- Recommended convention: attach a named
nullto each outlet (null_cam_left,null_cam_right, …).
Limitations and expected behaviour
- Black or empty outputs: you are not in the lab, or the sensors are off.
- All views look alike: they show the same empty room from different corners.
- No change after switching Image: press Configure.
- Unexpected resolution or frame rate: this comes from the sensor or stream. Use a Fit TOP or resample downstream.
- Privacy: these are identifiable camera images. When recording or passing on material from public sessions, you need visitors' consent.
Relations
- → Wall projection, Floor projection (via your own image processing)
- ← Azure Kinects calibration (NDI images)
- ↔ Azure Kinect sensors (same sensors, position data)
- Hardware: Inventory (the installed sensors, and other cameras available in the lab)
References
- User README: Azure_Kinect_camera-README
- Repository: <https://github.com/SpatialComputingL/Td-updates>
- Overview: Lab Tools