[OSC_dev] Application Profiles

[adrian at cnmat.berkeley.edu]

>
> The CNMAT objects for MaxMSP have been pretty much dead since Max 4.6,
> and are certainly dead in Max 5, replaced by built-in UDP/OSC objects,

whoa there. CNMAT objects are very much alive in Max5 - OSC related ones
and all the other
in our increasingly large Max/MSP Depot.
> so it's not very surprising that there's not much support effort for
> them. OSC-route still sees some use, but that's basically string
We use them extensively and respond rapidly to problems, but are not a
commercial
support-offering outfit.
> manipulation and Max has many other ways to achieve that.

I think you may be confusing Max objects that transport OSC packets. We
gave our OSC independent Open Transport
ethernet object source code to Cycling74 so they could create better
ethernet support when OS/X introduced a new threading model.
You can use their new TCP/IP stuff or the Java TCP/IP objects in max.

We have recently created objects like slip-OSC and the soon to be renamed
mc.usb to provide robust USB transport of OSC messages.

We recently fixed overdrive related bugs in the OpenSoundControl object
and have reported numerous performance-related bugs in Max 5 to Cycling74
revealed by our recent high-performance OSC applications.

Our uOSC effort is a source of free source code for a compact OSC
implementation.

Look out next year for reference  implementation and specification of OSC
1.1 in Max/MSP