Nodes/was-node-suite-comfyui/Video Dump Frames
ComfyUI Node Runs on cloud

Video Dump Frames

Pull a video apart into individual frames

By WASasquatch·Created 3 years ago·Updated 2 days ago· 1,839
Video Dump Frames
    • folder_written
    • processed_count
    • processed_count_float
    • processed_count_int
    video
    root
    folderframes
    prefixframe_
    filenumber_digits4
    extension

    Straight talk on this one: it's not called out by name in the WAS Node Suite README's own node list, unlike most of the pack's nodes, so what follows leans more on what the node's name and its neighbors tell you than on the author's own description. Going by the naming convention the rest of the suite's video tools use - Write to Video, Create Video from Path, Create Morph Image from Path - Video Dump Frames does the inverse of assembling a video: it takes a video file in and writes its individual frames back out, presumably as an image sequence or batch you can then process frame-by-frame with the rest of ComfyUI's image tooling.

    Why that matters for how you'd use it

    If you want to run any per-frame processing on an existing video clip - restyling, upscaling, running it through a filter chain - you generally need it as a batch of individual images first, since ComfyUI's image nodes work frame-by-frame, not on video containers directly. A frame-dumping node is the standard first step in that kind of pipeline: pull the clip apart into frames, do your image-space work, then reassemble with something like the suite's Create Video from Path or Write to Video once you're done.

    The constraint that actually is documented

    What the README is explicit about, in its Video Nodes section covering this whole family of tools: they require FFMPEG installed and configured (with the ffmpeg path set in was_suite_config.json), and the author states plainly that official support is Windows-only - "I do not have access to Mac or a stand-alone linux distro." Linux and Mac users report mixed results; it may well work if your ffmpeg install is sane, but you're off the documented, tested path if you're not on Windows.

    Installing it

    Through ComfyUI Manager: search "WAS Node Suite", install, restart. Manually:

    cd ComfyUI/custom_nodes
    git clone https://github.com/WASasquatch/was-node-suite-comfyui
    cd was-node-suite-comfyui
    pip install -r requirements.txt
    

    On top of the suite's own requirements, make sure FFMPEG itself is installed and its path is set correctly in was_suite_config.json (generated the first time you run ComfyUI with the suite installed) - the video nodes won't function without it.

    Troubleshooting

    If nothing happens, or you get an unclear failure, check the FFMPEG path first - that's the single most common point of failure across every video node in this suite, not specific to this one. If you're on Linux or Mac, be extra suspicious of anything video-related failing silently; that's exactly the unsupported territory the author flags.

    And as with the rest of the pack: WAS Node Suite hasn't had active development since December 2023, so a broken import after a ComfyUI update is far more likely to be a pinned dependency conflict suite-wide than anything specific to this node.

    CategoryWAS Suite/Animation

    Inputs (6)

    NameTypeDefaultDescription
    videoCOMBOWhich video to read. The menu lists every container in ComfyUI's input, output and temp folders and in any folder added under paths.allow_read: .mp4, .mkv, .webm, .mov and the rest ffmpeg opens.
    rootCOMBOWhich folder the files land in: ComfyUI's own 'output' or 'temp', or any folder added under paths.allow_write in config.yaml, listed by its own name. The name below it says the rest.
    folderSTRINGframesFolder below the root that the stills are written into, created if it is not there. Tokens expand, so '[time(%Y-%m-%d)]/frames' files each day's under a dated folder.
    prefixSTRINGframe_Text before the frame number, so 'frame_' gives 'frame_0000.png'. Tokens are expanded here too. Leave it empty to name the files by number alone.
    filenumber_digitsINT4-1–8How many digits the frame number is padded to: 4 gives 'frame_0001', which keeps the files in order when they are listed. 0 or -1 writes the bare number, so 'frame_10' sorts before 'frame_2'.
    extensionCOMBOImage format for each frame. `png` is lossless and the safest choice; `jpg` is much smaller but loses detail; `tiff` is lossless and large; `gif` drops each frame to 256 colours.

    Outputs (4)

    NameTypeDescription
    folder_writtenSTRINGFull path of the folder the frames were written to, for feeding an image batch loader.
    processed_countNUMBERHow many frames were written, for the NUMBER inputs of the suite's own maths nodes.
    processed_count_floatFLOATThe same count as a decimal, for example 250.0.
    processed_count_intINTThe same count as a whole number, for a core INT input.