Add a return track
Press⌥⇧⌘T to add a return track. Returns also appear in the right-click menu of the Sidebar’s empty area. New returns are inserted just above the Master bus and named Return 1, Return 2, … automatically. There is no limit on the number of returns.
Returns carry the same effects chain, mix controls (gain, pan, stereo width, mono-below), metering, and signal history as any other track. Load plugins on them through the Plugin Strip — including sidechain sources.
Create a send
On any sample or instrument track, open the Sends section in the Inspector. One row appears per return in the project; rows are dimmed until they carry signal. To create the send, drag the row’s slider above 0. The send starts at Post-Mix by default. To remove a send, drag the slider back to 0 — there is no separate “Remove” button.
Right-click a send row for:
- Send Pre-Mix / Send Post-Mix — choose the tap point (see below).
- Automate Send Amount — adds a new automation lane bound to the send level.
- Go to Track — selects the return in the Sidebar and reveals it in the Inspector.
Pre-Mix vs Post-Mix
A send’s tap point decides where in the source track’s signal path the audio is picked up.
Use Post-Mix for typical “more reverb on this track” routing. Use Pre-Mix when you want the wet path to stay alive while the dry source is faded down, or to drive a parallel processor at a fixed level regardless of the fader.
Muting the source does not silence its sends — the mute gate sits after both tap points. That’s what makes soloing a Return a clean way to audition just the wet signal.
Incoming Sends on the return
Select a return track. Its Inspector adds an Incoming Sends section listing every track currently sending into it — one row per source, in track order. The rows mirror the source side exactly:- Slider with the same 0 – 150 % range and 100 % snap.
- Right-click for Send Pre-Mix / Send Post-Mix, Automate Send Amount, and Go to Track (jumps to the source).
- Drag to 0 to disconnect.
What can send where
Gridshift checks for routing cycles every time you create or change a send; sends that would close a cycle are refused.