31 Aug
2004
31 Aug
'04
2:08 p.m.
On Tue, 31 Aug 2004 16:02:43 +0100, Steve Harris wrote
On Tue, Aug 31, 2004 at 02:48:46PM +0100, Dave
Griffiths wrote:
Ah, OK. Well thats one more test, I tested liblo against the
original C implementaion when I started it, and after that against
itsself, but I get nervous about self tested software. I was never
sure the old C library was doing what its supposed to though,
couldn't get it to build on a modern machine, and the only binaries
I had were 4 or 5 years old :)
Well, everyone seems to be using liblo :)
BTW, if
you have reasonable OSC covereage I'd be very interested in
compatibility tests between whatever you're using and liblo.
Very early days, I've only implemented simple messages so far - but I'm using
liblo for my server and some python I've nicked for the client
http://cvs.sourceforge.net/viewcvs.py/pure-data/supercollider/python/OSC.py
Seems flawless so far though, and liblo's got a nice clean api. I like the OO-in-C style of programming, its pretty
much the best of
both worlds IMHO. C syntax, but no C++ 'features'.
Not mention the lack of a maze of twisty ABI's...
Just a quick side issue, I'm doing a lot of message passing - in and out of
OSC, and then through my own realtime fifo IPC layer thingy into the audio
thread of my application. Are there any standard libraries or ways of doing
this all in one go? I guess the last step is very application dependant...
dave