Foundations
Start with signal flow, modulation basics, and first sound design patches.
- CV vs audio
- oscillator, filter, VCA
- envelopes and LFOs
Learn how to separate heard sound from control signals and why that distinction changes the way you patch.
Start with signal flow, modulation basics, and first sound design patches.
Theory, structure, and practical context are all driven from content files.
Concrete repository anchors already exist for this lesson track.
By the end of this lesson, you should understand:
audio means in a modular patchCV means and why it mattersIn modular synthesis, not every signal is sound.
Some signals are meant to be heard. Those are audio signals.
Other signals are meant to change behavior inside the system. Those are control signals, often described as CV or control voltage.
This distinction is one of the most important ideas in modular practice because it changes how you think about patching. A cable is not only a connection. It is a statement about function.
If you do not understand the difference between CV and audio, modular patches can feel confusing very quickly.
You may know that something is “connected,” but not know what that connection is supposed to do.
Once the distinction becomes clear, patches become easier to read:
That is the foundation for envelopes, sequencing, automation, modulation, generative systems, and performance control.
An audio signal is a signal intended to be heard directly.
Typical examples include:
When audio reaches your speakers, headphones, recorder, or DAW input, it becomes the sound result of the patch.
In simple terms, audio answers this question:
A control signal is not primarily there to be listened to. It exists to change the behavior of another part of the system.
Typical examples include:
LFO moving filter cutoffIn simple terms, CV answers this question:
One reason this topic confuses beginners is that the patch cable itself does not tell you whether the signal is audio or control.
The same physical cable can carry:
So the correct question is never just:
The better question is:
Whenever you patch something, ask:
This simple rule solves a large part of beginner confusion.
If the answer is “I should hear it,” you are probably dealing with audio.
If the answer is “it should change something else,” you are probably dealing with control.
Consider this patch:
graph TD
LFO[LFO<br/>Modulation] -.->|Control| VCF
ENV[Envelope<br/>Modulation] -.->|Control| VCA
OSC[Oscillator<br/>Audio Source] ==>|Audio| VCF[Filter<br/>Timbre]
VCF ==>|Audio| VCA[VCA<br/>Level]
VCA ==>|Audio| OUT((Audio<br/>Output))
classDef audio fill:#1A202C,stroke:#2D3748,stroke-width:2px,color:#E2E8F0;
classDef output fill:#2C7A7B,stroke:#319795,stroke-width:2px,color:#E6FFFA;
classDef control fill:#2A4365,stroke:#2B6CB0,stroke-width:2px,color:#EBF8FF,stroke-dasharray: 5 5;
class OSC,VCF,VCA audio;
class OUT output;
class LFO,ENV control;
Here the roles are different:
LFO is controlThis is the point where modular systems begin to make sense. You are not only connecting modules. You are connecting different kinds of behavior.
When reading a patch, use this quick check:
Examples:
it is probably audio.
Examples:
it is probably control.
This is not a perfect technical rule in every module ecosystem, but it is extremely useful for beginners.
Not everything in the patch is part of the audible chain. A lot of modular intelligence lives in control relationships.
CV is only pitchPitch is only one form of control. CV can affect amplitude, timbre, timing, probability, panning, effects, and more.
Beginners often focus on the source of control but forget to ask what the destination input is actually changing.
Just because an LFO can move a parameter does not mean it should. The useful question is whether the motion supports the musical result.
Build a simple patch and test these three signal types:
LFO to filter cutoffVCA levelThen describe each one in one sentence:
Take one modulation source such as an LFO and route it to three different destinations one at a time:
Do not patch all three at once at first.
Listen and write down:
This exercise trains your ear to connect signal type with behavioral outcome.
The next lesson should make this distinction practical by building a complete first subtractive patch.
That is where audio and CV stop being abstract categories and start working together as a playable instrument.
Use the linked patch entries below as concrete repository anchors for this lesson track.
Adjacent lessons in the same track keep the topic progression coherent.
The first system diagram connects the modular engine, DAW layer, and visual output layer.