Live data from Hacker News

Ableton Extensions SDK

ableton.com

51–60 of 104 posts

Re: Ableton Extensions SDK

#51

Wish we could get some native compatiblity with Linux. The closest I've gotten on NixOS was with Bitwig, with a simple compatability script I wrote: https://github.com/ArikRahman/Nixwig

For the Push 3 standalone they have ported Live to Linux, but it’s confined to their own hardware.

> The challenges were many: we had to create an operating system, we needed to deal with porting Live to Linux, we needed to deal with all the gory details of WiFi and authorization.

https://www.ableton.com/en/blog/the-evolution-of-push/

Re: Ableton Extensions SDK

#52

Earlier quoted context omitted.

Please say more

Yeah. How does ableton handle the transfer? Do you mail them the transfer request, they generate a new key and mail it to the new owner?

They describe it here: https://help.ableton.com/hc/en-us/articles/209771405-Buying-...

Re: Ableton Extensions SDK

#53

Wish we could get some native compatiblity with Linux. The closest I've gotten on NixOS was with Bitwig, with a simple compatability script I wrote: https://github.com/ArikRahman/Nixwig

For the Push 3 standalone they have ported Live to Linux, but it’s confined to their own hardware. > The challenges were many: we had to create an operating system, we needed to deal with porting Live to Linux, we needed to deal with all the gory details of WiFi and authorization. https://www.ableton.com/en/blog/the-evolution-of-push/

I'd probably be ready to shell money for another studio license if they could just make that version available to us plebs that run Linux on our desktop computers. There is basically just 2-3 programs left to have running on Linux for me to finally be able to uninstall Windows, Ableton being one of them.

Re: Ableton Extensions SDK

#54

>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.

I would imagine nearly every programmer who has ever used a DAW has thought “this would be cool to have its own scripting language.” They already had Python. Mentioning an architecturally obvious idea in a job application is likely to read as insulting, because it presumes their engineers weren’t already aware of that possibility.

> Mentioning an architecturally obvious idea in a job application is likely to read as insulting, because it presumes their engineers weren’t already aware of that possibility.

That's a bit much no, why would it be insulting? "Great minds think alike" would be my reaction, instead of "Ew, duh, of course we thought of that, you think we stupid?".

Re: Ableton Extensions SDK

#55

For people into this sort of thing, another option is using my foss Max extension, Scheme for Max, to script Live through the live API using Scheme. https://www.youtube.com/watch?v=j0sKBA-Pv2c&t=1s The live object model is MUCH nicer to use in a lisp, as basically you do everything by making dynamic lists to represent what you want to access! There are examples in the Scheme for Max help file. (Also, Scheme for Max c…

I need to check this out, I bounced off Max 3 times now because I find the GUI approach so tedious

Max itself can be manipulated through JavaScript. You can dynamically create and connect objects in it, set scheduler tasks, etc. Max goes a lot deeper than wiring some GUI boxes together.

Have a dig around here: https://docs.cycling74.com/apiref/js/

Re: Ableton Extensions SDK

#56

Wish we could get some native compatiblity with Linux. The closest I've gotten on NixOS was with Bitwig, with a simple compatability script I wrote: https://github.com/ArikRahman/Nixwig

Bitwig 6 works out of the box on NixOS unstable.

Re: Ableton Extensions SDK

#57

I hate max so much. I wish this could extend to the push 3, I've been working on an orchid clone. It would be TRIVIAL in any other language, but noooo, I have to write a fucking max patch and deal with their trash visual syntax and runtime.

The visual patching part of Max makes sense when you know the history of the program. It was built for musicians working at the forefront of interfacing MIDI with the power of the more compact mainframe computers of the day (PDP-11 IIRC). The 'programming' was done through a GUI running on the first Macintosh. At first there was no audio processing in Max itself, it was purely for generating and manipulating MIDI data.

You can see this 'bare-bones' style of Max with Miller Puckette's continuation of his original work in Pure Data[1] (aka Pd). The nice thing about Pd is that it's open source, so all the scheduling and signal flow logic can be examined and understood. As I understand it, the basics of Pd are comparable to how Max still works under the hood, though no doubt there has been some deviation over the years.

As it is now, Max offers a very smooth interface to the basic paradigm that was established 40 years ago, with many modern advances, but the fundamental idea hasn't changed all that much since it first came out.

If you really hate having to work through a GUI for computer music there's always SuperCollider[2] and its many derivatives (Sonic Pi, TidalCycles, etc.). It's nice to have options!

[1] https://msp.ucsd.edu/software.html

[2] https://supercollider.github.io/

Re: Ableton Extensions SDK

#58

I spent my day hacking on this to see what it’s capable of (built a simple little tool that displays MIDI clips as sheet music: https://github.com/madisonrickert/ableton-sheet-music-extens... ) My initial take on its strengths/weaknesses: - Strong: Using the TS/JS ecosystem to render UI and tools - Medium: Creating custom application windows in a web view. Window management features are pretty limited currently (can’…

Thank you! If I’m reading your findings correctly, this is focused on UI capabilities, and likely rides on top of the existing Live Object Model (LOM) rather than a new integration.

Which is a bummer, because LOM is fantastic for what it does, but has many many many frustrating gaps. Like, it cannot add devices to the master/main track. It can’t read MIDI pitch bend events, etc.

Re: Ableton Extensions SDK

#59

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!

We should talk - I'm building a new DAW with this in mind :)

We should talk - I’m building a Claude Code plugin for music composition and analysis, which currently integrates with Ableton using MCP and Ableton control surface (basically LOM) and an M4L patch. But it could easily work with any DAW that has the right primitives.

Re: Ableton Extensions SDK

#60

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 could see this being something that AI takes a bite out of in the coming years 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

IMO it’s going to work the other way around. I’m doing my best composition ever using LLM coding tools that just use Ableton as a rendering engine.
Post reply on HN