On 3 Feb 2006, at 19:10, matt wrote:
> in this vein, why are there so many mac-only externals, patches,
> etc.? why isn't max/msp components compatible across all platforms
> by now?
- Max was Mac-only for, what, fifteen years? A lot of externals go
back a long way, in terms of source code and compiler options, even
if they have been recompiled for PPC and OS X. (True, for instance,
of my registry object, which I wrote about ten years ago; that's
680x0 to PPC, OS 9 to OS X, and THINK C to Symantec C++ to
CodeWarrior to XCode (almost).)
- Some of us don't have Windows machines. (I only have one now
because the gallery for which we're doing a media installation is a
Windows-only shop.) I have no use for a Windows machine, and I'm
still waiting for somebody to pay me to buy one and port my externals.
- These days I'm doing all my externals, or "heavy lifting" code for
Max/MSP, in Java. This is cross-platform by default (assuming an
absence of careless coding involving filenames) and for non-
pathological examples has performance close enough to conventional
compiler output to make "going native" with development pretty much
So much for externals. What Mac-only patches have you come across?
nick rothwell -- composition, systems, performance -- http://