🔶 Convert Video2Img -> Frame

This is the on-ramp for the whole idea behind Chaosaiart-Nodes. The pack's pitch is "LowVRAM Animation" built on frame-by-frame generation - one image at a time, batch count rather than batch size, each frame cached and handed forward into the next - rather than the full-motion-batch approach a pack like AnimateDiff uses. If you're starting from an existing video instead of a blank canvas, this node is where that video becomes a folder of individual stills the rest of the pipeline can chew through one at a time.

How it works

Point it at a video file and it reads through frame by frame, writing stills out, with FPS_Mode controlling how many of those frames you actually keep. This is almost certainly why the README's Linux install step calls out pip install opencv-python explicitly - video decoding needs OpenCV, and it isn't part of ComfyUI's base dependencies, so the pack has to ask for it separately.

The FPS throttle matters more than it looks. Every frame this node keeps becomes a full separate sampling pass later in the pipeline - there's no batching a whole video through one generation here. Dropping a 30fps source down a tier or two is the difference between a workflow that finishes and one that's still running an hour later.

Inputs and outputs

• Video_Path (required, STRING) - a plain text file path to the source video, not a browser upload widget.
• FPS_Mode (required, enum) - Normal, Low FPS, Lower FPS, Ultra Low FPS. Each step down drops more of the source frames.

Output: Info (STRING) - a status readout (frame count, roughly), which is only useful once you wire it into chaosaiart_Show_Info - the node doesn't display anything on its own.

Installing it

ComfyUI Manager: Install via Git URL, https://github.com/chaosaiart/Chaosaiart-Nodes. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/chaosaiart/Chaosaiart-Nodes, restart. On Linux, run pip install opencv-python and pip install tqdm as well (activate any venv first) - this node specifically is the reason those are listed. No model downloads needed; it's pure video I/O.

Where people get burned

• Video_Path is a raw filesystem path, not a file picker. On a local ComfyUI install that's fine - point it at wherever the video lives on your own disk. Running on comfy.icu, your workflow executes on a remote container, so a path pointing at your own machine (C:\Users\you\clip.mp4, ~/Desktop/clip.mp4) won't resolve there. The file needs to already be reachable on the executor's filesystem - worth checking before you assume the node is broken when it's actually just looking in the wrong place.
• The exact frame-drop ratio for each FPS_Mode isn't documented anywhere. The README names the four options but doesn't say what each one actually targets in FPS terms - test on a short clip before committing a long one to a setting you're guessing at.
• This is a small, mostly-quiet project. The author's original announcement got a modest response on r/comfyui in early 2024 and real discussion of the pack tapered off soon after - there's no active community thread to search if this node's output looks off, just the source and your own testing.