Ableton Looper v2: MIDI CC, NRPN and OSC map¶
The Ableton Looper v2 as named OSC addresses — 9 CC — ready to use from Claude (MCP), SuperCollider, Sonic Pi, TouchDesigner or any OSC app via osc-bridge.
| Device | Ableton Looper v2 |
|---|---|
| Vendor | Ableton |
| OSC prefix | /looper_v2 |
| Source | 🎛️ Derived from an Electra One community preset |
| Revision | per Electra preset |
| Upstream | electra-preset |
| Driver file | devices/ableton/looper_v2.json |
Not tested on the device yet
This driver comes from documentation or community data and has not been checked on real hardware. If you own one, a quick test and a pull request promoting it helps everyone — see CONTRIBUTING.
How do you control it?¶
Find the MIDI ports, then start the bridge with this driver:
osc-bridge detect # prints the ready-to-run line for what is plugged in
osc-bridge run --device devices/ableton/looper_v2.json --out-port <N> --in-port <M>
Then send OSC to 127.0.0.1:7777, for example:
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as looper_v2: ask “what can the Ableton Looper v2 do?” and it reads this map with list_routes. See the MCP guide.
MIDI CC and NRPN parameters (9)¶
| OSC address | CC | NRPN (MSB/LSB) | Range | Nature | Section |
|---|---|---|---|---|---|
/looper_v2/state |
7 | 0–127 | continuous | ||
/looper_v2/song_control |
6 | 0–127 | continuous | ||
/looper_v2/speed |
1 / 33 | -360–360 | continuous | ||
/looper_v2/feedback |
0 / 32 | 0–1000 | continuous | ||
/looper_v2/quantization |
4 | 0–127 | continuous | ||
/looper_v2/tempo_control |
8 | 0–127 | continuous | ||
/looper_v2/reverse |
5 | 0–127 | continuous | ||
/looper_v2/monitor |
3 | 0–127 | continuous | ||
/looper_v2/device_on |
2 | 0–127 | continuous |
Performance MIDI¶
Notes, pitch bend and any CC are also available: /looper_v2/note/on <note> <velocity>, /looper_v2/cc/<number> <value>, /looper_v2/pitchbend <0-16383>, /looper_v2/program_change <n>.
Limitations¶
Imported from an Electra One community preset. The mapping reflects the preset author's editorial choices: parameter naming, ranges, and which params are exposed. Untested on hardware in this repo.