Gravity Feed for Reason
Connect Reason through Remote Override or OSC to a VST encoder in the rack.
This guide explains how Reason can work with Spatial9 Gravity Feed. Status: documented route. Reason hosts VST plugins in its rack but has no session scripting, so the route is MIDI or OSC control of a VST encoder, 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 sending MIDI (mapped with Remote Override) or OSC directly to the plugin |
| Reads | Nothing automatically; tempo, sections and roles are entered in the companion |
| Writes | Plugin parameters, recorded as automation while playing |
| Spatial plugin | IEM StereoEncoder (VST2 or VST3), which also listens to OSC |
Route
- Load IEM StereoEncoder in the rack on each spatial channel.
- Either open the plugin's OSC receiver on a port, or map two MIDI controls to azimuth and elevation with Remote Override.
- Enter tempo, section beats and track roles in the companion; it requests the plan with your key.
- Record automation while playing, and the companion sends the planned values at their beat times.
Limits today
- Reason cannot report its tempo or sections to an adapter, so they must be entered.
- Multichannel Ambisonic routing in Reason is limited; check that your output format suits the encoder you load.
FAQ
Does Reason Rack Plugin change this?
Inside another DAW, follow that DAW's guide; the encoder runs in the host, not in the Rack.
Is OSC better than MIDI here?
OSC sends full-resolution degrees and needs no mapping; MIDI is easier to record as Reason automation. Both are documented routes.