Nodes/Comfyui-PixNodes/Create Video List (PixNodes)
ComfyUI Node

Create Video List (PixNodes)

A video manager with native ComfyUI VIDEO output

By pixixai·Created 8 months ago·Updated 6 months ago· 24
Create Video List (PixNodes)
    • video_list
    • video_paths_list

    Video workflows have a version of the image problem: ComfyUI's Load Video handles one clip, and when you need to process a pile of clips in one pass you're back to stitching together individual nodes. Pix_CreateVideoList is the batch manager for video - an in-node UI where you upload, preview, hover-to-play, and drag-to-reorder clips, and the node hands you a native VIDEO-typed list that ComfyUI's batch machinery will iterate over.

    No visible inputs - the state is held in a hidden video_data field the frontend maintains, and you interact with the grid/list UI instead. Two outputs: video_list, a VIDEO-typed list (one VIDEO object per clip), and video_paths_list, a JSON array of absolute file paths. The pair is designed for two different consumers: video_list plugs into official nodes that speak the new VIDEO type (like Get Video Components or Save Video) and gets auto-batched by ComfyUI; video_paths_list gives you the plain paths when a node just needs filesystem locations. Notably, video_paths_list is not split by the batch loop - every iteration sees the full list, so it's for "give me all the paths at once" logic, not per-clip processing.

    This is where a compatibility caveat lives, and it's the most important thing on this page. The node tries to import comfy_api.latest and build real VIDEO objects with InputImpl.VideoFromFile; if that import fails, it prints a warning and falls back to handing you the path list on the video_list port too. The author's docs are explicit that native VIDEO output requires a current ComfyUI (0.3+ era). If your video nodes downstream keep rejecting the input, this fallback is almost certainly what happened - update ComfyUI, and the VIDEO objects come back.

    A few behaviors worth knowing from the changelog and source: it validates that files actually exist and logs warnings for missing ones, and 1.0.8 added auto-detection/cleanup of deleted videos and an auto column width for the preview grid. So a stale entry from an old session won't silently poison the batch - it gets pruned with a console warning.

    Install is the standard PixNodes path - ComfyUI Manager, search PixNodes, restart - or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/pixixai/Comfyui-PixNodes
    cd Comfyui-PixNodes
    pip install -r requirements.txt
    

    then restart. The requirements file is just openai and Requests - there is no ffmpeg/pyav dependency in this pack's actual install, so don't let a tutorial convince you to install one. (The docs' official Get Video Components-style chains do their own decode.)

    Honest take: this node only earns its keep if you're repeatedly processing the same curated set of clips - reorder, re-run, reorder again. For a one-shot "process this one file," the core loader is simpler. For batch video work, the VIDEO list output is genuinely the current-standard way to do it.

    CategoryPixNodes/video

    Inputs (0)

    No inputs

    Outputs (2)

    NameTypeDescription
    video_listVIDEO
    video_paths_listJSON