[nedt]

The have it buried in the FAQ, but that's pretty much the interface for AI. And a really good one. You can use it with just your old human intelligence, but then you can also get help if coding isn't your thing.

Biggest issue with having something so easy to work with is the huge amount of extensions we will be getting, which makes it harder to find the jewels.

Also wondering if we will get extensions for Abelton Move as well. There are already a couple of hacks that are adding functions that are running as a sidecar. This could give them an official API.

[coldtea]

>The have it buried in the FAQ, but that's pretty much the interface for AI.

Well, they have it buried because it's not "the interface for AI", it's a programming interface, that could have existed 5 and 10 years ago, pre-AI. And in other DAWs, it did.

It just happens that a programmatic interface is also very usable as an AI target. But that's orthogonal.

[nedt]

Yes of course. But then they wouldn’t be the first to create APIs, SDKs or CLIs as an enabler, because of AI. Which is why I‘m even more happy that it isn’t just a MCP.

[_def]

Got some links to the Move hacks?

[_def]

Answering my own question: schwung.dev

Also: yes, this SDK is a great interface for AI. It was trivial for Claude to quickly write a MCP extension. There is a lot of room to open up the API more and to save on tokens, but I already had fun sketching out new songs or open older projects with clips in session view and just tell Claude "create an arrangement out of them".

[nedt]

Yes Schwung is now the best. There is also the extending-move repo on github which has some documentation in the wiki. From time to time I look into the Abelton move reddit.