Devices
The Devices view is the studio’s Ableton-style device strip: for each track, the
instrument followed by its effect chain, each device showing its parameters. It
is a projection of the fx.* data and synth params in your song file — and it
writes those params back.
What it projects
Section titled “What it projects”- Per track: an instrument box (the synth id or
sampler/midikind, with itsparams) followed by one box per effect in the static chain, in order, each showing itseffectIdand parameter values. - The master row: the master-bus effect chain (
song.setMasterEffects(...)), rendered last. A muted (default) tag marks the implicit tuned chain when a song hasn’t declared one.
How it writes back
Section titled “How it writes back”Effect params whose value is a plain literal in main.ts are editable, and
commit straight into the source:
- Numbers: drag to scrub (
0.01steps; shift for coarse), or double-click to type. - Enums: a select — e.g. a
filter’stype(lowpass/highpass/bandpass), or asidechain’ssource(the other track names).
Computed values — anything that isn’t a plain literal (a spread, a value defined in another file, an expression) — render locked, with a hover lock icon and a reason: “edit it in code.” The panel stays calm and read-only-looking until you hover, then reveals the affordance.
The master chain is read-only by design
Section titled “The master chain is read-only by design”The master row never offers write-back. The master chain is code-owned through
song.setMasterEffects([...]), and the projection here is read-only on purpose
— so the one place that shapes the whole mix is always edited deliberately, in
code. Track instrument params are likewise shown read-only (the instrument box
carries no edit context); effect params are the write-back surface.