Modular in software: VCV Rack for learning & planning
Learning objectives
- learner can navigate VCV Rack — add modules, patch cables, and stack outputs
- learner can apply VCV's voltage standards and cable types to build patches that transfer to hardware
- learner can use VCV's polyphony model and gotchas (one-sample delay, dBFS) when prototyping
Capstone — one whole task that evidences the objectives
Recreate a hardware patch idea entirely in VCV Rack — correctly typed audio/CV cables, at least one polyphonic chain — and document how its voltages and quirks map to a real Eurorack build.
Prerequisite modules
Eurorack is expensive and unforgiving: a wrong module choice costs hundreds of euros and rack space. This module builds the skill that saves you from that — prototyping a complete modular patch in VCV Rack so faithfully that it doubles as a shopping list and wiring diagram for a real build. That is how working modular artists actually plan systems, and it is also a legitimate performance rig in its own right for techno and ambient sets on a laptop.
The arc starts fully supported: install Rack, then get fluent with the two motions you will repeat hundreds of times — adding modules via the Module Browser (right-click an empty rack space) and fanning one output to many inputs with Ctrl-drag cable stacking. These are the part-task drills; they must become reflexes so your attention stays on the patch, not the tool. From there, exercises tighten the conceptual screws: distinguishing audio from CV cables, internalising the voltage standards (±5 V audio, 0–10 V CV, 10 V gates) and the 1 V/oct pitch convention, because these are exactly what transfer — or fail to transfer — to hardware. A final scaffolded step introduces a polyphonic chain and the two quirks that bite prototypers: the one-sample cable delay that silently breaks clock/reset ordering, and Rack’s dBFS metering where full scale is 10 V.
Every required atom is load-bearing for the capstone: you cannot recreate, correctly type, and document a transferable patch without them. The supporting atoms deepen the same territory — how mono modulation fans across polyphonic voices, why “signal type” is a functional convention rather than a physical one, and why raw modular output still needs mix processing — enrichment worth reading, but the capstone stands without them.
Runnable examples
Generated from the context/ instrument corpus by concept (redistributable idioms only). Do not edit — regenerate with gen-module-examples.mjs.
gain-staging
(saw 110) * dbamp (-12) >> audio
punctual-0010 · CC0-1.0
SinOsc s => Dyno d => dac; d.limit();
chuck-0028 · MIT
Atoms in this module
Required — these gate the capstone
Supporting — enrichment, not gating
Part of curricula
- Dawless Performer — hardware jam to recorded live take — Signals, voices, and the DAWless mindset required