Gravity Feed DAW guides
How to connect REAPER, Ableton Live, Bitwig, FL Studio, Cubase, Nuendo, Pro Tools, Logic and more, with honest status.
This page explains how to connect Gravity Feed to each major DAW. Every DAW can reach the API, because a plan request is just an HTTPS call. What differs is how much of the session a script can read and whether it can write automation back. The status next to each DAW is honest: only REAPER has Spatial9 code, and it is a prototype.
The three adapter routes
| Route | How it works | Best for |
|---|---|---|
| Session script | A script inside the DAW reads tempo, regions and tracks, calls the API and writes automation | DAWs with full scripting, such as REAPER |
| OSC to the plugin | An adapter sends the plan's OSC messages straight to a plugin that listens, such as IEM or ICST | Any DAW hosting an OSC-capable spatial plugin |
| Plugin-side capture | A plugin on each track reads host tempo and position and writes its own parameters (Gravity Capture, planned) | DAWs without public automation scripting |
Whichever route you use, the adapter must check preconditions.session_revision and expires_at before writing, and write the whole alternative in one undo step where the DAW allows it.
What every adapter must do
- Convert the DAW's time to quarter-note beats using its tempo map.
- Send a stable, pseudonymous
session.idand arevisionthat changes when the session changes. - Mark tracks the user must keep still with
anchororlocked_parameters. - Bind tracks to targets only when you can actually write that plugin's parameters.
- Show all alternatives and every
unsupported_actionsreason before committing. - Never send audio, file paths or client names.
Guides by DAW
Each DAW has its own guide with setup steps, what the adapter reads and writes, and the limits today.
| DAW | Status | Route | Hosts IEM plugins | Guide |
|---|---|---|---|---|
| REAPER | Prototype | Lua script reads the session and writes envelopes | Yes (VST2, VST3) | REAPER guide |
| Ableton Live | Documented route | Max for Live device | Yes (VST2, VST3) | Ableton Live guide |
| Bitwig Studio | Documented route | Controller extension and remote controls | Yes (VST2, VST3) | Bitwig Studio guide |
| FL Studio | Documented route | Python MIDI script and a companion | Yes (VST2, VST3) | FL Studio guide |
| Cubase | Documented route | MIDI Remote and automation write | Yes (VST3) | Cubase guide |
| Nuendo | Documented route | MIDI Remote and automation write | Yes (VST3) | Nuendo guide |
| Pro Tools | Documented route | PTSL for session details, AAX plugin for writing | No (AAX only) | Pro Tools guide |
| Logic Pro | Documented route | MIDI on the IAC bus to an AU plugin | No (AU only) | Logic Pro guide |
| Studio One / Fender Studio Pro | Documented route | Control Link or OSC | Yes (VST3) | Studio One guide |
| Reason | Documented route | Remote Override or OSC | Yes (VST) | Reason guide |
| Cakewalk Sonar | Documented route | ACT MIDI learn or OSC | Yes (VST3) | Cakewalk Sonar guide |
| GarageBand | Documented route | Listening and manual use | No (AU only) | GarageBand guide |
For each plugin, see the plugin guides.
FAQ
Which DAW should I start with?
REAPER, because its scripting can read the session and write envelopes in one undo step, and a prototype script already exists.
Can I use Gravity Feed with a DAW that is not listed?
Yes. If the DAW can run a script that makes HTTPS requests, or can host an OSC-capable plugin, follow the steps in "What every adapter must do".
When will Gravity Capture ship?
It is planned and not scheduled. This page will change its status when a tested build exists.
Can I use IEM plugins in Logic Pro or Pro Tools?
Not natively. IEM's ready-made downloads do not include Audio Unit or AAX builds, so use a spatial plugin in the host's format.