Kinect and Processing - coding and set up.

I've figured that to achieve my projection idea is to use a Kinect, hence my earlier post on how it works. I've had trouble with admin rights and permissions with the university computers, so I've borrowed a Kinect from my tutor to take home with me and try it out on my own pc, which runs Windows 7. I also referred to Daniel Shiffman's guide to configuring the device to suit Processing. I had a friend, who works at Lockwood Ltd as a coder, help and take me through this. Didn't take him long to figure out Processing, which I was surprised to hear he had no awareness to.

For future references, this is basically what I've done to get the two working together:

1. Installed the Kinect-for-Windows SDK and Developer Toolkit applications - first and foremost thing one needs to do in order to install the hardware properly

.

2. Set up the necessary codes and sources/libraries OpenKinect - a few problems arose out of this, like the imported library SimpleOpenNI which didn't work at first, and compatibility issues between different versions of Processing itself, which were already factors of Mac vs. Windows. but luckily, said friend from Lockwood

3. Set up the pixel and depth resolution settings for the Kinect on Processing.

4. Translated the Processing sketch to the Kinect.

So far, so good; albeit a few brain farts and headaches. A lot of what I had to do now was to build the screen, source the projector and set it all up in a space I've organised at Trent.