Max, kinect and animata

edsonedge's icon

I am using the windows SDK and this OSC program: https://github.com/BanTheRewind/KinectOsc

... and the patch below to control a skeleton in Animata

My problem is that the skeleton I get in animata is all mangled up and I assume it is because of how my patch is built (I know it is no masterwork btw :) _ I am wondering if anyone has tried to do something similar and - maybe someone has a patch that they have used with animata?
- or if someone can point out to me what is wrong with my calibration in the patch

Max Patch
Copy patch and select New From Clipboard in Max.

All the best

Luke Woodbury's icon

Probably best to do the scaling yourself rather than with f0.auto_scale. What is coming out of KinectOSC? Not used it but possibly it uses screen coordinates and Animata uses pixel co-ordinates, so you would need to scale 0. 1. to 0 640 and 0. 1. to 0 280, but just guessing...Maybe KinectOSC has option to send screen or pixel co-ords?

Luke Woodbury's icon

Out of interest, why are you going through Max anyway? Personally I use Osceleton to send Kinect generated OSC straight to Animata. It has the option to send in screen or pixel co-ords (which Animata uses) and you can add an offset and filters too. If you are tracking a single user then Synapse is good and if you particularly want to do this in Max and you are on Windows then maybe check out jit.openni.

edsonedge's icon

The reason is that I am using the windows SDK drivers, and Osceleton works with the OpenNi drivers

Last time I checked you can´t have both sets of drivers installed?

For my money the windows SDK drivers are more comfortible to use because you don´t need to wait for the kinect to calibrate to a the arms up position like with Nite and openNI

Scaling 0. 1. to 0 640 and 0. 1. to 0 280, sound like a likely explination - Ill check that out - and Ill discard the autoscaling

Thanks alot :)

Luke Woodbury's icon

I understand, but you still don't need Max to send OSC straight from KinectOSC to Animata? There might be a reason if KinectOSC only uses screen co-ords, but your patch could be a lot simpler in that case.