Image

I got OSC support working now (using the TUIO protocol). Pictured above is one of the TUIO reference apps. You can grab the code from the google code touchlib repository. Or if you want to try the bins, get them here:

Touchlib Bins

That way you can run touchlib without having to compile it. The OSC app is currently hard coded to use port 3333.

Is anyone else experiencing runtime errors quite frequently (and randomly)?  Sometimes as soon as it starts up, sometimes it seems to be fine.  I’ve only had it crash running the OSC app (although i’ve only quickly tested out the other apps)

Also Flosc seems to crash using touchlib osc too… it runs ok for about 10 seconds then crashes.  Doesnt seem to crash using VVVV

C:\multitouch>java -classpath . Gateway 3333 3000
Attempting to start OSC / Flash Gateway server
OscServer created…
TcpServer created…
Exception in thread “Thread-0” java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at Bytes.copy(Bytes.java:243)
at OscServer.parseOscPacket(OscServer.java:125)
at OscServer.run(OscServer.java:71)

Ah seems you can solve my problem by changing some flosc code

In IRC i made out i figured this all out by myself, but infact i emailed the Flosc creator

yep… you need to increase the size of the memory allocated in OscServer.java

look for the line that defines:

byte[] datagram = new byte[1024];

and increase that number until it’s big enough to hold the packets you want to send.  i will probably increase this to 4k in the upcoming release.  i was concerned about memory use when i coded this, but it turns out to not matter at all.

Ah great news Joobs! Yeah 1024 bytes is not very much I wonder if I should divide my packets up more - I’m not sure what the best way to do it is.

I seem to be having a similar problem, random crashes that seem to be linked to too much camera movement. Is there some sort of maximum number of blobs that the OSC app can handle before it fizzles out?

I am NOT using flosc

does that message appear when there are 8 or more blobs on screen?

White has corrected that error, but hasnt released the binaries of it for some reason… if you compile yourself using the latest files then it should go away.  or ask white to release the newer binarys.

I get a memory error when it close it though.

ah ha, interesting. I bet that’s what it is. I’m kind of a C++ newbie and I’ve been unable to compile touchlib so far. I’ll give it one last shot and if all else fails I’ll ask for newer binaries.

Thanks for the quick reply!

WhiteNoiz - 12 February 2007 09:13 PM

Image
The OSC app is currently hard coded to use port 3333.

Ok I just fixed that (I hope ).

When starting OSC you must specify an IP address and Port number.

example: OSC.exe 127.0.0.1 3333

Binaries + Sourcecode are attached

WhiteNoiz: Perhaps you could update the SVN with this version?

*you might need to install the vs2k5 redist. when using my compiled binary

great job falcon. I tested it out and it works locally, i will let you know how the dual computer test goes. Perhaps we can try over the net soon as well. I just about have all the neccesary software together to make changing the software possible. Hopefully I can get that going soon.

tnx for the effort, but it kinda sux to have to specially download another program to use this actual program, hopefully somebody can make a version that doesnt need the vs2k5 redist.

xwolf told me that this problem lies in the fact that it’s dynamically compiled.
by statically compiling it you’ll solve the problem.
this is just a matter of a checkbox in the compiler vs2k5

so if u’d be so kind to recompile it and then post it again, that would be very much appreciated.

Thanks Falcon, it’ll be in the next release.

Hi guys,

I have tried using touchlib at night and during daytime.

I find that the datagram gets quite big and causes java.lang.ArrayIndexOutOfBoundsException especially during the day time.

OSC will eventually crash as well say in about 2 minutes if I dont change anything in configapp.

So what am I missing? In terms of finetuning the Threshold etc.... Or filters?

Its a known fact that OSC and flosc cant handle too many blobs at one go.

hi Armage.

I’ve augmented the datagram packet size up to 16384 (initially was 4096). I’ve also made default OSC port 3333. If anybody could check it’s datagram’s size I’ll be pleased to know so I can check and fix it.

Actually, increasing the datagram is easy adhoc solution right.

It also means that, the applications will have a likelihood to slow down if there are too many blobs (has to go through osc, flosc, flash right?). What we call noises.

Just a thought, maybe we can:
1. Limit the number of blobs by doing some checking.
a) By size (Diameter)
b) Speed? If there is any in touchlib

As for the type of filters. This need to understand and investigate further…

What I encountered is using my reading lamp to shine into the camera. And that is enough to crash touchlib and flosc. I mean shouldn’t the reading lamp be considered as one blob?