I made a quick demo of using the kinect.

http://www.youtube.com/watch?v=xd4lIJzzYCM

Dueyftw, thank you very much!

We have added link to this video to the Quick Start Guide:
http://ipisoft.com/en/wiki/index.php?title=Quick_Start_Guide_with_MS_Kinect_Sensor

Dueyftw, you must be very patient for 10 seconds per frame is all I can say :)

I know you referenced your slow graphics card but I get between 0.4 to 0.6 seconds per frame with a GTX 460.

I have a new computer with 6 cores and a 460, just haven't set it up. It uses two power supplies. I lost my work space in my friends cellar because it a duplex and I scare the other tenet. The 6 camera system is better than the kinect, you have more freedom of movement. Went I get another work space I'm wondering how much trouble would have two computers going at once, one capturing with PS3 cameras and the other using a kinect. You could have one in a semicircle with an actor and another actor facing a kinect in between the PS3 cameras. Or two kinects at 90 degrees on two computers so IR light crossed each other and the actors facing each other sort of.

Ah, you'll enjoy the other PC experience much better :)

How would you sync the data though? I don't have a spare PC for capturing the second, nor can I see any benefit directly?

What I am curious to try is having two actors with the Kinect and as long as they don't intersect, see if it can do two at once.

Here is what I'm taking about. The left is having PS3 cameras (gray) and having one Kinect in side the PS3 cameras. As long as the actor dosent block the PS3 cameras this should work. On the right is two kinect cameras. They shouldn't interfere with each other. Nether setup will allow the actors to face each other, but the timing of the motions capture should match.




Each capture could be render separately on a third machine while you do your recordings. Here is where batch rendering come in handy.