Gravity Feed for Studio One / Fender Studio Pro
Connect Studio One through Control Link or OSC to a VST3 encoder.
This guide explains how Studio One (now Fender Studio Pro) can work with Spatial9 Gravity Feed. Status: documented route. There is no public scripting for session automation, so the route is MIDI control of a spatial plugin, mapped with Control Link and recorded as automation. Spatial9 has not built or tested an adapter.
At a glance
| Item | Detail |
|---|---|
| Status | Documented route, no Spatial9 adapter yet |
| Adapter type | Companion process on a virtual MIDI port, mapped with Control Link |
| Reads | Nothing automatically; tempo, sections and roles are entered in the companion |
| Writes | Plugin parameters, recorded in Latch or Touch automation mode |
| Spatial plugin | IEM StereoEncoder (VST3) or another encoder with host automation |
Route
- Create a virtual MIDI port (loopMIDI on Windows, the IAC bus on macOS) and add it as a control surface or keyboard.
- With Control Link, map two controls to the encoder's azimuth and elevation on each spatial track.
- Enter the tempo, section beats and track roles in the companion; it requests the plan with your key.
- Put the tracks in Latch, play the range, and the companion sends the planned values.
Studio One also hosts OSC-capable plugins: IEM StereoEncoder can be moved over OSC directly (/StereoEncoder/azimuth 40.0) while the track records automation of the same parameter.
Mapping the request
| Gravity Feed field | Source |
|---|---|
session.tempo_map | Song tempo, typed in |
session.sections | Arranger sections or markers, typed in |
tracks[].role | Track names |
tracks[].position | Encoder values, read from the plugin or typed in |
FAQ
Does the product rename change anything?
No. The route depends on plugin hosting and MIDI mapping, which work the same way.
Will there be a native integration?
The planned Gravity Capture plugin is the intended route for hosts without public scripting.