Documentation menu
On this page

Version 0.2.0 exposes 90 MCP tools for composition, native Grid editing, arranger refinement and audio review. The main additions are identity-preserving note edits, native score-time automation, voice controls, read-only role reconciliation and bounded audio capture.

Compatibility

Version What it identifies
0.2.0 Bridge extension and Python package; install matching versions
Bitwig Studio 6.1.1 Exact supported private native runtime
Controller API 25 Public minimum API and compile-time dependency
Protocol 3 Local text-command/JSON-response socket protocol

Public API compatibility does not establish private native compatibility. Unknown private runtimes fail closed; read capabilities and selected state before native operations. Offline composition/export does not require Bitwig. The bridge remains local at 127.0.0.1:8765 and claims no MIDI ports.

The optional adapter requires Python 3.10+. Java 21 and Maven are needed only for source builds. Audio capture requires Linux PipeWire tools, GNU timeout, ffmpeg and ffprobe. See Installation.

Changes

  • Scoped composition. bitwig-track/2 separates score, synthesis, automation intent, native-only source policy and evidence. Role/section/phrase targeting, preservation locks and deliberate regeneration support local revisions. Custom contiguous forms, Hardgroove profiles, independent bass rhythm and synthesis, procedural percussion and vocal-like roles are supported.
  • Native voice preparation. grid_track_prepare_role previews construction on an explicitly selected empty native instrument Grid, or parameter-only refinement on its exact binding. Musical units use native scales. Import, selection, clearing and playback are never implicit.
  • Native notes. Inspect → bind → preview → apply reads complete bounded supported primary note/expression sources and produces minimal reviewed diffs. Existing note identities, attributes, expression points, unrelated notes and clip geometry are preserved. Apply checks exact project/content identity, uses undo and verifies read-back; stale or ambiguous mappings reject.
  • Native automation. grid_automation_* inspects, normalizes, previews and applies primary unsegmented arranger curves for exact Grid/mix destinations. Hold/linear points require explicit neutral/reset boundaries. Writes run once while stopped, with undo, outside-span preservation and read-back — not a playback-time stream of parameter writes. grid_track_preview_automation compiles bound vocal scores into supported vowel trajectories and phrase resets.
  • Voice and inspector controls. Native voice count, stacking, mono/retrigger, priority and glide use fresh selection/configuration guards. Supported static inspector and mix writes reject automated targets. Pitch In retains its voice-aware Default setting; device priority is not a module-level override. Arranger-loop range edits are distinct from clip loop flags.
  • Read-only reconciliation. grid_track_reconcile_role checks controls, explicit cables and voice allocation against fresh state and a complete explicit recipe-alias/module map. Required corrections reject for separate review. Reconciliation does not rebuild a graph, restore note bindings, verify automation or retain earlier audio/listening acceptance.
  • Audio review. Discover exact ordered Bitwig PipeWire outputs, preview a bounded span and release tail, then authorize capture and transport separately. Capture requires stopped, disarmed, non-recording transport, an active engine and arranger loop off; these preconditions are not changed implicitly. One consumed proposal observes seek/play settling and stop before the release tail. Poll status; never replay an ambiguous capture. Analysis reports bounded peak/RMS/envelope/low-band evidence. Comparison uses attenuation-only whole-file RMS matching, not perceptual LUFS. Listening records require an explicit human decision bound to the exact review/audio digest; analysis cannot supply one.

Support boundaries

  • Unsupported sources, stale identities and conflicting ownership reject. Alternate, clip, generated and segmented automation stores remain unsupported. Same-channel/same-pitch note overlaps reject; different-pitch overlaps can express legato articulation.
  • Source counts do not expand loops or prove intended playback. Native read-back does not establish sound quality, seek/loop behavior or persistence after reopening.
  • Capture routing is sampled, not continuously proven. Pre-roll and observed transport latency mean capture boundaries are not sample-accurate. Recorder limits cannot prove transport stopped after adapter loss.
  • Ordinary native save is not Collect and Save. Completion establishes the callback and expected file's presence, not content equivalence or collected external assets.
  • Nitro catalog discovery/readiness is separate from successful authorized inspection. Static DSP evidence is not live Grid identity or listening proof.

Generated songs, MIDI, captures, native delivery projects and session, evidence, listening or authorization records remain local. Shipped examples are deliberate public fixtures. Technical results do not imply human musical approval.

Upgrade

  1. Install matching extension and adapter versions using the installation guide. Use a published bundle, or build from source if the required version is unavailable.
  2. Restart Bitwig and perform read-only inspection. Reload is asynchronous; copying the extension alone is not readiness. Reconnect the MCP client to refresh its 90-tool catalog and schemas.
  3. Re-observe project, selection, graph and content/configuration revisions. Do not reuse pre-restart IDs, tokens or in-memory workflow authority. Exported files are artifacts, not permission to replay an import or write.
  4. Update composition callers to grid_track_revise's scoped arguments: scope, exact target when applicable, flat changes and deliberate regenerate. The whole-brief overrides path is removed. Automation callers must distinguish has_automation (a lane is attached) from has_timeline_points (the lane contains timeline points).

See the Tool reference for exact arguments, Agent workflow playbook for operation order and Data and safety for identity and recovery contracts.

Search docs

All words must match. Enter opens the first result.

Type a tool, argument, or guard to begin.