Loading & Removing Plugins
This page covers how to add AUv3 plugins to a track, manage plugin slots, and remove plugins when you no longer need them.
Opening the Plugin Browser
Tap any ＋ slot on a channel strip in the mixer to open the Plugin Browser.
[SCREENSHOT: Empty plugin slot with + icon on mixer strip]
[SCREENSHOT: Plugin Browser — Effects tab showing a list of installed plugins]
The Plugin Browser has three tabs:
| Tab | Shows |
|---|---|
| Effects | Amp sims, EQ, reverb, delay, dynamics, modulation, and Apple system effects |
| Instruments | Synthesizers, samplers, drum machines, and generators |
| MIDI Processors | Arpeggiators, chord generators, pitch correction |
Refreshing the List
If you install a new AUv3 app while the browser is open, tap Refresh in the top-right to rescan the system’s registered Audio Units.
Plugin Badges
Each plugin row shows:
- AUv3 badge (blue) — confirms this is a third-generation Audio Unit running in its own sandboxed process
- UI badge (green) — the plugin has a custom graphical editor you can open
Loading a Plugin
- Tap a ＋ slot in the mixer channel strip
- Select the correct tab (Effects, Instruments, or MIDI Processors)
- Tap the plugin you want to load
[SCREENSHOT: Tapping a plugin row in the browser to load it]
The browser closes and the slot updates to show the plugin’s name.
[SCREENSHOT: Loaded plugin slot — green border, plugin name, gear icon]
Loading may take a moment for complex plugins (particularly neural amp simulations that load large model files).
Note: Playback must be stopped before loading or removing a plugin. If the transport is running, you’ll see an alert asking you to stop first.
Viewing Loaded Plugins
Loaded slots show:
- The plugin name (truncated if long)
- A ⚙ gear icon indicating there are settings to open
- A green border to distinguish loaded slots from empty ones
[SCREENSHOT: All 4 slots showing different loaded plugins]
Opening a Plugin’s Editor
Tap a loaded slot to open the plugin’s editor. If the plugin has a custom UI (shown by the UI badge in the browser), its graphical interface opens as a full-screen overlay.
See Plugin Editor & Parameters for details on the editor interface.
Plugin Slot Context Menu (Long-Press)
Long-press any loaded slot to reveal advanced options:
[SCREENSHOT: Context menu appearing after long-press on a loaded slot]
| Option | Description |
|---|---|
| Open Editor | Opens the plugin’s graphical interface |
| Route Clips / Unroute Clips | Toggles whether recorded clips on this track pass through the plugin chain. When “Unrouted,” clips play dry. Useful for instruments. |
| MIDI Channel | (Instrument plugins only) Sets the MIDI channel the plugin responds to. Omni listens on all channels. |
| Enable/Disable Plugin Audio | Bypasses the plugin’s audio output without unloading it. Useful for instruments when you only want to capture MIDI, not live audio. |
| Remove Plugin | Unloads the plugin from this slot (destructive — preset state is lost unless you save it in the plugin’s own UI first) |
Removing a Plugin
Method 1 — Long-press menu:
- Long-press the loaded slot
- Tap Remove Plugin
- Confirm in the alert
Method 2 — Alert shortcut: Any slot’s long-press menu will show Remove Plugin at the bottom.
Warning: Removing a plugin discards any unsaved parameter tweaks you made in this session. If you want to keep your settings, save them as a preset inside the plugin’s own editor before removing.
Slot Order and Signal Flow
Plugins process audio in slot order: Slot 1 → Slot 2 → Slot 3 → Slot 4.
[SCREENSHOT: Diagram of slot signal flow: clips → slot 1 → slot 2 → slot 3 → slot 4 → output]
You cannot reorder slots by dragging. If you need a different order, you’ll need to remove and reload plugins in the desired sequence.
Saving Plugin State with the Project
Plugin parameter settings are saved automatically when you save the project (💾 button or auto-save). On next open, every plugin is reloaded with its saved state — you won’t need to re-dial in your tone.
Troubleshooting Plugin Load Failures
If a plugin fails to load, an alert shows the error message. Common causes:
- Plugin app not installed — The AUv3 extension’s host app was deleted from your device. Reinstall it from the App Store.
- Plugin not compatible — Some older Audio Unit v2 plugins are not supported. Look for the AUv3 badge to confirm compatibility.
- Insufficient resources — Running many neural amp plugins simultaneously can exhaust CPU or memory. Try removing unused plugins from other tracks first.