Nodes/comfyui_overly_complicated_sampling/OCSNoise to SONAR_CUSTOM_NOISE
ComfyUI Node

OCSNoise to SONAR_CUSTOM_NOISE

The adapter that connects two noise worlds

By blepping·Created 2 years ago·Updated 2 months ago· 30
OCSNoise to SONAR_CUSTOM_NOISE
  • ocs_noise
  • SONAR_CUSTOM_NOISE

This is the smallest node in the pack and possibly the most quietly useful. OCS has its own noise type (OCS_NOISE), and the author's other project - ComfyUI-sonar - has its own too (SONAR_CUSTOM_NOISE). Most nodes that consume noise accept either type, but not all of them. When you run into one that insists on SONAR_CUSTOM_NOISE and all you have is an OCS noise generator, this node is the one-line adapter that makes the connection legal.

What it is

A type converter with no logic of its own. It takes a single input (ocs_noise, which accepts both OCS_NOISE and SONAR_CUSTOM_NOISE) and passes it straight through as SONAR_CUSTOM_NOISE. Look at the source and that's literally all it does - the go function returns the input unchanged. Its entire job is to satisfy a node's input type so you can stop getting "input type mismatch" errors.

Why you'd reach for it

Two scenarios. First, you built a workflow around an OCSNoise PerlinAdvanced or OCSNoise ImmiscibleReference generator and want to feed it into a node that only declares a SONAR_CUSTOM_NOISE input - for example a noise slot on a sonar-powered sampler or a noise-aware node from another pack that chose sonar's type as its interface. Second, you're mixing ecosystems: OCS custom nodes "will accept either type currently," per the README, but sonar's own nodes aren't guaranteed to accept OCS_NOISE. Rather than rebuild the noise generator in sonar's nodes, you drop this adapter in between.

The inputs and output

Just the two wires: ocs_noise in, SONAR_CUSTOM_NOISE out. No settings, no YAML, no seed - it's the rare OCS node with zero knobs, which honestly makes it a nice palate cleanser in a pack where everything else has forty parameters. The only thing to remember is that it converts the type label, not the noise itself: an OCS Perlin generator stays a Perlin generator, it just wears sonar's type name afterward.

Installing and gotchas

It ships with the pack - ComfyUI Manager search "Overly Complicated Sampling", or git clone https://github.com/blepping/comfyui_overly_complicated_sampling into ComfyUI/custom_nodes, then restart. No models, no dependencies.

The one real gotcha is using it when you don't need it: inside the OCS pack itself, the adapter is redundant because OCS nodes accept either noise type, so you can wire OCS_NOISE straight in and skip the extra node. You only need this when the target node is outside the pack or otherwise type-strict. If you're not getting a mismatch error, you don't need it - keep the graph clean.

CategoryOveryComplicatedSampling/noise

Inputs (1)

NameTypeDefaultDescription
ocs_noiseOCS_NOISE,SONAR_CUSTOM_NOISEThe following input types are supported: OCS_NOISE, SONAR_CUSTOM_NOISE

Outputs (1)

NameTypeDescription
SONAR_CUSTOM_NOISESONAR_CUSTOM_NOISE