[OSC_dev] Managing different osc implementations

[Jamie Bullock]

On 20 Feb 2009, at 10:30, Mr.SpOOn wrote:

> Hi,
> I'm new to the opensoundcontrol world. I've just read some of the
> documentation about osc, but I've never tried anything in practice, so
> I don't really understand how it works, yet.
>
> I'm interested in developing some kind of musical interface, maybe
> with Processing, to put in sequence audio objects/events. The idea is
> not that simple, but doesn't matter here. What I'd like to do is
> something that can let me use different sound engines.
>
> I mean: if I can program with SuperCollider, I can make sounds with it
> and using them in this interface. But I'd like to have the same
> possibility with ChucK, or anything else that can produce sounds - as
> long as it supports osc communication.
>

This is one of the goals of libIntegra. Currently we only have  
'bridges' for Pd and Max/MSP, but SC3 and Chuck are high on our list.

> Does exist something similar?
> And what is the real problem? That every application (SuperCollider,
> ChucK, PureData etc.) that uses osc implements it in a different way?
>
> Would it be possible to write some sort of wrapper to manage all (or
> at least many of) the different implementations? Maybe some Python
> program put in the middle between the interface and the engine(s) to
> make them communicate in every case.

I suggest you have a look at our documentation:

http://www.integralive.org/dokuwiki/doku.php/screencasts
http://www.integralive.org/dokuwiki/doku.php/

It's very alpha at the moment, comments welcome!

best,

Jamie

--
http://www.jamiebullock.com