kinect-mssdk-openni-bridge Supplemental Diagrams Tomoto Shimizu Washio Rev 1: 9/5/2012

Kinect SDK SensorKinect Driver and K4W Driver cannot coexist OpenNI FW NITE Avin2’s SensorKinect Problem Image Node User Node OpenNI App Depth Node KinectSDK App Image Depth SensorKinect Driver K4W Driver Image Stream Depth Stream Skeleton Tracker Image Depth Skeleton User ID User ID+ Skeleton

Kinect SDK OpenNI FW NITE Bridge Bridge alters SensorKinect by providing OpenNI’compliant nodes that wrap Kinect SDK, so OpenNI/KinectSDK apps can coexist Bridge Solution Image Node User Node OpenNI App Depth Node KinectSDK App K4W Driver Image Stream Depth Stream Skeleton Tracker Image Depth Skeleton User ID User Node Kinect Studio.xed Image User ID+ Skeleton Depth

Bridge Solution (cont.) App can apply NITE’s algorithms (e.g. User node) upon Bridge’s Depth node App can also use Kinect SDK’s skeleton tracker through the User node bridge provides ◦ Use “query” on User node creation ◦ Bridge’s User node works by itself but requires no depth node ◦ App can use both User nodes at the same time if needed Compatible with recording/playback with Kinect Studio ◦ Kinect Studio is totally transparent within Kinect SDK

OpenNI FW NITE Kinect SDK Bridge Recorder can apply on bridge’s Depth and Image node ◦ So XED -> ONI conversion is possible ONI Recording Image Node User Node OpenNI App Depth Node UserID+ Skeleton K4W Driver Skeleton User ID User Node UserID+ Skeleton Kinect Studio.xed Recorder Image Stream Depth Stream Skeleton Tracker Image Depth Image Depth.oni

Kinect SDK OpenNI FW NITE Bridge does not do anything with ONI playback ◦ Kinect SDK’s skeleton tracking cannot be applied on ONI ONI Playback User Node OpenNI App Bridge User Node ST Mocks Depth Node Image Node Depth Node Image Node DS IS K4W Driver Skeleton User ID Depth Image Player Image User ID+ Skeleton Depth.oni

Misc Audio node is supported ◦ Wrapping DMO Device node is supported ◦ App can choose one of multiple connected Kinect Sensors ◦ Kind of hack, not perfect