Tune how knobs, faders and the XY pad respond to your hand, and keep a strip of your own command buttons. These preferences are yours. They do not change with the theme or the workspace, and they do not change what a control means.
Adjust control gestures#
Open Display and expand Interaction:
| Setting | Default | Range | Effect |
|---|---|---|---|
| Knob drag | Vertical or horizontal | Vertical, Horizontal, both | Which motion turns a knob. Up or right increases. Faders and send bars always follow their own direction. |
| Knob sensitivity | 1× | 0.25×–4× | Knob travel per point of drag. Faders and send bars track the pointer and ignore it. |
| Fine adjust (Shift) | 0.15× | 0.02×–0.5× | Travel while Shift is held. A fine drag also skips detents. |
| Wheel adjusts knobs | On | on/off | When off, the wheel scrolls the panel under a knob instead. |
| Wheel step | 24 notches per sweep | 4–200 | How many wheel notches cross a knob's whole range. |
| Double-click resets to default | On | on/off | When off, double-click leaves the value alone. |
| Detents | On | on/off | A drag sticks briefly at a control's default, unity or centre. |
Reset interaction to defaults restores the table's defaults.
The settings apply to the Perform strip's macro knobs, the XY pad (double-click reset only; it is a position surface), the Mixer's faders, pan pots and send bars, and the Bench track-card fader (fine adjust only). Only knobs (macros and pan) answer the wheel; a fader or send leaves it to the scrolling console. Each control's hover hint follows the profile: it mentions scrolling, detents and double-click only while they are on.
What stays fixed#
A preference changes how far and which way a gesture travels, not the parameter. Each control keeps its range, unit, default and detent positions, and its mapping: a logarithmically scaled control moves by equal ratios for equal travel under every setting. Automation ownership, source authority and Undo are unchanged. A Mixer drag is still one Undo step on release, a double-click reset is one step, and a wheel flick on a pan pot commits once after the wheel goes quiet. Arrow keys on a focused pan pot and right-click numeric entry on a fader work as before. ⌘Z / ⇧⌘Z undo and redo the song while a knob, fader or pan pot has keyboard focus (they take no text); inside a text field, including a control's typed entry, the field keeps them.
Add a command strip#
A Commands pane holds buttons for existing Studio commands. With the custom workspace on, place it from Display's Show or move pane (it appears above Source), or drag it like any other pane. Edit strip lists the eligible commands; check up to twelve. Reset strip restores Run, Play all, Stop all, Metronome and Tap tempo.
Each button is the same command as its menu item. It is greyed or absent exactly when the menu item is, acts on the same focused song or buffer, and runs at the start of the next frame. The strip offers commands, not menus, and cannot create new ones. Its buttons are inert while a song is opening, and restoring saved preferences never runs a command.
Saving and recovery#
Native Studio saves the profile and strip with its shell state; the browser keeps them in local storage beside, but separate from, the theme and workspace. A theme or workspace change does not carry or reset them. If the browser refuses to store them, they last for the session and a notice says so once.
Saved preferences are versioned. A damaged, out-of-range or newer-version value is replaced by defaults (field by field where possible), and the Interaction section explains what was reset. Unknown or menu-only commands are dropped from the strip with the same note.
Notes and limits#
Shift is the fine-adjust modifier; it is not remappable. Themes never apply interaction presets. A skin may carry an optional top-level "recommendedInteraction" (any of the fields above, camelCase, for example { "knobDrag": "vertical", "doubleClickReset": false }). When the theme on screen suggests something different from yours, Display shows The <skin> skin suggests: … with Use (takes only the fields it names) and Ignore (no offer from that skin again this session). Loading the skin changes nothing; unknown or out-of-range fields are dropped with a warning in the skin report. Song-authored panels and new kinds of controls are not part of this: they arrive through Authored Interfaces, which will reuse the same gesture adapter.