Scenes

A Scene switches which chain is active on each track. Triggering a scene simultaneously applies the stored chain selection across all tracks, letting you jump between complete performance arrangements in a single action.

Think of scenes like song sections — Intro, Drop, Break, Outro — where each section has a different set of effects loaded on each track.

Creating a scene

Set each track to the chain you want for that section.
The scenes bar runs along the bottom of the editor. If it’s hidden, click the scenes toggle button at the bottom of the Snapshots sidebar to show it.
Click + in the scenes bar to capture the current arrangement — the scene is added with an auto-generated name.
To rename it, right-click the scene card → Rename.

Triggering a scene

Click any scene card in the scenes bar to trigger it.

All tracks instantly switch to the chain stored in that scene.

MIDI trigger

Right-click a scene card → MIDI Learn — move a pad or button on your hardware. The scene triggers on every Note On from that control.

Updating a scene

Right-click a scene card → Overwrite with Current State — the scene is updated to match the current track states.

What scenes store

For each track, a scene captures:

Active chain — which chain is selected on the track
Fader value — the track’s opacity/blend level
Running state — whether the track is active

Scenes do not store effect parameter values or which effects are enabled. The way to have different effects active per scene is to put them on different chains — each chain is an independent effect stack, and the scene switches between them.

For full project parameter recall, use Snapshots →. For recalling effect parameter values within a single chain, use Chain Snapshots →.

Scenes vs Snapshots

	Scenes	Snapshots
Stores	Chain selection, fader, running state	Full project state
Slots	Unlimited	32
Trigger speed	Instant	Async
Use for	Section switching	Full state recall