ComfyUI Node

seed _O

A seed you can actually route around the graph

By omar92·Created 3 years ago·Updated 5 months ago· 181
seed _O
    • INT
    seed0

    ComfyUI's KSampler already has a seed field, so a node that's just a seed widget looks redundant - until you want that seed to be a value in the graph rather than a setting buried on a sampler. seed _O is exactly that: one seed input, one INT output, nothing else. It's the seed-shaped building block under O/utils in the Quality of Life Suit.

    The genuinely useful pattern is when the same randomness should drive multiple things. In this pack, the ChatGPT nodes all take a seed input - wire this node's output into the seed port of a ChatGPT Simple _O and a KSampler's seed simultaneously, and you can reason about your runs as a single "what seed did I use" knob instead of chasing four separate fields. It also plays nicely with workflow automation: a seed you can route means a seed you can compute or vary programmatically.

    How it works

    seed _O takes an INT (default 0, range up to 2^64−1, matching ComfyUI's seed conventions) and returns it unchanged. There's no hashing, no randomization, no "randomize" button built in - it's a pure pass-through. If you want random seeds, the KSampler's own control or a wildcard mechanism is what you're after; this node is for holding a seed in one place and sharing it.

    The one thing worth knowing: the pack's OpenAI nodes accept a seed but don't actually use it to make outputs reproducible - OpenAI's chat API doesn't expose a seed parameter, so the field is decorative there. But the INT output is real and can drive any genuine seed consumer.

    Installing

    Pack-wide, as always:

    cd ComfyUI/custom_nodes
    git clone https://github.com/omar92/ComfyUI-QualityOfLifeSuit_Omar92.git
    

    or ComfyUI Manager → search ComfyUI-QualityOfLifeSuit_Omar92, then restart ComfyUI (a refresh alone won't load the nodes). Zero dependencies.

    Honest verdict

    It's a one-input one-output utility node; nobody's building a career on it. You'll use it because a workflow you downloaded references it, or because you like keeping seeds as explicit graph values. Both are legit reasons. It's the kind of tiny convenience node that does nothing flashy and quietly makes your life easier - which is, in fairness, the whole point of the pack it ships in.

    CategoryO/utils

    Inputs (1)

    NameTypeDefaultDescription
    seedINT00–18446744073709550000

    Outputs (1)

    NameTypeDescription
    INTINT