Nodes/ComfyUI-YogurtNodes/Load Video Path (Yogurt Nodes)
ComfyUI Node

Load Video Path (Yogurt Nodes)

Get a video into your graph without a file browser, with a time range

By yogurt7771·Created 2 years ago·Updated 9 days ago· 1
Load Video Path (Yogurt Nodes)
  • start_time
  • end_time
  • VIDEO
video_path

Sometimes the thing you want to feed into your workflow isn't in ComfyUI's input folder - it's sitting in a scratch directory, or it's a file you downloaded mid-project, or it's a clip so long you only want a slice of it. Load Video Path (Yogurt Nodes) is the "just give me the file path" version of video loading, and it adds a time range on top so you can grab seconds 4 through 9 of a two-minute file instead of loading the whole thing.

The headline use case is video-to-video and frame-extraction pipelines: you hand it a path, it hands you a VIDEO tensor, and everything downstream - frame splitting, img2img on frames, feeding a video model - just works. If you're doing any of the LTX or Wan video work that's been dominating ComfyUI recently, this is a clean way to get a source clip in without moving files around.

How it works

The node is a thin wrapper around ComfyUI's own VideoFromFile helper. It builds a VIDEO output from the file at video_path, using start_time and end_time (in seconds) to compute how much of the clip to read. end_time of 0 means "no end limit", so the clip runs to the end of the file. It's careful about validating: if the file doesn't exist or the time range is invalid, you get a clear error at connection time rather than a crash mid-run. And it checks the file's modification time, so if you re-render the source video on disk, ComfyUI knows the workflow should re-run - no stale cached frames.

The inputs that matter

  • video_path - the path to the video file, as a string. Absolute paths are the safe choice (relative ones resolve from wherever ComfyUI was started).
  • start_time - seconds to start reading from; 0 means the beginning.
  • end_time - seconds to stop at; 0 means no limit. It must be greater than start_time if set.

One output: VIDEO - the loaded clip, ready for any node that accepts the VIDEO type.

Installing it

Load Video Path ships in ComfyUI-YogurtNodes, yogurt7771's ~150-node grab-bag. Install via ComfyUI Manager (search "ComfyUI-YogurtNodes") or:

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

Restart ComfyUI; everything appears under "Yogurt Nodes". No model files involved, and the requirements are just the usual numpy/pillow/requests plus the pack's API client libs.

Where people get burned

The main trap is expecting this to work in every ComfyUI build. The node relies on the VIDEO type and the newer video input plumbing, so if you're on an old core you may see the type refused or the node erroring on import - update ComfyUI first, it's a solved problem in current versions. Second, mind the time range: end_time of 0 is "to the end", but if you set both times, end_time must be strictly greater than start_time or you get a validation error. And as with any path node in this pack, if the file isn't where you think it is, check whether a relative path is resolving against the working directory rather than your input folder.

CategoryYogurtNodes/IO

Inputs (3)

NameTypeDefaultDescription
video_pathSTRINGPath to the video file
start_timeFLOAT,INT0Start time in seconds. 0 means from the beginning.
end_timeFLOAT,INT0End time in seconds. 0 means no end limit.

Outputs (1)

NameTypeDescription
VIDEOVIDEO