(reproduced please specify the source)
Using the SDK: Kinect for Windows SDK v2.0 1409
Come, Microsoft officially released the SDK v2.0 on October 22, the precursor is that the API document is found to be normal ...
Say why it's 1409, not 1410.
From this section, we begin to attach hyperlinks to the API. The official version of the volume is also considerable, a full (more than the July version) is one times larger
This section says the software that comes with it, Ben intended to record it, but it's too lazy.
With Microsoft's own address, part1,part2, this is gesture, although using C #, the tool is used exactly the same.
First look at the tools that come with the SDK:
0. Kinect V2 Configuration Verifier
A checking tool, like this one, says my USB bandwidth may be too small, but it doesn't seem to be a problem.
1. Kinect Studio
This is the most important tool that features:
Monitor Kinect
Recording files
Play file
Recording needs to be noted, it is recommended not to record color frames, Microsoft said it is 120MB per second ... I can't keep up with my hard drive, my soul is weak.
Playing the file is a very handy way to debug, after connecting to the Kinect service, allowing for a very IMBA feature that is not available with Kinect ,
Allow breakpoints, stepping, and debugging Kinect depends on it.
2. Visual Gesture Builder
visual gesture Builder, preceded by a video address, a build tool. features are:
Training (Build a viewing database file)
Analysis (Check the wrong)
3. Kinect Studio Utility
Operation of the files generated by KS, no more.
4.Visual Gesture Builder Viewer
Gesture frame that section of our imitation made one, nor say much
The main thing is to say KS. playback file Debugging and VGB usage
Kinect for Windows SDK v2.0 Development Note (16) SDK2.0 official release with own tools