[linux-audio-dev] OSC for GUI-Engine communication

[Steve Harris]

On Wed, Jul 28, 2004 at 01:36:37PM +0100, Dave Griffiths wrote:
> I've written a system like this myself, where the GUI/audio code passes token
> value pairs between them where the tokens are strings (ie "FilterCutoff") and
> the values are floats (or strings). It's pretty simple.
> 
> The audio engine can be requested a text description of all the tokens it
> accepts, and this includes hints such as ranges, which the GUI side uses to
> build an interface from.
> 
> This interface code is all scripted in python, so you can throw all the
> graphics away and run it manually on the commandline. As the text descriptions
> are all human readable, they can be used as a help file for what controls are
> availible.
> 
> Should I be using OSC? What are the advantages? Would it enable my engine to
> be accessed by more clients? Are people writing software where the only
> interface is via OSC?

Probably. OSC is starting to get widely used, and it saves having Yet
Another RPC Protocol. It would be accesible by more clients, eg. Pd,
Supercolider and csound can all use OSC. I think that SC only uses OSC for
communications, but I'm not sure.

- Steve