Will Marshall, an advanced OSCulator user, has been kind enough to share a template he created with OSCulator 2.9 that (amongst other things), sends the track names to TouchOSC controls. To make this work, he created a custom layout in the TouchOSC editor, a set of OSCulator files, and a virtual control surface script for Live.
If you want to learn about how to use this template, or just get inspiration to create one yourself, watch the video on his blog (better viewed on vimeo, actually).
Rishabh Rajan, an artist from Malaysia, has used Quartz composer to extract augmented reality controller values and send them via OSCulator to a Buffer Override plugin in Logic:
There is also this captivating Wiimote composition he made using the FM8 synthesizer:
A new public beta has been released that solves a bunch of annoying bugs and brings some new features.
In the Parameters Window, there is a new option to turn off TUIO protocol interpretation. The TUIO protocol is used with multitouch software and provides information on the tracked objects. OSCemote and MSA Remote are two examples of iPhone applications that implement this protocol.
Here is a video that basically shows the reacTIVision software analysing the video input, sending TUIO data to OSCulator, which in turns controls Ableton Live:
The TUIO protocol itself is not very easy to use out of the box and is not directly compatible with the way OSCulator triggers events. The solution to this problem has been to implement a kind translator that would interpret the protocol and convert it into something more user friendly. The benefits of this is the possibility to use TUIO messages very easily, however some users reported that they would also want to see in OSCulator the raw TUIO data, unmodified.
TUIO uses a single message (for example /tuio/2Dobj), but with varying arguments, of different types like numbers and strings. Until now, OSCulator was only able to receive input from numbers, but since version 2.9, it is able to receive any OSC data type. If the TUIO protocol handling is set to “Raw & Interpreted”, this means OSCulator will display both the original TUIO message /tuio/2Dobj, but also the interpreted ones.
This brings the possibility to process the messages in OSCulator, and also forward the TUIO data to another software or computer, which is very handy since most TUIO clients can not send their data to multiple destinations at once.
The extended OSC data type support made it possible to simplify the OSC Routing editor as well.
