Sequencing
Move from static sound into clocked motion, rhythm, and tonal control.
- clock, trigger, gate
- sequencers and quantizers
- melodic and rhythmic motion
Learn the timing logic behind modular sequencing by understanding clock pulses, triggers, and gates as different control events.
Move from static sound into clocked motion, rhythm, and tonal control.
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:
Before melody, rhythm, variation, or generative structure, a modular system needs timing.
It needs a way to answer questions like:
Three of the most important timing signals are:
These are not sound sources. They are control events that organize behavior in time.
If you do not understand these signals, sequencing can feel mysterious very quickly.
You may patch a sequencer and see lights moving, but not know:
Once clock, trigger, and gate become clear, modular sequencing stops feeling like magic and starts feeling like signal logic.
A clock provides regular timing pulses.
Its job is not to describe pitch or timbre. Its job is to create a repeating time reference that other modules can follow.
Typical uses include:
A clock answers this question:
A trigger is a very short pulse used to start an event.
It is often used for:
A trigger is about the start of something, not its duration.
A trigger answers:
A gate stays high for a length of time.
That makes it useful when duration matters.
Typical uses include:
VCA or logic state activeA gate answers:
This is the distinction that matters most:
In practice, a trigger can begin a note, but a gate often determines how long the note is held.
You can think of the three signals like this:
This is not a full technical definition, but it is a very useful working model.
A simple patch might look like this:
graph LR
CLK[Clock<br/>Pulse] -.->|Advance| SEQ[Sequencer]
SEQ -.->|Trigger| ENV[Envelope]
SEQ -.->|Gate| HOLD[Note Hold Behavior]
SEQ -.->|Pitch CV| OSC[Oscillator]
ENV -.->|Level| VCA
OSC ==>|Audio| VCA
classDef signal fill:#1A202C,stroke:#2D3748,stroke-width:2px,color:#E2E8F0;
classDef mod fill:#2A4365,stroke:#2B6CB0,stroke-width:2px,color:#EBF8FF,stroke-dasharray: 4 4;
classDef time fill:#2C5282,stroke:#2B6CB0,stroke-width:2px,color:#EBF8FF,stroke-dasharray: 2 2;
class OSC,VCA,HOLD signal;
class SEQ,ENV mod;
class CLK time;
Here the roles are separated:
This is why timing feels musical instead of random.
If you use a short trigger to fire an envelope, you often hear:
If you use a gate with visible duration, you often hear:
This is one of the first big sequencing lessons: timing is not only about when something starts, but also about how long it lives.
VCA logicRecognizing these destinations makes patch reading much easier.
They are related, but they do different jobs. If you confuse them, the articulation of the patch can feel wrong even when the rhythm looks correct.
The clock is only a reference pulse. Rhythm appears when that pulse is divided, skipped, transformed, or interpreted by other modules.
Very often the issue is not pitch or tone. It is the timing behavior of the control signals.
A strong habit is to ask:
That question makes sequencing systems much easier to understand.
Patch one voice and compare two behaviors:
Use the same oscillator, filter, and VCA if possible.
Then listen for:
Take one clock source and build three small tests:
Then write one sentence for each:
Once clock, trigger, and gate are clear, the next step is sequencing actual pitch material.
That is where sequencers and quantizers start turning timing structure into musical note patterns.
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.