Gravity Feed for Cubase
Connect Cubase through the MIDI Remote API and record encoder automation.
This guide explains how Steinberg Cubase can work with Spatial9 Gravity Feed. Status: documented route. Cubase has the MIDI Remote API for JavaScript control scripts and hosts VST3 plugins, so a companion process can drive an encoder while Cubase records automation. Spatial9 has not built or tested a Cubase adapter.
At a glance
| Item | Detail |
|---|---|
| Status | Documented route, no Spatial9 adapter yet |
| Adapter type | Companion process on a virtual MIDI port, mapped with MIDI Remote, or OSC directly to the encoder |
| Reads | Tempo, markers and track names are entered in the companion |
| Writes | Encoder parameters, recorded in Touch or Latch automation mode |
| Spatial plugin | IEM StereoEncoder (VST3), or Cubase's own panner by hand |
Route
- Load IEM StereoEncoder on each spatial track and open its OSC port, or map azimuth and elevation to two controls with MIDI Remote.
- Enter the tempo, marker beats and track roles in the companion; it sends the Gravity Feed request with your key.
- Set the tracks to Latch, play the range, and the companion sends each planned value.
Mapping the request
| Gravity Feed field | Cubase source |
|---|---|
session.tempo_map | Project tempo |
session.sections | Markers or the arranger track |
tracks[].role | Track names |
tracks[].position | Encoder values |
FAQ
Can Gravity Feed drive Cubase's own surround panner?
Not today. No profile describes it, so apply the plan's positions by hand.
Is Nuendo different?
Nuendo shares the same base and adds more immersive tools. See the Nuendo guide.