Nodes/Power Noise Suite for ComfyUI/Cross-Hatch Power Fractal Settings 🦚
ComfyUI Node

Cross-Hatch Power Fractal Settings 🦚

Tune the hatching once, feed it to the sampler and the generator

By WASasquatchΒ·Created 3 years agoΒ·Updated 2 years agoΒ· 81
Cross-Hatch Power Fractal Settings 🦚
    • ch_settings
    β—„frequency320.000β–Ί
    β—„octaves12β–Ί
    β—„persistence1.500β–Ί
    β—„num_colors16β–Ί
    β—„color_tolerance0.050β–Ί
    β—„angle_degrees45.00β–Ί
    β—„brightness0.000β–Ί
    β—„contrast0.000β–Ί
    β—„blur2.50β–Ί

    This node doesn't generate anything. It's a settings bag - a bundle of parameters that comes out the other end as a single CH_SETTINGS object you can plug into the nodes that actually do the work. Specifically, that means the Power KSampler Advanced and the Cross-Hatch Power Fractal generator both accept ch_settings, so you can tune your cross-hatch pattern in one place and reuse it everywhere without re-typing nine numbers.

    Think of it like a preset capsule. You dial in frequency (line density), octaves (fractal detail layers), persistence (how fast octave amplitude decays), num_colors (how few flat shades the pattern is quantized to), color_tolerance (how crisp the color boundaries are), angle_degrees (hatching direction), brightness, contrast, and blur - the exact same set of knobs the Cross-Hatch Power Fractal node exposes directly. The node just packages them into a dict and hands it out.

    Why use it at all

    Because of the sampler. The Power KSampler Advanced lets you plug ch_settings in to generate cross-hatch noise at every denoise step instead of power-law noise - and when it does, it uses these exact values. If you were fiddling with the standalone Cross-Hatch node to find a look you liked, this settings node is how you hand that same look to the sampler: build it here, wire it to both, and the two are guaranteed to agree. The KSampler also treats a plugged-in ch_settings as "cross-hatch mode" - the README notes it disables plain Power-Law noise, and ppf_settings will override it if both are connected.

    There's a second, subtler benefit: workflow cleanliness. A settings node keeps the sampling node from becoming a wall of floats, and it makes the noise profile a single visible object you can swap, bypass, or reuse across workflows. It's the same pattern as a lot of the ecosystem's "settings" nodes - cheap to build, nice to have.

    Output

    One ch_settings output. Feed it to:

    • Power KSampler Advanced β†’ ch_settings input, for cross-hatch noise during sampling.
    • Cross-Hatch Power Fractal β†’ ch_settings input, which then overrides that node's individual fields - handy because the generator's own params can be a trip hazard when you've also wired a settings node in.

    Install

    It's part of Power Noise Suite, so it comes with the one-install pack. ComfyUI Manager β†’ search "Power Noise Suite", or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/WASasquatch/PowerNoiseSuite
    

    Restart. Nothing else to fetch - torch is the only dependency.

    Gotchas

    The one confusion this node reliably causes: its inputs shadow the generator's own inputs. If you wire ch_settings into Cross-Hatch Power Fractal, the settings node's values win and the fields on the generator are ignored - people tweak the wrong node and wonder why nothing changes. Pick one place to tune (the settings node) and leave the generator's matching fields alone. Same story on the sampler: ch_settings overrides its power-law noise path, so don't expect noise_type to still matter while it's plugged in.

    CategoryPower Noise Suite/Sampling/Settings

    Inputs (9)

    NameTypeDefaultDescription
    frequencyFLOAT320.0000.001–1024β€”
    octavesINT121–32β€”
    persistenceFLOAT1.5000.001–2β€”
    num_colorsINT162–256β€”
    color_toleranceFLOAT0.0500.001–1β€”
    angle_degreesFLOAT45.000–360β€”
    brightnessFLOAT0.000-1–1β€”
    contrastFLOAT0.000-1–1β€”
    blurFLOAT2.500–1024β€”

    Outputs (1)

    NameTypeDescription
    ch_settingsCH_SETTINGSβ€”