[LAU] modular audio apps and control-communication was: off topic

Chris Wenn christopher.wenn at gmail.com
Wed Sep 2 22:32:29 EDT 2009


On Thu, Sep 3, 2009 at 12:24 PM, Paul Davis <paul at linuxaudiosystems.com>wrote:

> On Wed, Sep 2, 2009 at 10:10 PM, Patrick
> Shirkey<pshirkey at boosthardware.com> wrote:
> > So I guess they wanted things to be as tightly integrated as possible for
> > performance reasons?
>
> i had some extended conversations with one of ableton's founders about
> this, and he talked about it in one of my classes at the TU.
> basically, they wanted to tap into the "max crowd", however you
> interpret that, which they felt that Live currently didn't do. they
> saw/see a lot of skill and cool stuff going on with max that can't be
> done in Live. their idea seems to have been to try to integrate that
> as tightly as possble into Live, so that people who create cool max
> patches can use them as if they were builtin processing objects in
> Live. not "max connected to Live" (which is already possible with
> JACK, and they know it). at present, there is no "distribution" system
> for those patches, but that didn't seemed to be ruled out for the
> future.
>
>
That's the impression I got from the situation - they recognised that a
significant portion of the Max userbase were either already using Live +
Soundflower + Max (or some other kludge) or were interested in
interoperability.

This market seems pretty tightly pegged to the Apple platform. At least here
in Oz, Max users tend to pick it up at university, where there's pretty high
saturation of Apple hardware.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20090903/2cd990b5/attachment.htm 


More information about the Linux-audio-user mailing list