Nodes/ComfyUI-RvTools_v2/Pipe Out Project Folder Video
ComfyUI Node

Pipe Out Project Folder Video

Unpack a video project folder without the spaghetti

By r-vage·Created about a year ago·Updated 5 months ago· 23
Pipe Out Project Folder Video
  • pipe
  • pipe
  • width
  • height
  • batch_size
  • frame_rate
  • frame_load_cap
  • skip_first_frames
  • select_every_nth
  • path

Video workflows in ComfyUI are wiring nightmares. Resolution, batch size, frame rate, load cap, skip counts - a half-dozen numbers have to reach the same cluster of nodes, and if you hand-route each one, the graph reads like a plate of cold spaghetti. This node is the cleanup crew: it takes one pipe from "Project Folder Video (Pipe) [RvTools]" and unpacks the video settings that node bundled.

Think of the pair as a power strip. "Project Folder Video (Pipe)" computes a dated output folder and snaps width, height, batch size, frame rate, frame load cap, skip-first-frames and select-every-nth together into a single pipe. "Pipe Out Project Folder Video" is the socket on the other end - feed it the pipe, get the values back as individual outputs. The source is a straight tuple unpack plus a pipe passthrough; there's no filesystem work happening here, just relay.

The outputs, in order, are:

  • width, height (INT) - the resolution the project folder node chose.
  • batch_size (INT) - frames per batch.
  • frame_rate (FLOAT) - the project's fps.
  • frame_load_cap (INT) - how many frames to pull in.
  • skip_first_frames (INT) - frames to drop off the front.
  • select_every_nth (INT) - frame sampling stride.
  • path (STRING) - the actual output folder, last output, easy to miss.

The path slot being last is the classic footgun. If you wire outputs by visual position instead of by name, you'll happily feed a frame count into a string input and get a type error. ComfyUI shows the names on the sockets - use them.

Why bother? Because the same pipe can branch. Route the pipe output onward to other RvTools Pipe nodes or through group boundaries while you also unpack it here for the nodes that need individual numbers - the empty latent node wants width/height, the video loader wants the frame settings, the save node wants the path. One bundle in, many consumers, no crossing wires.

Installing it

Ships in ComfyUI-RvTools_v2. In ComfyUI Manager search "ComfyUI-RvTools_v2", or:

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

Restart ComfyUI. Requirements (torch, numpy, Pillow, opencv-python, pilgram, pynvml, piexif) install through Manager; nothing to download, no keys.

Where people get burned

  • Tuple shape mismatch. This node expects the exact eight-value pipe from "Project Folder Video (Pipe)". Feed it a sampler-settings pipe and execution dies with ValueError: not enough values to unpack. Match partners, not just types.
  • The pack is deprecated. ComfyUI-RvTools_v2 is unmaintained and the README directs everyone to the successor pack, ComfyUI_Eclipse. These nodes still work, but plan migration for new builds.
  • Path is relative by default. "Project Folder Video (Pipe)" returns ./... paths unless relative_path is off, so the path you unpack here is relative to the output dir, not absolute. That's usually what the save nodes expect, but it surprises people the first time.
Category🫦 RvTools II/ Folder

Inputs (1)

NameTypeDefaultDescription
pipepipe

Outputs (9)

NameTypeDescription
pipepipe
widthINT
heightINT
batch_sizeINT
frame_rateFLOAT
frame_load_capINT
skip_first_framesINT
select_every_nthINT
pathSTRING