Bitwig Grid Bridge
On this page
Inspect, build, and shape native Bitwig Grid patches through a local bridge that shows guarded changes before they are applied.
Install and activate Current boundaries
docs 0.2.1Bitwig 6.1.1license MIT
First, make the connection
Install the extension and use the read-only inspection procedure in the
quickstart. The source targets Bitwig Studio 6.1.1 and
Controller API 25. Python 3.10 or newer is required for the example script;
an MCP client is optional. The running native endpoint must report protocol 4
and the running MCP server's tools/list response is authoritative.
Then, make music
- Shape a sound. Use musical styling for bounded selected-device parameter changes.
- Build a Grid patch. Use the minimal techno guide with fresh graph identities and read-backs.
- Export an offline score. Use offline composition and export. This produces Type-1 MIDI and a manifest; it does not import or realize a Bitwig project.
- Prepare a performance. Live-set construction covers transport, track, mix, device, and action boundaries.
Keep control of the session
Use observe → preview → authorize → apply → verify. A preview is not a mutation, and a submitted host operation is not proof of completion or sound quality.
- Work in a project copy for experiments.
- Re-read project, selection, mix, and graph identities before changing them.
- Treat
graph_available: falseas a hard boundary; do not invent modules, ports, or cables. - After an ambiguous timeout, inspect the result before retrying.
- Keep backups; session restore and Bitwig's global undo are different scopes.
Go deeper
| You want to… | Start here |
|---|---|
| Run a repeatable script | Python automation |
| Connect an AI or MCP client | Integration overview |
| Find an operation quickly | Cheat sheet · Tool reference |
| Understand identity, ranges, and safety | Data and safety |
| Look up modules or modulation sources | Device inventory · Modulator catalog |
All bridge traffic stays local. The bridge intentionally does not implement native arranger note/clip/automation editing, MIDI import or voice realization, live capture, audio rendering/export, or project save/new/load/ delivery. Read the integration boundaries before building automation around it.