SuperCollider: I/O, analysis and integration
Learning objectives
- learner can receive and send MIDI and OSC and remap external data to sound live
- learner can extract audio features (pitch, amplitude, FFT/MFCC) for responsive systems
- learner can build GUI controls and sonify external data
Capstone — one whole task that evidences the objectives
Build a SuperCollider instrument driven by live MIDI input and OSC, with a small GUI, whose synthesis parameters are steered in real time by pitch/amplitude/FFT analysis of the incoming audio, and route MIDI out to a DAW.
Prerequisite modules
This module turns SuperCollider from a closed synthesis sandbox into the hub of a real performance rig. On stage — a laptop, a MIDI keyboard, a phone sending OSC over Wi-Fi, and a DAW recording the set — the instrument that matters is the one that listens: to your hands, to the network, and to its own audio. The capstone is exactly that instrument: MIDI-playable, OSC-steerable, self-analysing, GUI-monitored, and feeding MIDI back out to a DAW.
The arc starts with MIDI input. Get notes sounding from a keyboard using the MIDIdef callback pattern, drilling per-note synth tracking so held chords release cleanly (“ADSR gate management requires per-note synth node tracking”). Next, open the network side: send and receive OSC with NetAddr and OSCdef, then practise re-evaluating an OSCdef live to remap phone-sensor data onto synthesis parameters mid-performance. In parallel, wire a machine-listening front end — SoundIn feeding Pitch and Amplitude UGens, then FFT frames for spectral shape (the foundation MFCC analysis builds on) — so the instrument reacts to what it hears. Finally, wrap it in a small Window of sliders and views, and route MIDIOut through a virtual bus to the DAW, minding the channel off-by-one and latency defaults.
Every required atom gates the capstone: without the MIDI procedure (connectAll, per-note tracking, gate management), notes hang; without OSC and live remapping, external data cannot steer sound; without the analysis UGens and mic input, parameters have nothing to follow; without GUI composition and mapping strategy (linear vs exponential scaling from sonification practice), the instrument is neither controllable nor musical. Supporting atoms widen the horizon — earlier MIDIdef concept references, OSC’s design rationale, mouse control as a pre-MIDI stepping stone, reproducible seeds, machine-listening performance systems, spatialization and granular textures — enriching where the instrument can go once it works.
Runnable examples
Generated from the context/ instrument corpus by concept (redistributable idioms only). Do not edit — regenerate with gen-module-examples.mjs.
physical-modeling
Mandolin m => dac; 0.9 => m.pluck; 220 => m.freq;
chuck-0043 · MIT
Atoms in this module
Required — these gate the capstone
Supporting — enrichment, not gating
Part of curricula
- Live Coder — zero to performing live-coded music — Generative Systems & the SuperCollider Stack recommended