devices/arturia/beatstep-pro.vendor.fw-1.3.jsonEdit on GitHubJSONArturia BeatStep Pro MIDI CC chart, NRPN and OSC map
The Arturia BeatStep Pro MIDI implementation: 8 SysEx commands, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- firmware1.3
- real unitnot yet checked
Not checked on a real Arturia BeatStep Pro yet. Own one? Load a sound or send a control, and tell us whether it worked.
- Maker
- Arturia
- Version
- BeatStep Pro User's Manual 1.3.0
- Source
- maker's documentation
- OSC prefix
/beatstep_pro
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/arturia/beatstep-pro.vendor.fw-1.3.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 beatstep_pro: ask “what can the Arturia BeatStep Pro do?” and it reads this map with list_routes. See the MCP guide.
MIDI controls
8 controls, each with its number, its range and the name to send
SysEx commands
| Command | Arguments | Name to send |
|---|---|---|
| Seq1 note on | note: u7, velocity: u7 | /beatstep_pro/seq1/note_on |
| Seq1 note off | note: u7 | /beatstep_pro/seq1/note_off |
| Seq2 note on | note: u7, velocity: u7 | /beatstep_pro/seq2/note_on |
| Seq2 note off | note: u7 | /beatstep_pro/seq2/note_off |
| Transport clock | /beatstep_pro/transport/clock |
|
| Transport start | /beatstep_pro/transport/start |
|
| Transport continue | /beatstep_pro/transport/continue |
|
| Transport stop | /beatstep_pro/transport/stop |
Performance MIDI
Notes, pitch bend and any CC are also available: /beatstep_pro/note/on <note> <velocity>, /beatstep_pro/cc/<number> <value>, /beatstep_pro/pitchbend <0-16383>, /beatstep_pro/program_change <n>.
Limitations
Source: BeatStep Pro User's Manual 1.3.0. The BeatStep Pro is mostly a sender: in Control Mode its pads, step buttons and encoders send what the MIDI Control Center assigns (defaults: pads = notes, encoders = CCs 'that vary', on the User channel 1), its sequencers play on channels 1, 2 and 10 and its transport sends MMC and/or CCs. What it receives and acts on: notes on SEQ1/SEQ2's receive channels go to their CV/Gate jacks (routes above); notes on the Drum channel (10) open the Drum Gate jacks whose note numbers are set in the MIDI Control Center (no default is printed, so no trigger is listed); notes on the Transposition input channel transpose the sequences around the centre pitch (default note 60), channel and port set in the MIDI Control Center. The manual documents no SysEx, and no Program Change or CC that the BeatStep Pro obeys. Untested on hardware.
Frequently asked questions
Can an AI agent like Claude control the Arturia BeatStep Pro?
Yes: SynthHub's hosted MCP server knows the Arturia BeatStep Pro's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.