Bitwig Studio: OSC control from Claude, scripts and controllers¶
9 named commands to drive Bitwig Studio over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | Bitwig Studio |
|---|---|
| Vendor | Bitwig |
| OSC prefix | /bitwig |
| Source | 📡 From a third-party OSC API |
| Firmware | Bitwig Studio 5 |
| Revision | Bitwig Studio 5 + DrivenByMoss (latest) |
| Upstream | third-party-osc |
| Driver file | devices/bitwig/bitwig-studio.third-party-osc.fw-5.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?¶
Start the bridge with this driver; it forwards named OSC commands to the software:
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 bitwig: ask “what can the Bitwig Studio do?” and it reads this map with list_routes. See the MCP guide.
OSC commands (9)¶
| OSC address | Arguments |
|---|---|
/bitwig/transport/play |
|
/bitwig/transport/stop |
|
/bitwig/transport/tempo |
bpm: float |
/bitwig/transport/tap |
|
/bitwig/track/{n}/volume |
n: int, v: float |
/bitwig/track/{n}/mute |
n: int, on: bool |
/bitwig/track/{n}/solo |
n: int, on: bool |
/bitwig/track/{n}/arm |
n: int, on: bool |
/bitwig/scene/{n}/launch |
n: int |
Limitations¶
v1 covers transport (play / stop / tempo), per-track volume / mute / solo / arm for the first 8 tracks (DrivenByMoss bank size), and scene launch for the first 8 scenes. Track and scene indices are 1-based in DrivenByMoss (NOT 0-based like AbletonOSC). Browser, devices, automation, and the wider DrivenByMoss surface are out of scope for v1.