ComfyUI Node

Fresco Inputs

One wire for the text encoder, the photo, the VAE and SAM3

By Nynxz·Created 12 months ago·Updated 10 days ago· 4
Fresco Inputs
  • clip
  • image
  • vae
  • inputs
◄sam3none►

Fresco Inputs is a bundle node, and it earns its place by deleting wires. Everything the Fresco editor needs to look at, in one socket: the Krea 2 text encoder, and optionally a photo to trace, segment and edit, that photo's VAE, and a SAM3 checkpoint for turning text or clicks into layer shapes.

The Fresco node's inputs socket accepts either a bare CLIP or this node's output, so nothing breaks if you start simple. Start simple, actually. You only need this the moment you want to segment or edit.

The fields

clip is required - Krea 2's text encoder. Krea 2 runs on Qwen3-VL, and that's not incidental: the encoder is what reads reference images inside a layer's prompt, and the "look" mode encodes through the vision tower with your images in view. Plain CLIPLoader with a krea2-type encoder is all it takes.

sam3 is required too, but its default is none, so you can leave it alone until you need it. It's a dropdown, not a loader - and that's deliberate. Fresco loads the checkpoint only when a layer has something new to segment, then keeps it around for the next one. Load it up front with a SAM3 loader node and you've spent the VRAM whether or not you draw a single segmented layer.

image (optional) is the photo you're working on. It gets shown under the canvas after a run so you can trace over it, it's what SAM3 segments against when a layer asks, and it's what Fresco Apply edits if edit_image is on. vae (optional) rides along to Fresco Apply, which needs it to encode that photo - or to encode the layout start image if you raise layout_start.

One output: inputs, into Fresco. That's the whole node.

Why it's a separate node at all

Because Fresco Apply picks the photo and VAE up from the fresco wire the editor already carries. Without this node you'd wire the same photo twice, once into the editor (to draw and segment over) and once into Apply (to edit), and they could drift apart if you swapped one and forgot the other.

Install

Search Nynxz in ComfyUI Manager, or:

comfy node install comfyui-nynxz-nodes

From source, remember the frontend:

cd ComfyUI/custom_nodes
git clone https://github.com/Nynxz/ComfyUI-NynxzNodes
cd ComfyUI-NynxzNodes
pnpm install && pnpm build

Then restart. No Python packages to add - and that includes SAM3: this node expects the SAM3 support ComfyUI already ships, so pick a checkpoint in the dropdown rather than installing a second sampler of segmentation.

Common issues

"The dropdown is empty." No SAM3 checkpoint in your models folder - get one placed where core's SAM3 nodes find it, and if core's own SAM3 Detect works, this will too.

"Segmentation does nothing." You picked a checkpoint but the photo didn't arrive, or the layer has nothing to segment yet. A layer segments when its box, its click points, its capture text or the image changes; once segmented, your hand-painted touch-ups survive re-runs, which is the behaviour you want.

"Edit mode ignores my photo." Check the photo reached Fresco Apply - it comes down the fresco wire, so the Fresco node in between has to be the one holding this bundle. And edit_image has to be on, which it is by default.

CategoryNynxz/Regions/Fresco

Inputs (4)

NameTypeDefaultDescription
clipCLIPThe text encoder — Krea 2's.
sam3COMBOnoneThe SAM3 checkpoint, for layers that capture something by text or click points. Loaded only when a layer has something new to segment.
imageoptIMAGEA photo to work on: shown under the canvas after a run, segmented by SAM3 for layers that ask, and edited by Fresco Apply.
vaeoptVAECarried to Fresco Apply, to encode the photo or the layout start.

Outputs (1)

NameTypeDescription
inputsNYNXZ_FRESCO_INPUTSInto Fresco.