File Path Processor

File Path Processor is the bridge between your filesystem and the path-hungry nodes in this pack. You give it a path - a single file, a directory, or a wildcard pattern like C:/clips/*.mp4 - and it returns all matching files as one string with newlines between them, each converted to an absolute path.

The reason this node exists is that lazniak's suite is path-driven: SimpleImageLoader, EDLSceneParser, MovingTitles' srt_path and friends all take plain string paths instead of ComfyUI's picker widgets. If you're building workflows where the file set changes, you don't want to retype paths - you want one node that resolves "everything in this folder" for you. That's this.

What it does, precisely

• Single file: give it an existing file path, get back that path as absolute.
• Directory: walk it recursively and return every file under it.
• Wildcard: pass *.png or a deeper pattern and it globs, honoring * and ? (globbing is recursive, so ** works too).

One output, file_paths (STRING), newline-separated. Point it at ComfyUI's output folder and you get a plain-text inventory of everything you've generated - which, combined with the KB's point that ComfyUI embeds the workflow in every PNG, is a decent way to see what's sitting in there at a glance.

What it doesn't do

The README advertises extension filtering, path-component extraction, and symlink resolution. The actual code does none of that - no extension filter, no splitting, no links. So don't come here expecting a Swiss-army path tool. What you get is: file / directory / wildcard → newline-joined absolute paths. That's the honest feature set.

One more honesty note on wiring: you might assume FilePathProcessor feeds VideoMerger, since both live in this pack. It doesn't - VideoMerger expects a directory as its input_path and scans it for video files itself. FilePathProcessor's output is a file list, so use it to inspect, or to drive a loader that consumes individual paths, not to feed the merger.

Install

Standard pack install: ComfyUI Manager search "videoclipgenerator", or

cd ComfyUI/custom_nodes
git clone https://github.com/lazniak/videoclipgenerator
cd videoclipgenerator
pip install -r requirements.txt

Restart and you'll find it under "utils". No dependencies beyond the standard library. Errors (bad path, permission issues) come back as an empty string, so check for a blank output before assuming your glob matched something.