Saving your work
A snapshot holds the whole instrument — patterns, sounds, levels, and the driver's own state. Two things it cannot hold, and one trap in the web interface.
Try it
- On the touchscreen (or through VNC in a browser), open the snapshot list and enter a bank.
- The first entry is Save as new snapshot. That is the one.
- To load, pick any snapshot in the list. Everything comes back — including which channels you had switched, and who owned each pattern.
The trap
In webconf's Snapshots page, the Name field and its checkmark RENAME THE SELECTED BANK. They do not save a snapshot.
It looks exactly like a save box. It is not one. Save from the touchscreen or VNC.
What a snapshot carries
The patterns themselves, play chance and swing, mixer levels and mutes, both effect sends per channel, and each channel's kit or preset.
Plus the driver's own state, which exists nowhere else: every voice's Turing register and its four-deep undo ring, the voice parameters, the globals, which channels you switched kind on, who owns each pattern, your modulators — depth, rate, shape, position and base — and the mode and page you were in.
A set saved mid-sweep comes back at the value you dialled in, not wherever a modulator happened to be when you saved.
What it will not carry, and why
A mute set on the sequencer does not persist. Mute the mixer strip instead — that is in the snapshot, and it shows on the touchscreen mixer too.
Amber provenance on a drum channel does not survive a reload. Your take does; the colour does not. A played drum note has the same pitch as a generated one, so once the pattern is read back nothing can tell them apart. The PLAY indicator remains the authority.
See also
- Playing and recording — what ownership means, and why amber matters
- Modulation — modulators are saved running