hello to all of you,
first of all I’d like to present myself, my name is Martin Kaltenbrunner, I am one of the developers of TUIO, reacTIVision and the reacTable.
I didn’t yet participate too much in your community, but I am glad to see that our protocols and software has been adopted widely here.

You might be interested in the latest release of reacTIVision, which finally makes the reactable’s multi-touch feature available to the public.
Along with this 1.4 prerelease that joins multi-touch and fiducial tracking within a single application,
I also prepared a series of new TUIO clients, which provide a more powerful and convenient API, such TuioObject and TuioCursor references,
that are automatically updated by the client, as well as the introduction of an alternative polling interface.
At the moment I already finished the C++, Java, C# and Processing clients, Pure Data and Max/MSP are soon to follow.
There will be also some new clients for VVVV and Quartz Composer available soon.

This release contains also an updated and improved version of the TuioSimulator,
which fixes quite a few bugs and is a bit more compact than the 1.3 version.
most importantly it implements a few tricks for multi-touch simulation.
see the readme and help menu for more detailed instructions.

you can find all necessary information about reacTIVision, TUIO and the TUIO example clients on the project page:
http://reactivision.sourceforge.net/

best wishes,
Martin.K

welcome Martin !

great to have you here ,

a lot of NUI members wants to include multi touch and fiducials in the same table .

1/ Could you explain us the multi touch function in Reactivision .

2/ Are you using fiducials with FTIR ?

hello again,
I will try to explain a bit how the finger tracking is implemented in reacTIVision:

our application was primarily designed for fiducial tracking, so the thresholder
and after all the segmenter are very much tailored for that use.
in order to introduce the finger tracking without any additional overhead, I am actually just
using the region data of the segmenter itself rather then adding another image processing step.
in the end I am only comparing any white region of a given size with a white circle, calculating the error.
if the difference is small enough, reacTIVision takes it as a finger ...

1/ Could you explain us the multi touch function in Reactivision.

so basically reacTIVision tracks any round white blob as a finger.
you can adjust the average size and the sensitivity in an individual setting.
this should work fine with FTIR setups and it works also with diffuse illumination
as we do it in the reacTable. FTIR of course will work better due to the cleaner image,
which helps to reduce false positives. But from my experience with the reacTable,
the tracking performance with the DI variant is also very robust.

2/ Are you using fiducials with FTIR ?

no, if you want to use the fiducials, this will only work with DI.
FTIR does not illuminate the marker symbols at all, at least I do not
know about a trick how this could be done. but as I said above DI is good enough,
just make sure you have strong diffuse IR lights and a matte lower surface to avoid reflections.

best,
Martin.K

Thanx Martin,
It’s nice to see the 1.4 release is finally there and it’s great to see you participate on this NUI forum…

Welcome & greetings from SOCO Amsterdam

hai martin. welcome, i wanna of you fans, lol. right know im using gg_viz from tangible laptop for client graphic feedback.
i wanna ask you few thing.
1.how a good setting of reactivision for reactable(im still using xml for midi), what synthetizer? reaktor?
2. please can u share us your graphical visualisation binary/and source(please ). right now using tangible laptop just can have link to one id.
3.how is a reactable good setup (camera, the circle table setup, diffuser, etc)
i really wanna build the same as on the video(reactable)
give us a clue!!

hello ruly,

1.how a good setting of reactivision for reactable(im still using xml for midi), what synthetizer? reaktor?

I am quite surprised that so many people are using the MIDI mode, I basically made it for a friend when he asked me if it were possible to use reacTIVision with Ableton.
For these kind of audio applications the MIDI mode is of course the most convenient way to communicate, but as I state on the reacTIVision page, MIDI is much more
limited regarding bandwidth and resolution compared to TUIO (OSC).
As the synthesizer you can use whatever you want, I cannot recommend anything in particular.
This choice probably only depends on your instrument design, programming abilities and musical taste I would say.

2. please can u share us your graphical visualisation binary/and source(please ). right now using tangible laptop just can have link to one id.

We are committed to open source with the publication of reacTIVision, TUIO and all related tools and examples.
And we are happy to see that these technologies are widely adopted and that we were able to make the topic of “tangible interaction” available to a larger community.
On the other hand we have no plans to release any other part of the reacTable as open source software in the near feature.

3.how is a reactable good setup (camera, the circle table setup, diffuser, etc)
i really wanna build the same as on the video(reactable)

This is should be probably discussed somewhere else in another thread.

best wishes from Chicago,
Martin.K

Hello Martin , i’d have a question about the reacTable.What is the resolution of the camera that you are using?
And i’d like to thank you and your team for making Reactivision and the whole reactable package open source and free to download and distribuite.

Hello Martin K.

Its really an honor to have you in the community…

And from our communities heart we give out a THANK YOU!!! for you and your teams INVALUABLE work.

We have been able to leverage your standards and thus accelerate development and thought processes.

Open standards and vision for a better future

Any news on TUIO 2.0?

hey nuiman,
well I am happy to be here, although I am quite busy lately
so don’t be surprised if I disappear again for a while ...

Any news on TUIO 2.0?

after the final release of reacTIVIsion 1.4 I am planning to reshape reacTIVision quite a bit,
most importantly adding a few new features which will require some updates to the TUIO protocol.
these updates include features such as finger IDs and pressure amongst others.
I am also planning to introduce another “plain” object type, that describes size, shapes, skeleton
and the oriented bounding box of “blob” objects on the surface.

I was thinking how I could maintain some kind of backwards compatibility,
but due to some other shortcomings of our way we used OSC so far,
I think it will be best to create a completely revamped TUIO2 using its own name space.

It probably won’t take long until I will publish a first draft on our TUIO page,
which of course will be open to discussion and proposals from your side.

http://reactable.iua.upf.edu?tuio

actually the current document you can find on that page, shows the actual TUIO specification
without all the stupid errors that we made in the original document.

best,
Martin.K