Combine offsets
Merge two step patterns into one rhythm
- offset1
- offset2
- OFFSET
Combine offsets is the companion to Transform offset in the Advanced Latent Control pack. Where Transform offset makes a single on/off step pattern, Combine offsets merges two of them into one and lets you nudge the combined result. You feed it two OFFSET inputs and get back one OFFSET for a transform's offset_optional socket.
The inputs
offset1andoffset2- the two OFFSET patterns (usually two Transform offset nodes).offset- an integer that shifts the combined pattern, applied after merging.
That's the whole interface. The merge is an OR: a step is active if either pattern is active on that step. The author's example shows how two sparse patterns interleave into something livelier: pattern 0 0 0 1 (every 4th) combined with 0 0 1 (every 3rd) yields 0 0 1 1 0 1 0 1 1 0 0 1 - a rhythm neither pattern alone produces.
Why you'd use it
Because a single Transform offset is a metronome, and sometimes you want a polyrhythm. Combine a process_every: 2 and a process_every: 3 offset and you get a pattern where some steps fire two steps apart and others four - an irregular pulse that makes a transform feel alive instead of mechanical. It's the difference between "mirror every 4th step" and "mirror on a pattern that breathes." People reach for this when a single-period gate feels too robotic.
The extra offset input is a fine-tune: it slides the merged pattern around so you can align its active steps with specific phases of the sampling trajectory. It works like Transform offset's own offset field (wrapping modulo the period), but applied to the union.
When to bother
Honestly, this is a power-user node. If you're new, one Transform offset on one transform will teach you 90% of what offsets do. Combine offsets earns its place when you're stacking transforms - a mirrored symmetry edit on a polyrhythm, a multiply pulse on another - and you want the two gates to interlock rather than fire together. That's also where its subtlety hides: an OR merge means overlapping steps fire both transforms simultaneously (in sequence, per Combine transforms order), so some steps get a double dose. If that surprises you, you've found the node's personality.
Install
Same repo as the rest of the pack:
cd ComfyUI/custom_nodes
git clone https://github.com/RomanKuschanow/ComfyUI-Advanced-Latent-Control
Restart, or install "Advanced Latent Control" via ComfyUI Manager. No models, no dependencies.
The one-liner
Combine offsets takes two clocks and makes one composite clock. Nothing more, nothing less - and that's exactly what you want when your transforms deserve a rhythm that a single period can't express.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| offset1 | OFFSET | — | |
| offset2 | OFFSET | — | |
| offset | INT | 0-10000–10000 | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| OFFSET | OFFSET | — |