Projects and storage

s32 --loopback list
s32 --loopback active
s32 --loopback storage
s32 --loopback pull internal 1 /tmp/p1.s32p
s32 --loopback push /tmp/p1.s32p
s32 --loopback --yes push /tmp/p1.s32p --activate

list and active are aliases for project list and project active.

Library

Command	Notes
list	* marks the active project
active	Dirty flag and generation
storage	Per-volume capacity and job state
pull VOLUME UID OUT.s32p	VOLUME is internal or sd
push IN.s32p [--activate]	--activate prompts (or --yes)
project create VOLUME NAME [--seed empty|daw]
project delete VOLUME UID	Prompts
project rename VOLUME UID NAME
project duplicate VOLUME UID NAME	Prints the source uid and job handle. job HANDLE (Done) or list shows the copy uid.
project load VOLUME UID	Prompts; replaces the live session
project save	Write the live project in place
abort	Cancel an in-flight push

internal is onboard storage. sd is microSD. Raw microSD pull/push may be unavailable on some firmware; s32 reports that status instead of inventing a path.

s32 --loopback --yes project create internal Scratch --seed empty
s32 --loopback --yes project load internal 2
s32 --loopback project save

A push without --activate stores a record and does not change the live project. Confirm with active after both forms.

If a push is interrupted, power-cycle the S32 before you rely on knobs or MIDI. Keep a pull copy so you can restore.

Files

.s32p is a full project record. Archive it, restore it with push, or decode it with the layout JSON from s32 layout --emit-layout-json.