Gravity Feed for Cakewalk Sonar
Connect Cakewalk Sonar through ACT MIDI learn or OSC to a VST3 encoder.
This guide explains how Cakewalk Sonar can work with Spatial9 Gravity Feed. Status: documented route. Sonar hosts VST3 plugins and can map MIDI to plugin parameters with ACT (Active Controller Technology), so a companion process can drive an encoder while Sonar records 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 ACT, or OSC directly to the plugin |
| Reads | Nothing automatically; tempo, markers and roles are entered in the companion |
| Writes | Plugin parameters, recorded with automation write |
| Spatial plugin | IEM StereoEncoder (VST3) |
Route
- Create a virtual MIDI port and enable it as an input.
- Use ACT MIDI learn to map two controls to the encoder's azimuth and elevation, or open the encoder's OSC port instead.
- Enter tempo, marker beats and track roles in the companion; it requests the plan with your key.
- Enable automation write on the tracks, play through the range, and the companion sends the planned values.
Mapping the request
| Gravity Feed field | Source |
|---|---|
session.tempo_map | Project tempo, typed in |
session.sections | Markers |
tracks[].role | Track names |
tracks[].position | Encoder values |
FAQ
Is CAL scripting an option?
Cakewalk's older CAL language edits MIDI events and is not suited to network calls or plugin automation. Use the routes above.
Which Cakewalk versions does this cover?
The route depends on VST3 hosting and MIDI mapping, which current and recent Cakewalk releases share.