28 Jul
2004
28 Jul
'04
8:47 a.m.
On Tue, Jul 27, 2004 at 11:34:48AM -0600, martin rumori wrote:
On Tue, Jul 27, 2004 at 12:33:56PM -0400, Paul Davis
wrote:
do you mean the sdk distributed by berkeley? if you're speaking about
libOSC++ from stetson university (part of the wiretap project), it
doesn't wrap the berkeley thing. when using the "fraunhofer" branch
from cvs, it comes with some classes wrapping the unix network stuff
(UDP and TCP).
if you don't need bundles, I'd go with liblo, cause it's really
lightweight.
I agree. Thought its now really only the API thats lightweight, the code
is growing a bit :(
- Steve
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.