Gravity Feed for Bitwig Studio
Connect Bitwig Studio through a controller extension and remote-control pages.
This guide explains how Bitwig Studio can work with Spatial9 Gravity Feed. Status: documented route. Bitwig has a public JavaScript and Java controller extension API, and it hosts VST3 and CLAP plugins, so an adapter can read the project and drive an encoder. Spatial9 has not built or tested a Bitwig adapter.
At a glance
| Item | Detail |
|---|---|
| Status | Documented route, no Spatial9 adapter yet |
| Adapter type | Controller extension plus a companion process for network calls |
| Reads | Tempo, cue markers and track names through the controller API |
| Writes | Encoder parameters, recorded as automation |
| Spatial plugin | IEM StereoEncoder (VST3), driven by OSC or remote controls |
Route
- Load IEM StereoEncoder on each spatial track and open its OSC port, or map azimuth and elevation to the device's remote controls.
- The controller extension reports tempo, cue markers and track names to a companion process, which sends the Gravity Feed request with your key.
- Arm automation write and play the range. The companion sends each planned value at its beat time.
Mapping the request
| Gravity Feed field | Bitwig source |
|---|---|
session.tempo_map | Transport tempo |
session.sections | Cue markers |
tracks[].role | Track names |
tracks[].position | Encoder values |
FAQ
Can the controller extension call the API itself?
Controller extensions are not designed for web requests, so a small companion process handles the network call.
Does Bitwig handle multichannel audio?
Bitwig supports multichannel routing for plugins, which suits Ambisonic encoders followed by a binaural decoder for headphones.