Ableton Extensions SDK Adds ‘Experimental Playground’ To Live Suite

Ableton today introduced the Extensions SDK, described as “an experimental playground inside Live Suite”.

The Extensions Software Development Kit (SDK), now in public beta, is an open JavaScript toolkit that lets you create custom tools that expand what you can do in Live Suite.

Extensions are optional add-ons that run alongside Live and can be accessed with a right-click from anywhere in your Set. They can read and edit the structure of your Set – including tracks, clips, parameters, automation and more. Using the Extensions SDK, you can create tools that analyze, visualize, and reorganize your Live projects, automate repetitive parts of your process, connect Live to entirely new services and more.

The SDK is based on JavaScript, so it’s designed to be easy to get started, especially for people with previous experience with Web development.

Anyone can create Extensions under the Ableton SDK license. Live 12 Suite users can join the beta program and download the Live 12.4.5 beta to get started. See the intro video, embedded above, for a overview of developing your first Extension.

Availability: 

The Ableton Extensions SDK is available now as a free download.

9 thoughts on “Ableton Extensions SDK Adds ‘Experimental Playground’ To Live Suite”

  1. Live can’t remember what clips it played when you pressed save,
    instead of fixing it we get this, seriously is this a joke ?!?

  2. I wonder if this will finally make my midi controllers give proper LED feedback when I when custom midi mapping assignments, instead of guessing in the dark. e.g. try midi mapping any button on a Novation LCXL or an Arturia Keylab (in my case, mkII)… it sure would be nice to get straight-up conditional LED feedback. I’m watching this one closely… but not getting involved until I see some real user base and progress out there.

    Also I can’t help but think, this sounds quite a bit like Logic Pro’s “Environment,” but coming late to the party.

    1. That’s just for MIDI, seems it is equivalent to Live’s MIDI Effects (sit on Tracks, real-time FX), MIDI Transformations and MIDI Generators (aka MIDI Tools, sit on the MIDI Editor aka piano roll, non real-time editing), which are a subset of what Max For Live or Extensions SDK can do.

  3. This is big… Well depending on how it’s implemented. Will this finally make it possible to stop the cursor from jumping to the beginning of a part when you select it?
    Might actually start using Live 12 then.

  4. I wish it was a potential alternative for Max4Live, but it seems mainly for automating repetitive steps one might do like editing or reorganizing a project. There’s no real-time MIDI input, no MIDI routing, and no audio stream processing. The docs say “for MIDI routing or real-time MIDI manipulation, use Max for Live.”

Leave a Reply

Your email address will not be published. Required fields are marked *