Pipe In Generation Data II

Pipe In Generation Data II is the current, non-deprecated version of the pack's "generation recipe" pipe: it collects everything you'd want to remember about a run - sampler_name, scheduler, steps, cfg, seed_value, width, height, positive, negative, modelname, vae_name, loras, plus denoise and clip_skip - and packs it into one pipe. Feed that into the pipe_opt input of Save Images [RvTools] and every saved PNG carries its full generation data in the metadata. That's the author's "Save Image with Generation Data" workflow in action: the image stays reproducible without you keeping the .json next to it.

It's the "II" because there's a v1 of this exact idea (see Pipe In Generation Data, now deprecated). The II version bumps the layout: it adds denoise and clip_skip, and it reorders the tuple - in V2 the sampler and scheduler ride right after the version tag instead of deeper in. Internally the node stamps the pipe with a hard-coded "V2" version tag, and Save Images [RvTools] checks that tag to decide which layout it's unpacking. That's why the two generations can coexist: old V1 pipes still decode, new V2 pipes add fields, and the save node handles both by looking at the tag rather than guessing.

Like all RvTools pipe nodes, this is a merge, not a store: the optional incoming pipe provides previous values, and any slot you connect overwrites that position. The inputs are all forceInput, so plan to wire these from primitives, selector nodes and your prompt text rather than editing them inline - there are no meaningful defaults.

Install. ComfyUI Manager → search "RvTools" → install ComfyUI-RvTools_v2 and restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2
# restart ComfyUI afterwards

No models or keys. Manual installs need pip install -r requirements.txt (opencv-python, pynvml, piexif, Pillow, pilgram) - piexif is what writes the EXIF data.

The catches. The one to keep front of mind is layout: the V2 pipe must be decoded by a V2-aware consumer. If you wire a V2 pipe into something that only understands the V1 layout, it'll unpack into the wrong slots or throw - save-image nodes from other packs will almost certainly not know your V2 ordering. And the pack caveat: RvTools v2 is unmaintained and the README points you to ComfyUI_Eclipse as the successor. None of that stops this node from working today - it's the current, recommended member of its family - but it's legacy software, and if the workflow's being shared around, make sure whoever receives it also installs the pack so the [RvTools] node names resolve.