Bitwig Grid Bridge
On this page
Inspect, build, and shape native Bitwig Grid patches — with a local bridge that lets you see what will change before you change it.
Install and verify What’s new in 0.2.0
docs 0.2.0Bitwig 6.1.1license MIT
First, make the connection
Install the extension, select a device, and run the read-only inspection command. A working connection returns ok: true, the runtime version, and the selected device. Nothing plays. Nothing moves. For once, that is the point.
The bridge supports Bitwig Studio 6.1.1 exactly, using Controller API 25. You need Python 3.10 or newer for the example script; an AI client is optional. Follow the quickstart for the shortest path, or installation for platform paths and troubleshooting.
Then, make music
- Shape a sound. Start with musical styling: choose a role and motion, preview a small parameter change, then apply it.
- Build a groove. The minimal techno guide walks through a native kick and bass patch.
- Arrange a track. Composition and delivery covers score planning, MIDI export, native realization, and verification. MIDI is a score, not a finished recording.
- Prepare a performance. Live-set construction organizes scenes, roles, and bounded performance controls.
Keep control of the session
Use observe → preview → authorize → apply → verify. A preview is not a mutation, and an accepted command is not proof that the sound is right.
- Work in a project copy for experiments. Re-read the selected device and graph 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. See recovery.
- Keep project backups. Session parameter rollback and Bitwig’s global undo are different operations.
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. Optional Nitro inspection supplies static DSP evidence; it does not establish a live module’s identity. Read the integration boundaries before building automation around them.