[OSC_dev] Managing different osc implementations

[salsaman at xs4all.nl]

On Fri, February 20, 2009 11: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.
>
> 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?
>

This is also a goal of open media control:

http://openmediacontrol.wetpaint.com/

However, despite the fact that many people _claim to be interested in
this_, debate there seems to have died off...

If we could agree the major points, then it would be a fairly simple
matter for any application to implement it.


Regards,
Salsaman
http://lives.sourceforge.net