Docs / Scenes & Presets / Scenes

Scenes

A scene is a photograph of the entire mixer: every channel and bus, every fader, every EQ curve, every routing switch, every effect. Save one per context — Streaming, Gaming, Meetings — and switch your whole audio life with one click.

Open the Scenes window with Scenes in the menu bar.

The Scenes window — a 2×3 grid of 6 slots, each occupied slot showing the scene's name, save timestamp, and four actions (▶ Load · ↺ Overwrite · ↓ Export · ✕ Delete). Empty slots show + Save here. Bottom bar: a name field with SAVE and an ↑ Import button for .ngss files.
The Scenes window — six named checkpoints for the whole mixer.

The six slots

Scenes live in a 2×3 grid of 6 slots. Each occupied slot shows the scene's name, when it was saved, and four actions:

ActionEffect
▶ LoadRecall the scene — the whole mixer snaps to the saved state.
↺ OverwriteReplace the slot's contents with the current mixer state.
↓ ExportSave the scene to a .ngss file — for backup or sharing.
✕ DeleteFree the slot.

Saving a new scene: type a name in the field at the bottom and hit SAVE (lands in the first free slot), or use + Save here on a specific empty slot. ↑ Import loads a .ngss file from disk into a slot.

The active scene's name appears as the 🎬 chip in the monitor bar, and its slot is highlighted in the grid.

What's saved — and what deliberately isn't

A scene captures the full mixer state: channels with all their processing (EQ, gate, compressor, FX, spatial), buses with theirs, routing, sends, groups, fader positions, mutes.

Two things are intentionally left out:

  • Solo states — solo is a temporary listening tool; scenes always load solo-free so a forgotten solo can't ambush your next session. (Why)
  • Global app settings — driver mode, buffer size and theme belong to the app, not the mix.

Scenes vs. auto-save — no conflict

Aura Mixer continuously auto-saves your working state — close the app, reopen, everything's where you left it, no scene involved. Scenes are something else: named checkpoints you return to on purpose. Load a scene, tweak it for an hour, and the original snapshot stays untouched until you explicitly Overwrite it.

💡 Editing a loaded scene

After loading a scene you immediately start "editing" it (auto-save tracks your tweaks as the working state). If the tweaked version is the better one — ↺ Overwrite the slot. If not — ▶ Load it again and you're back to the checkpoint.

Sharing and backup

The .ngss export is a plain file: park copies of your battle-tested streaming setup in cloud storage, move scenes to a second PC, or trade them with friends. One caveat travels with the file: device assignments reference your hardware, so on another machine the strips arrive intact but may need their devices re-picked in SETUP.

Cloud sync — your scenes on every PC ⭐ (Premium · coming soon)

🔜 Not available yet

Cloud sync arrives alongside online accounts as a Premium feature — included with Premium (not a subscription) and optional. Until it ships, your scenes live on this PC and travel as .ngss files (above).

With Premium, every scene you save is also stored in your account in the cloud — automatically, with no manual export. Sign in on another computer and your scenes are already there: build a Streaming snapshot on your desktop and find it waiting on your laptop. Because they ride along with your account, a reinstall or a dead drive can't take your library with it.

Manual .ngss export stays for everyone — it's still how you share a single scene with a friend or hand one to someone without an account. Premium cloud sync just removes the copying-between-machines chore for your own setups.

stuck? ask on Discord
An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.