11–20 of 104 posts
Far too much of Ableton's secret sauce is hidden away behind Max for Live and top-tier pricing only features. This is a great step in the right direction.
I've often felt as though the way to make a DAW that competes with Ableton today would be to build the entire UI around composable scripted modules. Far too much of Ableton's secret sauce is hidden away behind Max for Live and top-tier pricing only features. This is a great step in the right direction.
i've been making my own vst instruments and effects with faust, and codex knocks it out of the park; it's basically a trivial task
the only problem is that i have to use software that's external to DAWs. it's only a matter of time before this is first class in DAWs
I've often felt as though the way to make a DAW that competes with Ableton today would be to build the entire UI around composable scripted modules. Far too much of Ableton's secret sauce is hidden away behind Max for Live and top-tier pricing only features. This is a great step in the right direction.
Ableton and Max are totally separate codebases, and "Max for Live" is just a ~VST interface between them.
I do agree that "scriptable Ableton" would be far better for production and sound design than Max, because they make all the hard parts easy: MIDI, sequencing, mixing, etc.
In Max, you have to build everything from scratch, every time.
A couple of times I've tried somewhat seriously to build "google docs for ableton" (meaning two people editing the same project on different computers, seeing each other's edits in realtime). Frustratingly I decided it was impossible to do a really good job of it back then. This sounds like it might finally make it doable!
I've often felt as though the way to make a DAW that competes with Ableton today would be to build the entire UI around composable scripted modules. Far too much of Ableton's secret sauce is hidden away behind Max for Live and top-tier pricing only features. This is a great step in the right direction.
The other way around. Ableton exposes some internal modules to Max for Live as Max for Live modules.
What Ableton gets from Max for Live is not internals, but basically a few Ableton-only Max-built plugins, that could as well use VST underneath.
>Extensions are built on the NodeJS platform, a free, open-source, cross-platform JavaScript runtime environment. I applied for a job with them and proposed this exact thing about 8 years ago (got auto-rejected, I would've been very happy to work on it). But I'm glad to see they finally did it.
You could already use Node through M4L. I'm not clear on what this adds that wasn't already possible.
Ableton Extentions if a first class api to Live, kind of like AppleScript.
I've often felt as though the way to make a DAW that competes with Ableton today would be to build the entire UI around composable scripted modules. Far too much of Ableton's secret sauce is hidden away behind Max for Live and top-tier pricing only features. This is a great step in the right direction.
There is zero "secret sauce" in max for live. Ableton and Max are totally separate codebases, and "Max for Live" is just a ~VST interface between them. I do agree that "scriptable Ableton" would be far better for production and sound design than Max, because they make all the hard parts easy: MIDI, sequencing, mixing, etc. In Max, you have to build everything from scratch, every time.
I don't own Max for Live. If I want to use it, I either need to upgrade to Ableton Suite for $500 or I need to upgrade to Standard and buy Max for Live separately (also $500).
There's a huge ecosystem of tools that are implemented as Max for Live packages which I cannot access because I haven't paid the toll.
I see that even this new Extensions SDK is only available to people who have paid for the full Suite edition.
I'd describe that as a market opportunity.
This is just what I've been looking for. I never warmed to Max for Live for mods. But the extensions SDK I can get behind.