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:
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.
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 :)
i used libOMC [which is the old library "upgraded" to be buildable again] in RunMotherfuckerRun player (http://www.artm.org/). it's available here: http://www.piksel.no/pwiki/OpenSoundControl
it wasn't maintained since around piksel gathering (nov 2003)... oh, and i'm afraid i have fixed some bugs on artist's offline machine and never brought the sources back to piksel site. the fixes made it compatible with Max/MSP's OSC objects (half of the installation is a max patch running on a mac). if Steve's interested i could find it.
i believe veejay uses it's own OSC implementation (probably based on the same old implementation but i'm not sure). you could use it to test liblo.
we are considering to start using liblo as "piksel-approved" osc implementation instead of libOMC.
and afaik there are OSC objects for PureData. i was testing earlier versions of RmR with PureData coz i don't have a Mac myself. So it was compatible with those as well.
finally, some of our (http://lab.v2.nl/) artistic hardware speaks OSC over bluetooth, but it's irrelevant coz there's always only one last prototype ;-)
