Nodes/ComfyUI Fictiverse Nodes/Video Params Expand
ComfyUI Node

Video Params Expand

The video params packet, split back into the numbers your nodes want

By Fictiverse·Created 3 years ago·Updated 21 days ago· 27
Video Params Expand
  • _
  • width
  • height
  • duration
  • Megapixels

This is the unpack half of the pack's video-params pair. Video Params bundles base resolution, ratio, orientation, frames, and fps into one opaque VParams packet; Video Params Expand takes that packet and hands you back the actual numbers - width, height, frames, fps, and megapixels - as five normal sockets.

Why the round trip? Because it keeps your video workflow tidy. You set the video parameters once, in one node, and a single wire carries all of it across the graph. Then, wherever a consumer node actually needs a plain integer - EmptyLatentVideo's width, the sampler's frame count, a loader's fps - you drop in an Expand and the number appears. Change the aspect ratio upstream and every Expand downstream picks it up automatically. That's the same "define once, split where needed" pattern the pack's Image Params/Image Params Expand pair uses, and it's the pattern most good-size video graphs end up wanting.

How it works

It's a pure unpacker, and that's the whole job. The node checks that it received a proper VParams packet and returns its contents as separate values. No math, no pixels touched, nothing to tune. The interesting work - turning your base and ratio into aligned dimensions - happened upstream in Video Params.

Inputs and outputs

  • _ (VParams) - the packet. Wire it only from the pack's Video Params node.
  • width, height (INT) - resolution, aligned to what your video model expects.
  • frames (INT) - total frame count.
  • fps (FLOAT) - frames per second.
  • Megapixels (FLOAT) - a computed area readout, handy for eyeballing whether you're inside your model's resolution band.

Typical wiring: width, height, and frames into EmptyLatentVideo (or your video model's latent/loader), fps into anything that needs playback speed. Megapixels is mostly a sanity check - "am I asking this model for more pixels than it can handle?"

Installing it

Ships in ComfyUI Fictiverse Nodes, a dependency-free single-author utility pack - nothing beyond ComfyUI's own Python stack, no model files.

  • ComfyUI Manager → search ComfyUI Fictiverse Nodes → Install, restart.
  • Or: cd ComfyUI/custom_nodes && git clone https://github.com/Fictiverse/ComfyUI_Fictiverse, restart.

Common issues

The one thing that bites people is mixing packet formats. VParams is this pack's private socket type, so Expand only accepts a packet from its own Video Params node - feed it something else and the connection won't even attach, which beats silent corruption. Keep the two as a pair and you'll never hit it.

Pack-level gotcha: Fictiverse nodes show up in shared video/animate workflows, and the classic "this node is broken" is actually ModuleNotFoundError: No module named 'custom_nodes.ComfyUI_Fictiverse' from loading a workflow before installing the pack. Install the pack, restart ComfyUI, and reload.

CategoryFictiverse/Params

Inputs (1)

NameTypeDefaultDescription
_VParams

Outputs (4)

NameTypeDescription
widthINT
heightINT
durationFLOAT
MegapixelsFLOAT