This content is currently under development. If you are an editor, enter your password.
Patching and Signal Flow
Asset not found in manifest.
In a modular system, nothing is connected until you patch it. Every wire is a decision. That is what makes modular synthesis powerful and also what makes it confusing at first — there is no default signal path, no preset routing, no automatic connection between the oscillator and the output. You build the entire instrument from the ground up, one cable at a time.
This guide starts in VCV Rack for a reason. It forces you to understand signal flow. In a closed synth with a keyboard and a panel of knobs, the wiring is hidden. You can make sounds without understanding how they are made. In VCV Rack, if you do not patch the oscillator to the filter to the VCA to the output, you hear nothing. That transparency is the point.
Audio Rate vs. Control Rate
Signals fast enough to be heard as sound — typically 20 Hz to 20,000 Hz. In a modular synth, oscillators generate audio rate signals. Audio rate signals can also be used for modulation (FM synthesis, for example), though they are often too fast for controlling parameters smoothly.
Signals slow enough to control parameters rather than generate sound — typically below 20 Hz. LFOs, envelopes, and sequencers produce control rate signals. In VCV Rack and most modular systems, there is no enforced distinction between audio and control rate — a slow oscillator is an LFO, and a fast LFO is an oscillator.
Every signal in a modular synth is a voltage that changes over time. The distinction between audio and control rate is about speed, not type. An oscillator running at 440 Hz produces a signal that vibrates 440 times per second — fast enough to hear as a pitch. An LFO running at 2 Hz produces a signal that cycles twice per second — too slow to hear, but useful for making other parameters move.
The critical insight — and it bears repeating — is that there is no structural difference between the two. An LFO is an oscillator running slowly. An oscillator is an LFO running fast. Speed the LFO up to 100 Hz and it becomes an audio-rate modulator. Slow an oscillator down to 0.5 Hz and it becomes an LFO. VCV Rack does not enforce any distinction between audio and control inputs. You can patch anything into anything.
This is what “using LFOs at audio rate” means — a concept that seems abstract until you try it. Patch an LFO into the frequency input of a VCO and set the LFO to 0.5 Hz. You get vibrato. Now increase the LFO speed to 50 Hz, then 200 Hz, then 1000 Hz. Vibrato becomes FM synthesis. The same connection, the same cable, the same two modules — only the speed changed, and the result went from a gentle wobble to a completely new timbre.
CV: Control Voltage
A voltage signal used to control a parameter of a module — pitch, filter cutoff, amplitude, anything with a CV input. In the standard 1 volt-per-octave system, a 1V increase raises the pitch by one octave. CV is the language modules use to talk to each other.
Control voltage is how modules communicate. A keyboard sends CV to an oscillator to tell it what pitch to play. An LFO sends CV to a filter to make the cutoff sweep. An envelope sends CV to a VCA to shape the amplitude over time. A sequencer sends CV to anything — pitch, filter, effect depth, modulation amount — depending on where you patch it.
The 1 volt-per-octave standard means that for every 1 volt increase in CV, the oscillator’s pitch goes up by one octave. Middle C might be 0 volts, the C above it is 1 volt, the C above that is 2 volts. A semitone is 1/12 of a volt, or about 83.3 millivolts. This standard is what makes modular synthesizers play in tune across modules from different manufacturers.
Not all CV follows this standard. Filter cutoff CV might use a different scaling. Amplitude CV might be 0-10 volts. The point is that CV is a general-purpose language: a varying voltage that controls a parameter. The scaling and range depend on the specific module and the specific parameter.
Gates and Triggers
A signal that is either on or off — high voltage or zero. A gate stays high for as long as a key is held down (or a step is active). Gate length determines how long the sound sustains. Keyboards, sequencers, and clock modules generate gates.
A very short gate — a brief pulse that says 'now.' Triggers fire events: they start envelopes, advance sequencers, reset LFOs. Unlike gates, triggers carry no information about duration. They only mark a point in time.
Gates and triggers tell the synthesizer when to act. A gate says “start now and keep going until I stop.” A trigger says “start now” with no information about duration.
When you press a key on a keyboard, two things happen simultaneously: a CV signal tells the oscillator what pitch to play, and a gate signal tells the envelope to start its attack phase. As long as you hold the key, the gate stays high, and the envelope sustains. When you release the key, the gate drops, and the envelope enters its release phase.
A trigger is used when duration does not matter — when you just need to fire an event. Clock signals are triggers. The ticking of a clock module sends a trigger on every beat, telling sequencers to advance, envelopes to restart, and other modules to do their thing at that instant. The clock does not hold a gate for the duration of the beat; it pulses and moves on.
Understanding the difference between gates and triggers matters for sequencing. A gate sequencer lets you control the length of each step — long gate for legato, short gate for staccato. A trigger sequencer fires the same short pulse on every active step. De-aggregated sequencing takes this further: separate the gate sequence from the note sequence so they run independently on different step counts. The gate pattern determines the rhythm while the note pattern determines the melody, and when the two patterns have different lengths, they create phasing polymetric structures that slowly shift against each other.
Building a Voice from Scratch in VCV Rack
The first exercise anyone should do: build a playable synth voice in VCV Rack from stock modules. No third-party modules, no presets, nothing pre-patched.
The basic voice requires five things:
- An oscillator — generates the raw waveform (saw, square, sine, triangle)
- A filter — shapes the harmonic content
- A VCA — controls the volume
- An envelope generator — shapes the VCA (and optionally the filter) over time
- A way to play it — a MIDI-to-CV module that converts keyboard input to CV and gate signals
The signal path: MIDI-to-CV sends pitch CV to the oscillator and gate to the envelope. The oscillator’s output goes to the filter’s input. The filter’s output goes to the VCA’s input. The envelope’s output goes to the VCA’s CV input. The VCA’s output goes to the audio output module.
That is a complete playable synthesizer. It has one voice, one oscillator, one filter, and one envelope. Every synth you have ever used — from a Minimoog to a software workstation — has this architecture at its core, possibly duplicated and elaborated but never fundamentally changed.
From this foundation, complexity grows. Add a second oscillator for thicker sound. Add an LFO modulating the filter cutoff for movement. Add a second envelope controlling the filter separately from the VCA. Route the keyboard velocity to the envelope amount for dynamic response. Each addition is one more cable, one more module, one more decision about what controls what.
Normalization and Default Connections
A default internal connection in a module that is active when no cable is plugged into a specific input. Normalization means the module works 'out of the box' without patching everything. Plugging a cable into a normalized input overrides the default connection.
Most hardware modular modules and some VCV Rack modules use normalization to make common connections automatic. A filter might have its cutoff CV input normalized to an internal envelope — so even without patching anything, the filter sweeps when you play a note. Plug a cable into that CV input and the normalization breaks, replaced by whatever signal you patched in.
Normalization is a convenience, but it can also be a trap. If you do not know a connection is normalized, you might not understand why changing one parameter affects another. In VCV Rack, normalization varies by module. Some modules show normalized connections as dimmed or dashed lines in the panel graphic. Others do not indicate them at all. Reading the module documentation — or just plugging a cable in and listening to what changes — is how you discover normalizations.
The broader lesson is about assumptions. A closed synthesizer (a keyboard synth with a fixed panel) is fully normalized — every connection is made internally, and you can only modify what the manufacturer decided to expose as a knob or switch. A fully modular system has zero normalization — nothing works until you patch it. Semi-modular instruments (like the Moog Mother-32 or Arturia MiniBrute 2) sit in between: a default signal path is normalized so the synth works as a keyboard instrument out of the box, but patch points let you break any normalization and reroute the signal.
Signal Flow in Non-Modular Synths
Every concept in this chapter applies to synthesizers that have no patch cables at all. The signal flow is the same. The vocabulary is the same. The only difference is visibility.
In a soft synth like Vital, the oscillator feeds the filter feeds the amplifier, and envelopes and LFOs modulate the parameters. You cannot see the virtual cables, but they are there. When you drag a modulation source to a destination in Vital’s interface, you are doing exactly what you do when you plug a cable from an LFO to a filter cutoff input in VCV Rack. The synth just hides the cable.
Understanding modular signal flow makes every synthesizer easier to learn. When you sit down with an unfamiliar plugin, you ask the same questions: Where is the oscillator? Where is the filter? How does the envelope connect to the VCA? What modulation routing is available? Those questions map directly to “what would I patch first?” in a modular system.
The eventual goal is transferring modular thinking back into DAW-based workflows. After building patches in VCV Rack, the real payoff is labeling, transferring, and recording those patches — getting the sounds you built into your actual music projects. The modular work is not meant to stay in VCV Rack. It trains a way of thinking about sound that applies everywhere. If you use a DAW like Logic or Ableton, every soft synth you open will feel more transparent once you understand the signal flow underneath.
Debugging a Patch: Why Is There No Sound?
When a patch produces no sound, the problem is almost always in the signal flow. This is where modular transparency pays off — every connection is visible, so you can trace the signal path from oscillator to output and find the break.
The debugging checklist:
-
Is the oscillator running? Check that it has power, is turned on, and is set to an audible frequency. A VCO with its frequency knob fully counterclockwise might be oscillating at 0.1 Hz — too slow to hear.
-
Is the VCA open? A VCA with no CV input and no manual gain is silent. If the VCA is controlled by an envelope, is the envelope getting a gate signal? No gate means no envelope means no sound.
-
Is the gate arriving? If you are using a keyboard or sequencer to trigger notes, check that the MIDI-to-CV module is receiving MIDI and that the gate output is patched to the envelope’s gate input.
-
Is the filter open? A filter with a very low cutoff and no modulation will remove all audible frequencies from the signal. Turn the cutoff up manually to check.
-
Is the output patched? In VCV Rack, the audio output module must be patched and its level must be up. A missing cable from the VCA to the output module is a common oversight.
-
Are cables in the right jacks? Plugging a CV signal into an audio input (or vice versa) will not damage anything in VCV Rack, but it will not produce the expected result. Check that gate goes to gate, CV goes to CV, and audio goes to audio.
Work backward from the output. Start by patching the oscillator directly to the audio output, bypassing the filter and VCA. If you hear sound, the oscillator works. Add the VCA back in. If the sound disappears, the problem is the VCA or its control signal. Add the filter. If it disappears, the filter cutoff is too low. This subtractive debugging process — removing modules until sound appears, then adding them back one at a time — isolates the break quickly.
What to Practice
- Build a basic synth voice from scratch in VCV Rack using only stock modules: MIDI-to-CV, VCO, VCF, VCA, ADSR, and Audio output. Play it from your keyboard or the on-screen keys. Make sure you understand what every cable does before you add anything.
- Add modulation one layer at a time. First, add an LFO to the filter cutoff. Then add a second envelope controlling the filter separately from the VCA. Then add keyboard tracking (pitch CV) to the filter cutoff so higher notes have a brighter tone. Each addition is one cable — observe what changes.
- Practice the two-pathway mindset. Look at your patch and identify every cable that carries audio (oscillator to filter to VCA to output) and every cable that carries control (CV, gates, envelopes, LFOs). Color-code them mentally or use VCV Rack’s cable colors to distinguish them visually.
- Break something on purpose. Remove the gate cable from the envelope and observe what happens. Remove the CV cable from the oscillator and play — the pitch does not change. Unplug the filter from the signal path and listen to the raw oscillator. Debugging gets faster when you have seen what each failure mode sounds like.
- Build a de-aggregated sequencer: use one sequencer for pitch CV and a different sequencer (with a different step count) for gate/trigger. Run both from the same clock. Listen to how the patterns phase against each other and create longer phrases from shorter sequences.
- Open a soft synth you use regularly and map its interface to modular concepts. Find the oscillator section, the filter section, the amplifier, the modulation routing. Identify which connections are normalized (automatic) and which are user-configurable. The exercise is not about patching — it is about seeing the signal flow that the interface hides.
This Course
- 1. What Is Synthesis?
- 2. Oscillators: Where Sound Begins
- 3. Filters: Sculpting the Spectrum
- 4. Amplifiers and Envelopes
- 5. Modulation: Making Sound Move
- 6. Subtractive Synthesis
- 7. FM Synthesis
- 8. Additive Synthesis
- 9. Wavetable Synthesis
- 10. Sampling as Synthesis
- 11. Granular Synthesis
- 12. Physical Modeling
- 13. Effects as Synthesis Tools
- 14. Patching and Signal Flow
- 15. Sound Design Exercises
- 16. Sources and Further Reading
Upcoming Events
Feedback or corrections
© 2026 Beat Kitchen School — beatkitchen.io. Licensed under CC BY-NC-SA 4.0. Free to share and adapt for non-commercial purposes with attribution.