Pipe In Generation Data

Pipe In Generation Data is how the RvTools pack collects "what did I generate with" into one pipe that its Save Images [RvTools] node can stamp into the PNG. Feed it steps, cfg, sampler_name, scheduler, positive, negative, modelname, width, height, seed_value, loras, vae_name - and it packs them all into a single pipe output. Wire that pipe into the pipe_opt input of the pack's save node, and the saved image carries the whole recipe in its metadata, so the generation is reproducible and the workflow survives without the workflow file itself.

That metadata story is the whole reason this family exists. ComfyUI's culture runs on "workflow included" - images that embed their own pipeline - and this is the pack author's take on doing it for the specific sampler/settings/size/LoRA data that usually gets lost. The author's own README section for "Save Image with Generation Data" is the framing: you keep the generation data with the image.

The mechanism is the standard RvTools bus merge, with one detail that makes this pipe special: it carries a version tag. The pipe_version is hard-coded to "V1" on this node, and Save Images [RvTools] reads that tag to know which tuple layout it's looking at. That versioning is exactly why the pack kept a V1 and a V2 of this node around instead of just editing one in place - old saved workflows and old pipes keep working.

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, no keys. Manual clones: pip install -r requirements.txt (opencv-python, pynvml, piexif, Pillow, pilgram) - the piexif dependency is what actually writes the EXIF metadata.

The catches. First: this V1 node is deprecated. Use Pipe In Generation Data II for anything new - it adds denoise and clip_skip, and it reorders the tuple, so V1 and V2 pipes are not interchangeable. Save Images [RvTools] can read both because of the version tag, but only if you feed it a pipe from the matching node. Second, everything here is forceInput, meaning you're expected to wire values in from selectors and primitives rather than typing into widgets - the node deliberately has no defaults to drift. And the pack-level caveat still applies: RvTools v2 is superseded by ComfyUI_Eclipse per the README, and workflows referencing the old deleted v1 repo's nodes won't install. If you just want your saved PNGs to carry full generation metadata, this family is the most direct route - just reach for the II version.