Need a little QC guidance...

[Nico Danger]

Hey there,

Can anybody offer me a little advice doing something that is probably super easy?

I'm trying to translate kinect X/Y/Z points into VDMX via a QC patch. I have Synapse up and running and I have installed the Tryplex toolkit. So I am seeing data from torso, head, etc.

Basically I want to turn these points into data that VDMX can interpret. Can somebody with more QC knowledge than I offer any advice?

Thanks!

[Nico Danger]

Okay so I have managed to get Kinect's OSC data routing into QC via Hexler's qcOSC patch. I am seeing a skeleton's worth of points coming up in the patch. What I can't figure out how to do is publish them as outputs so I can use this as a plugin in VDMX. I tried simply publishing the outputs and saving the file in the folder. It comes up in the plugins window and I can create it but then nothing happens.

I am so close to using kinect skeleton points as data sources.... unless I am totally wrong?

[Nico Danger]

Figured it out. Quartz was not the answer. I've got Kinect points feeding into VDMX via OSC. If anyone's interested I can explain how...

[AVicious]

Definitely interested. Please explain.

[Nico Danger]

I actually ended up ditching QC altogether. If you run Synapse and the supplied MaxMSP app "quartz_passthrough_plus" you should be able to see incoming OSC data in b8 if you listen on port 12348. A simple Comm Display plugin should show you what you're getting (Synapse must be tracking a skeleton for this to work obviously).

What I then did in b8 was to create a control surface with sliders for whichever skeleton points you want to use (i.e. 'left hand X,' left hand y' etc). In the UI inspector you should be able to create a new data source for each slider. Be sure to name it exactly what the incoming OSC data reads as (/OSC/lefthand_pos_screen for example). Then set the slider range so that it covers the whole range of values you're getting (0 to 600 for the horizontal, 0 to 400 for the vertical seems to be working). The pos_screen values are structures so you'll need to unpack them by selecting which member you want to listen to (0 for X, 1 for Y and 2 for Z).

The control surface plugin is an extra step here but I found it useful. If you wanted to you could simply select a given OSC structure and assign it to control whatever you want.

Planning on using this for a tour in February... Exciting!

[Dub Prack]

thanks a lot! its work very well...

[lefty]

Anyone able to talk me through using osceleton and VDMX?

[lefty]

Ok. I've got synapse to send to VDMX. I need a patch or adaptation for the pass through to send body relative messages. I'm workin on it, but has someone solved it?

[Dub Prack]

hey lefty, you need synapse and the max patch “quartz_passthrough_plus” (in the synapse download web page, in the Quartz Composer example project + plugins (Mac only) link). This patch send the data from synapse to vdmx
cheers
m

synapse download
http://synapsekinect.tumblr.com/post/63 ... 1/download

[myngus]

Hi,
I bought the Kinect,
running synapse,
running the maxMSP Passthrough plus plugin.
....
not sure what you men by "Synapse must be tracking a skeleton for this to work obviously".

I pretty much know nothing about the kinect. Can someone explain this to me please?

cheers,

[myngus]

don't worry about replying to that one. I guess I should have read the instructions....
DOH!!!!

[myngus]

Hi Nico,
got the data coming onto VDMX.
How do I "unpack" the structures so I can use each x,y and z value?

cheers,

[rybotron]

I think this might be helpful:
viewtopic.php?f=25&t=7030&p=25432#p25432

Download the attachment and there is a VDMX file with the custom controller built in VDMX.