OVERTLI Addtl Load Video

This is the video half of the same idea as OvertliAddtlLoadImage: ComfyUI's native Load Video with its file list scoped to ComfyUI/input/OvertliDS/addtl. If you're wiring a reference clip into a video workflow and your dropdown is empty, you're not broken - you're pointing it at a folder where nothing lives yet.

What it's for

Since the native VIDEO type landed in ComfyUI, handing a file to a graph became a normal move instead of a VHS-era workaround. Reference-driven video generation is the reason: 2026 video models take first and last frames, character sheets, reference clips and audio as named inputs, and the pack's own MiniMax H3 guide is built around that. H3 works with reference tags numbered independently per type - <Picture 1>, <Video 1>, <Audio 1> - so a clip you load has to be identifiable as the clip.

That's where a scoped loader earns its place. The suite keeps a separate pile of Addtl reference media, and the Director's H3 review tools scrub and extract frames from exactly that pile without it bleeding into your normal reference set. If you're building the other half of that - a bare graph where you just want one reference clip - you can use this node as a plain scoped picker.

How it works

The node subclasses comfy_extras.nodes_video.LoadVideo and replaces its schema's inputs with a single file combo built by walking input/OvertliDS/addtl recursively and keeping .mp4 .mov .webm .mkv .avi .m4v. Note that this is the pack's own extension whitelist, not ComfyUI's MIME sniffing - core's Load Video filters top-level input/ entries by content type instead. Validation is the same island check as its image sibling, with the same blunt message: "Choose an existing reference inside input/OvertliDS/addtl."

One input, one output. The required file combo (with an upload control) in, a single VIDEO out. Wire it into whatever consumes VIDEO: the pack's H3 reference islands, a video-to-video model, or a Get Video Components node if you want frames and audio separated. Loading is lazy - execute returns a file reference, and the decode happens downstream in whatever consumes it, using ComfyUI's bundled PyAV. That's worth knowing for troubleshooting, because it means a bad file usually blows up two nodes later, not here.

Also inherited from core: the node fingerprints on the file's modification time instead of hashing it, so swapping a clip for a new one under the same filename is picked up without you touching the graph.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/OvertliDS/overtli-studio-suite
cd overtli-studio-suite
pip install -r requirements.txt

Restart ComfyUI, or search Overtli in ComfyUI Manager and let it do the same thing. No model downloads, and the pack's requirements are only requests, Pillow and numpy - video decoding comes from ComfyUI itself.

One thing the requirements file won't tell you: this node only registers if your ComfyUI is new enough to have comfy_api.latest and the native video nodes. The suite imports that plumbing at load time. If the node is missing after install - or the whole pack fails to appear - update ComfyUI before you start reinstalling things.

Then put a clip where the node can see it:

mkdir -p ComfyUI/input/OvertliDS/addtl
cp ~/clips/ref_shot.mp4 ComfyUI/input/OvertliDS/addtl/

Uploads made through the suite's own Director panels land in that folder automatically (they post with subfolder=OvertliDS/addtl); by hand is fine too, and nested subfolders work.

Where people get burned

• Empty dropdown. The folder doesn't exist, the clip is in input/ at the top level (core Load Video shows that one), or the extension isn't on the whitelist - .mpg, .flv and .wmv won't appear.
• "Choose an existing reference inside input/OvertliDS/addtl." The graph remembers a path. Rename or move the clip and the node refuses rather than guessing. Reselect the file.
• A decode error downstream. If Get Video Components or the video model complains about the stream, that's the file's codec, not the path. The loader never inspected it - the pack's whitelist is suffix-based.
• It's a reference loader, not a trimmer. No frame counting, no fps, no duration controls, and it doesn't write anything. Long 4K reference clips load instantly and then cost you on the decode, so keep references short if VRAM is tight.
• Licence, not plumbing. If you're pointing this at an H3 local workflow from the US, EU, UK or South Korea, the thing that will stop you isn't this node - MiniMax's community licence excludes those territories for the local weights.