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

RouteHow it worksBest for
Session scriptA script inside the DAW reads tempo, regions and tracks, calls the API and writes automationDAWs with full scripting, such as REAPER
OSC to the pluginAn adapter sends the plan's OSC messages straight to a plugin that listens, such as IEM or ICSTAny DAW hosting an OSC-capable spatial plugin
Plugin-side captureA 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

  1. Convert the DAW's time to quarter-note beats using its tempo map.
  2. Send a stable, pseudonymous session.id and a revision that changes when the session changes.
  3. Mark tracks the user must keep still with anchor or locked_parameters.
  4. Bind tracks to targets only when you can actually write that plugin's parameters.
  5. Show all alternatives and every unsupported_actions reason before committing.
  6. 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.

DAWStatusRouteHosts IEM pluginsGuide
REAPERPrototypeLua script reads the session and writes envelopesYes (VST2, VST3)REAPER guide
Ableton LiveDocumented routeMax for Live deviceYes (VST2, VST3)Ableton Live guide
Bitwig StudioDocumented routeController extension and remote controlsYes (VST2, VST3)Bitwig Studio guide
FL StudioDocumented routePython MIDI script and a companionYes (VST2, VST3)FL Studio guide
CubaseDocumented routeMIDI Remote and automation writeYes (VST3)Cubase guide
NuendoDocumented routeMIDI Remote and automation writeYes (VST3)Nuendo guide
Pro ToolsDocumented routePTSL for session details, AAX plugin for writingNo (AAX only)Pro Tools guide
Logic ProDocumented routeMIDI on the IAC bus to an AU pluginNo (AU only)Logic Pro guide
Studio One / Fender Studio ProDocumented routeControl Link or OSCYes (VST3)Studio One guide
ReasonDocumented routeRemote Override or OSCYes (VST)Reason guide
Cakewalk SonarDocumented routeACT MIDI learn or OSCYes (VST3)Cakewalk Sonar guide
GarageBandDocumented routeListening and manual useNo (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.

Go deeper on the blog