Ableton Extensions, AI Coding & Sound Design with dnksaus
Producer and Max for Live developer dnksaus joins the podcast to explore Ableton Extensions, AI-assisted workflow building, and the creative techniques behind his unconventional sound design approach.
Producer, Max for Live developer, and sound designer dnksaus (Carter) sits down to dig into one of the most significant additions to Ableton Live in years: the new Extensions feature. Alongside that, Carter shares how AI-assisted coding has changed the way he builds custom tools, why finishing music requires better creative habits, and what unconventional workflows actually look like in practice.
What It Does
Ableton Extensions, currently in beta as part of Live 12.4.5, allow producers to install custom workflow scripts directly inside Live via a new Extensions tab in Preferences. These files, saved in the ABLX format, can be built by anyone and activate through context menus throughout the application. The possibilities range from simple utility tools to deep integrations with external algorithms and neural networks.
Carter has been building extensions rapidly using Claude Code for AI-assisted JavaScript generation. His approach: conceptualise an idea, describe it to the AI, and have a working extension inside 15 minutes. He has already built tools that shuffle drum pad sample positions, clear unused pad samples before sending a project for collaboration, and generate new drum clips by recombining MIDI from all of Ableton’s stock packs. None of these were previously achievable through Max for Live alone.
Beyond his own builds, Carter and the host also discuss notable community extensions including Basic Pitch (Spotify neural network powered audio-to-MIDI conversion for polyphonic detection), Theory Aid (harmonic analysis of your project MIDI with chord function explanations), and Yoink (direct YouTube audio download straight into the Live timeline). The ecosystem is growing fast, and the creative ceiling is not yet in sight.
How to Use It
- Install an extension: Go to Ableton Live Preferences, open the new Extensions tab, and select your ABLX file to install it. Installed extensions appear listed and can be uninstalled from the same panel.
- Activate in context: Extensions live in context menus throughout Live depending on what they are designed to act on. Right-click on a drum rack, a clip, or a track to find relevant extensions.
- Build your own with AI: Carter uses Claude Code to vibe code extensions in JavaScript. Describe the workflow you want clearly, reference what you know about Ableton’s Extensions API, and iterate on the output until it behaves as expected.
- Clean up drum rack bloat: Use an extension that reads which pad samples have been played in the arrangement and deletes everything unused before you collect and save. This keeps project folders lean when collaborating.
- Generate drum patterns from stock MIDI: Extensions can pull from all of Ableton’s built-in clip MIDI data and recombine it to produce new patterns. Pair this with the sound similarity search to find matching samples quickly.
- Use community extensions: Search for tools like Basic Pitch for improved audio-to-MIDI, Theory Aid for harmonic analysis, and Yoink for pulling reference audio directly from YouTube into your session.
Why It Matters
Max for Live remains the gold standard for deep, reliable device building inside Ableton Live, and Carter is clear that AI vibe coding does not replace it. What Extensions do is lower the barrier for workflow-specific automation that producers have wanted for years but could not justify the development time to build. The combination of a new API, AI-assisted coding, and a growing community sharing ABLX files means that custom Ableton workflows are no longer reserved for experienced developers. Carter’s work, alongside developers like Sidebrain and the broader community already sharing extensions publicly, points toward a version of Ableton Live that producers can genuinely shape around how they actually work rather than adapting to how the software works by default.




