SuperCollider is two separate processes: a language client and a sound server

SuperCollider consists of two distinct applications that communicate over a network socket. The language (sclang) is where you write and evaluate code; it sends instructions to the server. The server (scsynth) is the sound engine — it generates audio samples. Every sound you hear comes from the server; everything you type runs in the language. This two-process architecture means you must boot the server before making sound. Beginners often forget the server starts off by default. Boot it with ctrl+B; the Status Bar turns green when successful. Running {SinOsc.ar}.play without a booted server will fail silently.

Examples

Boot with s.boot (code) or ctrl+B (keyboard). Check the Status Bar: zeros = server off, green numbers = server on. Every .ar UGen runs in the server; every variable assignment runs in the language.

Assessment

Without running code, explain why {SinOsc.ar}.play produces no sound immediately after opening SuperCollider. What two steps are required? What does the Status Bar look like before and after booting?