Hi there,
I finally got a Client for TUIO in BlitzBasic/Blitz3D working.

After checking the code provided in Thread http://nuigroup.com/forums/viewthread/6165/ I did some research by myself and began from scratch.

It’s quick and dirty, so many functions the OSC provides are not implemented, but the TUIO-Stuff works.

I encountered some problems though:

- Why do i have to swap x and y coordinates for CCV?
- Sometimes, when i touch a certain point on the screen, bytes are missing in the stream (?)
- Maybe caused by the previous problem, the touches near the edges of the screen aren’t properly displayed

Is someone able to help?

What do you guys think? I attached the file below.

Greets,
miLORD

Hot Dang! Beat me to it! :D
Thanks so much for posting!

For an answer to question/problem #3 --> In CCV for some reason when you touch near the edges it will send out 0,0 or bad coordinates… I have no idea why but I remember reading this somewhere on the forums.

Thanks again!

Are you checking the code and develop it as well, or are you just using it?

If you develope: Is german okay for you? I commented on all the things in german - i can change it to english if you want me to.

EDIT: Oh and thx for answering that question!

Greetz,
miLORD

Update:

I now added paket\active and ID_number.

paket\active shows how many times the paket has been set. If it is 1 the paket is completely new.
Above it, the blob was dragged or held and therefore existed before the current frame.

ID_number is the number of all currently active pakets.

And the whole thing is optimized for including now, it’s no standalone anymore. But you can easily set up your own frame-program.
I attached a sample below.

Hope it helps,

miLORD

P.S.: Sorry for double-posting

I’ve found out why I was getting some weird results in this.... You have it set to receive Y and then X coordinates from the stream but as you can see from the TUIO protocol specification, (http://www.tuio.org/?specification), the OSC message is sent in the order of X and then Y. This gave me a good laugh after wondering for about 2 hours why I was getting a blob nowhere near my finger!

Anyway, thanks for taking this a step further, adn I do intend to use it if I can. Thanks again miLORD!

Hi hillbilly,
that’s really weird, because - as i wrote above - i had to swap X and Y coordinates to get proper results :D
Suppose my cam’s just weird… it’s a fairly old model anyway…

Sorry to cause this problem

In the next update i’ll change the language to english.

Take care!
miLORD

hmmm.... strange nevertheless, this works for me. Now to develop!

Does it work all the time?
I encountered problems with some cursorpositions, wich is a problem when dragging things like rects around my screen…

Have fun, and keep me up to date about all the beta-testing.
You’re my only tester so far

Thanks in advance,
miLORD

well what happens is when you get towards the center, the positions are normal, and acurate but then as you move towards the sides or bottom, they get a bit off.. This could be because sf my camera’s unbalanced position though, I don’t know. But, I have calibrated with CCV so I don’t think that my camera’s unbalaced position has anything to do with it…

Nope, it doesn’t.

That’s why i’m totally NOT happy with the client so far.

- Still the edge-issue, the whole sensing area seems to have moved a bit on display and/or has some kind of fishlens-effect?!?!?
- Still the errors where not enough bytes are sent

Check the Debug-Console, there are the errors listed in detail. At certain points i get “set failed: not enough bytes”, same for fseq.
As a result, there are sometimes “Wrong adress"-failures as well. These occur often like that:

#bundle ...(all that stuff) BUT ONE BYTE MISSING so that the next adress is tuio/2dcur instead of /tuio/2dcur

so the wrong adress-failure is called.

Why the bytes are missing? Beats me, i haven’t found out yet.

miLORD

hmm… I really don’t know… but anyway, a temporary way to maybe solve this would be to divide (scale) the positions by multiplying by like .96 or something and then center them. But remember, only temporary… -_-

Well, I repositioned the webcam in my table today and it’s fairly straight so I went to CCV and ran and calibrated and then back to Blitz and the blobs are nearer than when I had my webcam slightly tilted to the left. So the whole thing revolves around the positioning of your/my webcam; if it’s not in the center, the blobs will be off-target.