27 Jul
2004
27 Jul
'04
2:48 p.m.
I'm writing an audio engine that will communicate
with the outside world
exclusively via OSC (and perhaps MIDI, but I digress..) It's much more
generic, but for the sake of argument let's say the engine is a synth
and it needs to talk to a GUI.
I need realtime appropriate performance for parameters, and two-way
communication (though the synth -> GUI is really simple and not
performance critical - error reporting etc.)
so lets just say thats its basically identical in all gross ways to
jesse chappell's latest incarnation of sooperlooper, which uses OSC to
connect an out-of-process GUI to the sooperlooper jack client engine,
and also does MIDI->OSC bridging from an ALSA sequencer port. it works
great. it uses liblo.
The question is, which implementation is best? All I
can find is
Steve's liblo, libosc++, and the 'official' OSC kit. What are the
afaik, libosc++ just wraps the sdk distributed by stanford. and that
sdk is just a total nightmare. the 2nd worst code i have ever
read. use liblo.
--p