Nodes/ComfyUI-QwenVL-Utils/Load Video Advanced (Path)
ComfyUI Node

Load Video Advanced (Path)

Point at any video without copying it into input/

By AkihaTatsu·Created 7 months ago·Updated 6 months ago· 0
Load Video Advanced (Path)
    • video
    • path
    file

    The path-based half of the pack's video-loading pair. Load Video Advanced (Path) - class QwenVLUtils_VideoLoaderPath - is identical to Load Video Advanced except for one thing: instead of picking a file from ComfyUI's input folder, you type (or paste) a path to a video anywhere on your disk. No copying clips into ComfyUI/input, no managing the file through the UI.

    Inputs and outputs

    One input: file - a plain string field, with the placeholder X://insert/path/here.mp4 to show you the shape it expects. Two outputs:

    • video - the video itself.
    • path - the absolute file path string.

    The mechanism is the same as its sibling: the source takes the path, resolves it through ComfyUI's annotated filepath handling, and builds the video via InputImpl.VideoFromFile(path). It also checks the file's modification time for IS_CHANGED, so the node re-runs when the file on disk changes.

    Load Video Advanced vs. Load Video Advanced (Path)

    Two loaders, one difference:

    • Load Video Advanced reads from ComfyUI/input - use it for anything you've dropped into the UI.
    • Load Video Advanced (Path) reads from an arbitrary path - use it for videos living anywhere else: a render scratch folder, a dataset directory, another drive.

    Same two outputs, same native VIDEO type. The trade is convenience vs. reach: the input-folder version gives you a dropdown and upload, the Path version gives you every file on your machine.

    The wiring caveat, same as its twin

    Don't expect to plug this node's video output straight into a QwenVL node. The QwenVL nodes' video input is an IMAGE type - a batch of frames it uniformly samples - while this loader emits ComfyUI's native VIDEO object. To feed QwenVL video analysis you'd go through a frame-conversion step first, or route the path output where a path is consumed. And in the current release the QwenVL nodes' source_path input isn't wired into generation yet, so the path output is best used by other PATH-consuming nodes for now.

    Install

    Part of the QwenVL-Utils pack, installed the same way:

    cd ComfyUI/custom_nodes
    git clone https://github.com/AkihaTatsu/ComfyUI-QwenVL-Utils.git
    cd ComfyUI-QwenVL-Utils
    pip install -r requirements.txt
    

    Or ComfyUI Manager → search "QwenVL Utils" → install → restart.

    Troubleshooting

    The "Invalid video file" error here almost always means a path typo, and Windows users get bitten by backslashes - the placeholder's X:// style hints at it: use forward slashes (C:/videos/clip.mp4) or escape the backslashes, because a raw C:\videos\clip.mp4 in the string field will not resolve the way you hope. If the path is right and it still fails, the file genuinely isn't a format ComfyUI can open, so check it plays in a normal player first.

    CategoryQwenVL-Utils/Input

    Inputs (1)

    NameTypeDefaultDescription
    fileSTRING

    Outputs (2)

    NameTypeDescription
    videoVIDEO
    pathPATH