LatentNoiseList
One latent in, a batch of noised variants out
- latent
- alphas
- ks
- latent_list
Most of RES4LYF's noise nodes give you back one latent. LatentNoiseList gives you back a list - its latent_list output is explicitly marked as a list type, not a single tensor. Feed it one latent and a seed, and it produces a run of noised variants of that latent rather than a single new one, which is the useful bit if you're trying to generate a spread of starting points instead of committing to one.
That's genuinely niche. If you've clicked into this page you were probably already deep in a workflow that wires list outputs into a batch or a "for each" style process - this isn't a node you reach for on a first txt2img graph.
How it works
RES4LYF doesn't publish a written explanation of this node's internals beyond the parameter names, so take the following as a reasonable reading of the schema rather than gospel: alpha looks like a blend-strength dial between the original latent and the noise being mixed in per step, k and the boolean k_flip give you a second axis over how that noise is generated, and steps determines how many variants land in the output list. If you're relying on this node, the fastest way to actually understand it is to wire its output straight into a Preview or Save node per list item and watch what changes as you sweep alpha and steps - the pack's own example workflows (linked from the README) are the other place to see it used in context.
The inputs and outputs that matter
latent(required) - the source latent the list is built from.alpha(default 1) - treat this as a mix-strength control between the original latent and injected noise; sweep it to see the effect on your own graph.k_flip(boolean) - a secondary toggle on the noise pattern.steps- how many entries land in the output list.seed- reproducibility.- Optional
alphas,ks(bothSIGMAS) - schedulealpha/kper step instead of a fixed value. - Output:
latent_list(LATENT, list) - a list, not a single latent. Downstream nodes need to accept a list input (or you need a batching/unpack step) to consume it directly.
How to install it
Via ComfyUI Manager, search "RES4LYF" and install. Manually, from ComfyUI/custom_nodes:
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt
Activate your venv first if you have one; on portable builds use python_embedded\Scripts\pip.exe in place of pip. Restart ComfyUI afterward.
Common issues & troubleshooting
A downstream node rejects the output, or only processes the first item. That's the list output biting you - plenty of ComfyUI nodes expect a single LATENT, not a list of them, and will silently only touch the first entry or error outright. Check whether the node you're feeding actually declares list support before wiring this in.
No documentation exists beyond the node itself. This is one of the more obscure corners of a pack that's already thin on written docs outside its README - there's essentially no community discussion of this node by name. If the defaults don't do what you expect, treat it as an experiment: vary one parameter at a time on a fixed seed and watch the list output, rather than assuming a specific mechanism.
You actually wanted a single noised latent, not a list. For that, reach for LatentNoiseBatch_gaussian_channels or LatentNoiseBatch_perlin instead - both output a single latent, which is a much easier drop-in for a normal txt2img/img2img graph.
Inputs (7)
| Name | Type | Default | Description |
|---|---|---|---|
| latent | LATENT | — | |
| alpha | FLOAT | 1.000-10000–10000 | — |
| k_flip | BOOLEAN | false | — |
| steps | INT | 0-10000–10000 | — |
| seed | INT | 00–18446744073709550000 | — |
| alphasopt | SIGMAS | — | |
| ksopt | SIGMAS | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| latent_list | LATENT | — |