Vysil Microsoft Kinect Tools - Personal Project

This is one of my top personal projects and also at the same time the longest project ever. The reason why I say it's the longest project ever, it's because it took me up to 6 months to get it done, normally I try my best to get a project done in 1-2 months tops. I will tell you my journey on how I got started on this personal project and also how you can make it your self.

What is the "Kinect Tools" and what does it do?

The Vysil Kinect Tools connects to the Microsoft Kinect and takes control over the Kinect. After it has done this, I then use a SDK offered by Microsoft which allowed me to grab information in and out from the Kinect. For example, the most basic function is telling the Kinect to move up and down. This particular SDK I'm using can be run on Visual Basic, C++, and C#. The Vysil Kinect Tools is programmed in Visual Basic, and this limits some of the functions I could do with the Kinect. Some other cool functions are bone movement, resolution settings, and basic a basic video camera. Don't forget the voice command, which did wonders for me when I had to test the software. 

How can I make my own Kinect software?

Lets get started with a quick checklist on how you can get started. You will first need to the following items.
1. Kinect Sensor
2. USB AC Power Adapter Supply Cable Microsoft Xbox 360 Kinect Sensor
3. Microsoft Kinect SDK 2.0 (C++ / C# / VB.net )
Now that you have all those major and required items, you can get started on this adventurer to make your own software. Keep in mind I'm not about to guide you step by step on how to make it, but don't worry! Microsoft did a wonderful job by making tutorials.
Get Started->http://www.microsoft.com/en-us/kinectforwindows/develop/learn.aspx

Now that you have enough tools to get started on your own Kinect software. Keep in mind it's not going to be easy, and I don't recommend this to a beginner. Also at the same time, this does not mean a newbie wont be able to make their own software, it just means that they might not understand what is going on. If you can't understand what is going on, you wont be able to make your own "custom" software or add your own additional tools into the software.

That is the software, I designed the GUI in Photoshop, and during this time I called it a "Remeir" production. Remeir is nothing really, it a small graphics company I was working on back when VysilHq started.

I usually answer this question "Why not release it to the public?" and the answer is simply because it's would be too much work for one developer. You have to keep in mind for me to make a ready product for market, it had to offer value to people. For example, only other programmers would use it for open source purposes, other than that I would have to make it record / track user movement! At the end of the day, it was a fun project and if I had to do it again I would!