Skip to content

Presets and Persistence

Built-ins are read-only researched configurations. Production menus show only operational presets. Future catalog entries remain hidden until their research, shared engine strategy, controls, capability gates, persistence, and note ownership are complete.

Save As captures the current arrangement configuration with user-authored metadata. Custom arrangements remain distinct from built-ins and can be edited or deleted.

Applying an arrangement preserves:

  • tonic/key
  • BPM and transport state
  • connected devices
  • input and output routing
  • selected sound
  • master level
  • mute and solo state
  • hosted plug-ins

Storage depends on the surface. Browser data belongs to the current browser profile and site origin. Desktop and plug-in surfaces can also participate in native or host state, but do not assume browser custom presets automatically synchronize to a desktop app or another computer.

Before clearing browser site data, resetting a plug-in, or reinstalling, export or record any custom settings the surface allows you to preserve. Built-in arrangements can be restored from the application; user-authored metadata may not be recoverable after storage is cleared.