tuio

Hey everybody, II was wondering if anybody had any suggest on how to utilize the Kinect in TuioKinect. My big big problem is that if i run synapse( synapsekinect.tumblr.com/‎) to get the video in qc it's all ok, when i try to use recent patches that i find on the web or the sample patch for see the kinect in qc (open kinect) or TuioKinect i don't see nothing or message No kinect/device connected. From my research on the forum, i read that probably th problem is the model of my kinect ( I'm running this off my macbook 10.7.5 - kinect model n.1473) Any suggest? i'm really really really tired of this situations! thxs

Greetings Kineme,

I have been developing some nice looking compositions for a 50" PQ multitouch surface, tons of fun and super easy to work with in quartz.

So far I have just been using particle systems with static images as the input to create multitouch effects but when I use a video input all the particles have the same movie position.

Hopefully there is a way to use iterators, sample and hold, and billboards to spawn videos with unique play positions (I don't think I worded that well). In other words, you press your finger down, a video plays at that position and stays there until it is done playing, meanwhile more of the same clip can be spawned around the composition, each instance starting from the beggining and playing to the end.

I doubt I am the first to attempt this and any guidance is greatly appreciated.

Thanks in advance!

I have been using the new TUIO apps for both the iOS and Android. Alone they are great, but when I connect them in combination, the one port (3333) cannot handle both at the same time.

So I am wondering if there is a way to change the port that Quartz is listening to, so you could have multiple devices connect with one application or host computer.

Since TUIO and OSC are related, I used the stock oscreceiveing patch to listen to port 3333 and the received signal would flash when the device was touched. Using the qcOSC plugin from hexler I saw that a packet was named /tuio/2Dcur, within there were 2 structures that I could get to: one was a string that said "fseq" and the other was a counter that would only increase when the pad was touched.

I then changed the Tuio settings from the device to "not send full updates" which gave me /tuio/2Dobj and /tuio/2Dbib - both of which gave nothing but a string - but still a lead.

So perhaps the source of the tuioclient plugin could be changed?

Or is there a way to dig deeper into the structure listed on the receiving OSC patch?

Thanks for any clues

http://code.google.com/p/tuiodroid/ http://code.google.com/p/tuiopad/

Hi there monsters! :) I've been reading this lovely forum since 3 months ago and now I feel to get started posting my problems and hope I will have your lights through my way.. I'm going to have this fiducials have visual feedbacks,so I started from the very basic steps... The problem I have right now is how to make each Fiducual ID separated for different visual feedbacks? I'm guessing to use structure thingies but imagine me as a noob person both in coding and QC.. cheers