CreativeCode Settings

CreativeCode Settings is the least glamorous node in the ComfyUI_CreativeCode pack, and the one you'll quietly thank once you have three Code2Vid render nodes in a graph. It's a configuration bundle: resolution, frame count, fps, shader code - everything the render node needs, packed into one CC_SETTINGS object you wire into as many CreativeCodeRender nodes as you like.

That's it. That's the whole job. It's pure plumbing of the "one source, many consumers" variety the KB's node-plumbing essay calls out: define the settings once, fan them out, never retype the same 640×360 @ 24fps into three nodes again. If you only ever have a single render node, you can ignore this one entirely and just set the widgets on the render node itself.

The extra trick: it's also the shader library picker

The select_shader dropdown is the interesting bit. It lists every .glsl/.js file in the pack's saved_shaders folder - 42 presets at last count, from aurora_waves.glsl and cyber_glitch.glsl to fractal Julia sets. Pick one and it loads that code into shader_code, overwriting whatever was there. So the node doubles as a preset browser for the pack's curated library, which is genuinely handy when you're poking around trying to learn what these shaders can do.

That also means the node's full set of fields mirrors the render node's: shader_code, width, height, frames, fps, time_start, plus optional version_mode (auto/es300/glsl330) and code_type (glsl/p5). When you connect settings into a render node, those values override the render node's own widgets - the render node only keeps its local values when no settings wire is attached.

The gotcha that trips people up

Because the bundle carries shader_code too, wiring a Settings node in doesn't just share resolution - it also takes over the code. If you edit the shader on the render node and wonder why the output didn't change, this is why: the Settings node is now the source of truth. The rule is simple once you know it: when a Settings node is connected, configure the code there, not on the render node. If you only wanted to share width and fps, you're still stuck copying the code over - a minor annoyance, but worth knowing before you spend an hour "debugging" a shader that was never running.

The pack() method is about as simple as a node gets - it returns the kwargs as a dict, and the render node unpacks whatever fields it recognizes. That thinness is a feature: there's very little that can break here. The main realistic failure is the same as the rest of the pack - if the render node isn't installed or is missing ModernGL, the bundle just sits there inert.

Install

Shared with the whole pack:

cd ComfyUI/custom_nodes
git clone https://github.com/SKBv0/ComfyUI_CreativeCode.git
pip install -r ComfyUI_CreativeCode/requirements.txt

Restart ComfyUI. No models, no extra services, and select_shader will only show presets after the pack's files are on disk - which they are, by construction.

It's a small node with a small job, and that's fine. Use it when you're running several render nodes at matching settings; skip it when you're not. The preset dropdown alone might be worth keeping one around.