OSC

What are the thoughts about the various QC OSC implementations?

I'm familiar with:

-the stock OSC patch. It seems like this has some issues with truncating floating point values, and whatever happens to data when it drops values sometimes (I haven't observed this much... does anyone know more about this patch's potential issues?).

-qcOSC - It looks like this has been updated recently. This one's pretty cool, because of the "auto listening", but it seems to have problems when working in apps sometimes(?). Is there source available on this?

-BBOSC - Not much personal experience with this. I gather there are issues with it running multiple instances?

-OSC Tools (Mansteri) - this looks like it's not really general purpose, and just a sender maybe (no receiver)?

I have a variety of questions:

Has anyone tested any of these for leaks when running a custom app, tested what happens with multiple instances, etc? Do all of them support structures? Which have source available? Are there any I'm missing from this list?

I'm gathering there are some conflicts in multiple patches both using VVOSC framework(?). Can anyone clarify which patches? Do they both use the same version of the VVOSC framework?

BBOSC.plugin (1.0.1-FIXED) https://github.com/jdelStrother/BBOSC and

MnstriOSCTools.plugin (1.0) http://mansteri.com/software/

cannot run together!

When i try this, QC crashes with the error message:

(null) EXCEPTION IGNORED: +[QCPlugInPatch executionModeWithIdentifier:]: Inconsistent state

May this be caused by the same underlying Framework VVosc?

Fortunately, both plugins are open source. Unfortunately, i do not know how to fix this issue.

Could somebody be so kind to help me out, or hint me to way, how one would need to recompile from source, so that this problem can be avoided?

Background: I duly need the fabulous BBOSC receiver (because it handles utf8) AND (since BBOSC sender works only in one singular instance) i do depend on the Mansteri OSC Sender as well.

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/

I'm trying to make run together Iannix (http://www.iannix.org) with QC through OSC. I have 20 elements in Iannix which sends their ID, X and Y position every 20ms under the same adress: /cursor cursor_id cursor_x cursor_y. The aim is to represent the 20 elements at the same time, queueing the structure and passing to an Iterator I got 1 element which jumps between the positions, I tried also with JS Smooth from here: (http://kineme.net/forum/Discussion/DevelopingCompositions/Smoothingcoord...) but not desired result is obtained. Any idea?