A live-coding setup file pre-loads server memory, sample dictionaries, SynthDefs, a clock and a safety limiter before the set

Live coding in SuperCollider needs preparation so that stage time goes to composition, not infrastructure. A Setup.scd file handles that upfront: it increases the number of buffers and the server memory for CPU-heavy work; loads a folder of samples into a nested dictionary where the folder name becomes an entry and files become sub-entries (so a kick is reached as d[“k”][1]); loads custom SynthDefs such as bplay for sample playback; starts StageLimiter from the BatLib quark to protect ears; and establishes a 60 BPM proxy tempo clock so patterns stay in sync. Running one file at boot leaves the performer ready to make music immediately.

Examples

d[“k”][1] reaches the second kick sample; the 60 BPM proxy clock means dur values are read in whole-note terms; StageLimiter guards the output bus against accidental clipping.

Assessment

List five categories of infrastructure a setup file should establish, and explain why loading samples into a nested dictionary is more stage-usable than separate Buffer.read calls.