two kinects skeleton data

[ruigato]

I'm currently working on a theatre play, and using two kinects to track depth and skeleton data of 4 actors. everything is working, apart from the fact that i have to separate the kinects in different touch designer processes to get the skeleton data working on both, witch is, as Rod already pointed out well, a bit messy

any news on suppoorting both kinects skel data at the same time on the same td process?

i had to make also a figuring out session to get them both working, by trying different startup orders and usb ports, but once that done it seems to be stable enough..

will premiere tomorrow, let's hope all goes ok

cheers,
Gato

[malcolm]

I find it funny that that works with two processes. It's a limitation of the Kinect 1.0 SDK, and unless I'm wrong I don't think 1.5 expanded on this. Only thing you can do is email Microsoft and ask them to expand the SDKs limitation, they are actually pretty responsive if you email the blog authors.

[Achim]

if you at any point support skeletontracking across multiple kinects, it would be great if there was a "skeleton match" node that would keep IDs persistent across different kinects (via some kind of neirest neighbour search and/or maybe also via face tracking ). And a nice and easy way to calibrate multiple kinects into one single coordinate system

[ruigato]

right now is working with this setup;

fire touchdesigner process nº1 with kinect nº2 selected, and sending through shared memories the RGB image and the depth image; the skeleton data goes trough OSC out

fire the touchdesigner process nº2 with kinect nº1 selected, same output scheme

fire the touchdesigner process nº3 with the sharedmemory receives and OSC in, and generate geometry and image manipulation

anyway, just did a post on the KFW blog asking for the two kinect data stream support!


cheers,
Gato