Written from devices/ableton/move.vendor.fw-extending-move-e8aef58.jsonEdit on GitHubJSONMIDNAMOSCQuery

Ableton Move (extending-move e8aef58) MIDI CC chart, NRPN and OSC map

The Ableton Move MIDI implementation: its MIDI messages, each named, for Claude (MCP), SuperCollider or any OSC app.

• sourcemaker's documentation
• firmwareextending-move-e8aef58
• licenceMIT
• real unitnot yet checked

Not checked on a real Ableton Move yet. Own one? Load a sound or send a control, and tell us whether it worked.

Maker

Ableton

Version

extending-move e8aef58 (by Charles Vestal)

Source

maker's documentation

Data licence

MIT

OSC prefix

/move_extending

README.mdfrom the author's repository; not claimed yet, anyone can improve itEdit

From the README of charlesvestal/extending-move at e8aef58, licence MIT.

extending-move

Tools for extending the Ableton Move. This project provides a companion webserver that runs alongside the official Move server, accessible at move.local:909!

Demo on YouTube

Come talk to us on Discord.

Installation instructions

Quick installation video - Clone or download the repository. - Run utility-scripts/setup-ssh-and-install-on-move.command - Follow the instructions!

Read the whole README on GitHub

Use 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/move.vendor.fw-extending-move-e8aef58.json --out-port <N> --in-port <M>

From Claude or any MCP client, the osc-bridge mcp server exposes this driver as move_extending: ask “what can the Ableton Move do?” and it reads this map with list_routes. See the MCP guide.

MIDI controls

0 controls, each with its number, its range and the name to send

Performance MIDI

Notes, pitch bend and any CC are also available: /move_extending/note/on <note> <velocity>, /move_extending/cc/<number> <value>, /move_extending/pitchbend <0-16383>, /move_extending/program_change <n>.

JSON

The same MIDI as move.vendor.fw-unknown, which this firmware shares.

Limitations

extending-move by Charles Vestal (MIT): tools that run alongside the Move's firmware. Move's MIDI is unchanged. Untested on hardware.

Firmwares

The Ableton Move runs 3 firmwares SynthHub maps, each with its own MIDI or another's it shares. All the devices with several: firmwares.

Firmware	From	Licence	MIDI	Sounds
extending-move e8aef58	github.com/charlesvestal	MIT	same as ableton/move.vendor.fw-unknown
move-anything 15b212e	github.com/bobbydigitales		same as ableton/move.vendor.fw-unknown
Schwung 1.8.2	github.com/charlesvestal	MIT	same as ableton/move.vendor.fw-unknown

Other sources

The Ableton Move is mapped in 4 versions. Move Manual.

Frequently asked questions

Can an AI agent like Claude control the Ableton Move?

Yes: SynthHub's hosted MCP server knows the Ableton Move's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.