Skip to main content

Skeleton Music - Music with the Kinect

I have started messing about with the Kinect again. Finally! Mr Randall, our head honcho at North 51 kindly supplied us with a company unit so we can begin messing about with it.

I am hoping that once the holiday period dies down we can begin to really start thinking about genuine applications.

At the moment it's just a case of reminding myself of the mechanics of how it works. I thought I would once again take one of the examples that comes with the SDK and just toy with it.

I fancied a little peek at NAudio (I have been watching an Audio course on Pluralsight) so I got NAudio back out again.

The project is to create a music generator based on the location of the hands according to the kinect sensor. It also changes amplitude depending on your distance from the device.

I reallly like the way you can get a hold of the location points of the skeleton with the Kinect SDK. Once you have the skeleton getting the hands is as simple as             

var leftHand = skel.Joints[JointType.HandLeft];
var rightHand = skel.Joints[JointType.HandRight];

Anyway, take a look at the code, it's in GitHub https://github.com/DominicFinn/MusicSkeleton

The code is far from fantastic but it's just a scratchpad of fiendery (as are all my Github projects, my nice projects are private on BitBucket... I don't do things for free, I have a family to feed!).

Comments

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second