Skip to content

Latest commit

 

History

History

examples

README.md

LiveBridge examples

What it looks like when you make music in Ableton Live by talking to Claude. You only type the prompt; Claude picks the tools. Each page also shows the tool calls Claude makes, written as function calls, so you can see what happens in Live and learn the tools if you script Live yourself.

# Example You say Shows
1 An 8-bar house beat "Make an 8-bar house beat at 124 BPM…" drum patterns, presets from the browser, a bassline, chords, mixing in dB
2 Chords, bass and an arp that fit together "Write a melancholic lo-fi progression in D minor…" Roman numerals, arpeggios, a theory check that finds and fixes a clash
3 A Reese bass in Serum 2 "Load Serum 2 and design a dark Reese bass…" 120 Serum parameters without Configure, macros, an LFO on the filter
4 Splice samples straight into your set "Find a rolling hi-hat loop on Splice…" Splice's MCP server + LiveBridge: search, choose, download, import, warp
5 From loop to song "Turn the loop into a full track…" scenes, a build-up with a clap roll and filter sweep, the arrangement, locators
6 Mix check "Check my mix against my reference track…" meters, a bounce, LUFS and spectrum vs a reference, EQ, side-chain, limiter
7 Live on another computer "Connect to Live on my Windows PC…" LAN mode, discovery, sending files to the Live machine
8 Anything else "Rename every clip after its track and scene" the Live Object Model, batches, Python inside Live

More: 100+ prompts to copy · Scripting Live from Python without Claude.

How these were made

The LiveBridge calls in examples 1–6 and 8 were run against Ableton Live 12.4.5 Suite on macOS with LiveBridge 1.0 (September 2026). The JSON under the calls is real output, shortened. Not re-run for these pages: the steps that play audio (the meters and the bounce in example 6), Splice's own search and download (example 4, which needs a Splice login; its file names are placeholders) and example 7, which needs two computers. tests/test_examples.py checks on every commit that each tool and argument used on these pages exists.

The calls are written like Python so they're easy to read. true, false and null are JSON values, as in the MCP messages Claude actually sends.

Try them yourself

  1. Install LiveBridge (quick start) and enable the control surface in Live.
  2. Open Claude Code or Claude Desktop and paste a prompt from a page. Start with an empty set or a scratch set.
  3. Everything Claude does is one undo step per call in Live: Cmd/Ctrl+Z takes it back.