When using touchlib74 with PureData (pureDataTUIOclient), it works fine,
PureData is receiving the full info :
(update,addCursor ,RemoveCursor session_id xpos ypod angle xspeed yspeed maccel)

While using versions 2.0 & rev359, Pure Data is only receiving : addCursor_id and removeCursor_id .

Has the transmission of those datas been removed in the newest version of Touchlib ?
Do you have any explanation or clue for this particular problem ?

Below the PureData print from the TUIO client .
/Pd version 0.39.3-extended-rc5
---------------------------------------------------------------------------------------------
Touchlib74 :
print: updateCursor 328 0.778321 0.829246 -0.00180173 0.004471 0.00482038
print: addCursor 328
print: removeCursor 328

Touchlib rev 359 and Touchlib 2.0:
print: addCursor 46
print: removeCursor 46

They have not been removed. It’s possible that the format for sending them has changed. I’m a PD user, so I’ll see if I can look into this and get an answer for you soon.

Is that print directly from the outlet of the TUIO object? Are you trying to unpack the messages from osc objects in PD or are you using the reactivision TUIO object?

Are you able to compile touchlib itself? It looks like in osc.cpp, we added height and width sending. That may be affecting how the TUIO object in PD is working. I would try removing those parameters so it looks like:

p << osc::BeginMessage( “/tuio/2Dcur” ) << “set” << d.ID << d.X << d.Y << d.dX << d.dY << m << osc::EndMessage;

instead of

p << osc::BeginMessage( “/tuio/2Dcur” ) << “set” << d.ID << d.X << d.Y << d.dX << d.dY << m << d.width << d.height << osc::EndMessage;

That would make the send message the same to what it was in v74.

Thanks for this quick answer,Flying CAT.
This is very clear answer.

i’m using the Reactivision TUIO client.
Do you mean by using osc object, i could avoid this problem…

I am not able to compile Touchlib yet (i’ve been trying to ...i am still a JimiDummy)

Heh, no problem.

No, stay with the Reactivision TUIO client. It’ll be too messy to use the OSC messages directly. I’ll see if I can compile a version for you that you can test and let me know if it works. If it does, in order for the reacitvision TUIO client to work in PD, the TUIO client would need to add a part for height and width receiving.

I’ll get back to you later tonight or tomorrow hopefully.

Great!!!

I will try that tomorrow as soon as i come back from work.

jimihertz - 27 March 2008 03:47 PM

When using touchlib74 with PureData (pureDataTUIOclient), it works fine,
PureData is receiving the full info :
(update,addCursor ,RemoveCursor session_id xpos ypod angle xspeed yspeed maccel)

While using versions 2.0 & rev359, Pure Data is only receiving : addCursor_id and removeCursor_id .

Has the transmission of those datas been removed in the newest version of Touchlib ?
Do you have any explanation or clue for this particular problem ?

Below the PureData print from the TUIO client .
/Pd version 0.39.3-extended-rc5
---------------------------------------------------------------------------------------------
Touchlib74 :
print: updateCursor 328 0.778321 0.829246 -0.00180173 0.004471 0.00482038
print: addCursor 328
print: removeCursor 328

Touchlib rev 359 and Touchlib 2.0:
print: addCursor 46
print: removeCursor 46

How can I generate PureData print from TUIO client ?
I need TUIO emulator and have PureData print saved to a file to feed swf client
to test resolution and response time of webcam blobs recognition.