h4 - Seed Sequencer

The h4 - Seed Sequencer is the MissionControl family's standalone seed utility, and its one genuinely unusual feature is in the name: it remembers. Set auto_advance on and the node tracks its own seed between runs, so you don't need the pack's global loop counter or a broadcast system to sweep seeds - this single node handles sequencing by itself. It's the "chaos controller" of the family: fixed, incrementing, or random, with a self-contained memory that makes it work even in a graph with no other h4_Live loop nodes.

It's also the descendant of a node called h4_SeedBroadcaster, which tells you what it's for: feeding a sequence of seeds to samplers in an orderly way.

How it works

Give it a base seed and pick a mode:

• fixed - same seed every run. Your reproducibility anchor.
• increment - adds increment_step each run. Run 0 uses the base, run 1 is base+step, run 2 is base+2*step. This is a controlled sweep with whatever step size you want, not just +1.
• random - rolls a new seed, with random_digits controlling the size: set 4 and you get 4-digit seeds (1000–9999), set 10 for a proper 10-digit range.

The auto_advance toggle is what makes the increment and random modes feel alive: with it on, the node persists its own state so each queue run picks up where the last left off, even across a ComfyUI restart (state lives for the session). Turn it off and the sequencer resets to the base anchor each run - which is what you want when you're debugging and need reproducibility.

The inputs that matter

• seed - the base anchor.
• mode - fixed, increment, or random.
• increment_step - how much to add per run in increment mode.
• auto_advance - remember the seed for next time, or reset each run.
• random_digits - seed size in random mode.

One output: seed (INT), converted into your sampler's seed input.

Installing it

It's part of h4_Live:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_Live
# restart ComfyUI

or ComfyUI Manager → search "h4_Live." No extra dependencies.

Where it can bite you

Because it keeps its own state, it's easy to lose track of "which seed am I on" - the auto-advanced value isn't always obvious on the canvas, so if you get a run that doesn't look like it follows from the last, check whether auto_advance is silently moving you forward. It also duplicates what the pack's Seed Generator already does via the global loop counter, so having both in one workflow is redundant: pick the Sequencer if you want self-contained behavior, the Generator if you want everything driven by Mission Control's counter. Two seeds in the same graph is a recipe for confusion, not variety.