Build a Shared Timing Backbone

A large self-running patch becomes easier to control when its parts share one sense of time. We will create several trigger lanes from the same one-bar device phase instead of placing an unrelated LFO beside every sound.

The Idea #

The timing block should create different time scales:

• fast pulses for percussion details;
• normal note events for melody;
• slower events for bass and accents;
• bar and phrase events for structural changes.

All lanes come from the same phase, so they remain related when the tempo changes or the transport restarts.

Build It Step by Step #

1. Open Grid System 00 - Skeleton.
2. In the TIMING area, add four Triggers modules.
3. Let their phase pre-cords use the one-bar device phase.
4. Set the modules to 4, 8, 16, and 1 events per cycle.
5. Label their outputs MAIN, NOTES, DETAIL, and BAR.
6. Connect each lane to the Oscilloscope one at a time.

You should see four related patterns:

Device phase -> Triggers 4  -> MAIN
             -> Triggers 8  -> NOTES
             -> Triggers 16 -> DETAIL
             -> Triggers 1  -> BAR

The names describe intended jobs, not fixed musical values. Later you can change the number of triggers without renaming every destination.

Add a Phrase Trigger #

1. Add Clock Divide after the BAR lane.
2. Set its division to 4.
3. Label the result PHRASE.
4. Watch it with the Oscilloscope for at least four bars.

The phrase lane fires once every four bar events. We will use it for slow memory changes and larger shifts in density.

Add One Uneven Lane #

1. Add another Triggers module and set it to 5.
2. Add Clock Quantize after it.
3. Use the DETAIL lane as the reference clock for Clock Quantize.
4. Label the result ODD.

Five events are now moved onto the shared sixteen-pulse grid. The result is uneven but still synchronized. Try 3, 5, 7, or 9 source events and keep the version that creates a useful pattern.

Checkpoint #

The timing block should now produce six named signals:

• MAIN: four events per bar;
• NOTES: eight events per bar;
• DETAIL: sixteen events per bar;
• BAR: one event per bar;
• PHRASE: one event every four bars;
• ODD: an uneven pattern quantized to the detail grid.

Change the project tempo. Every lane should speed up or slow down together. Stop and restart transport several times and confirm that the patterns return to the same bar structure.

Save the preset as:

Grid System 01 - Timing

Common Problems #

A slower lane drifts away from the others #

Check that it is derived from BAR, MAIN, or another shared lane. A free-running LFO has its own timeline and may not restart with the system.

Clock Quantize produces no obvious change #

Compare its input and output on the two Oscilloscope traces. The source events must fall between reference pulses before quantization becomes visible.

The patch starts in an unexpected position #

Confirm that the device phase follows the project transport. If you later need a local manual restart, place Phase In through Ø Reset and feed that phase into the Triggers modules instead of their pre-cords.

Extend the System #

Create a second phrase lane with Clock Divide set to 8 or 16 bars. Do not connect it yet. Label it SECTION. It can later change harmony, enable a layer, or move between larger states.

In the next lesson the NOTES lane will decide when the pitch engine chooses a new note.

▶ Next Lesson: Build a Pitch and Harmony Engine
◀ Previous Lesson: Plan the Patch Architecture
▲ Building Large Bitwig Grid Patches