Ino S3 Download Video

Video workflows change the storage game. Clips are big, you don't want them squatting in your local folders, and if you're generating video on rented GPUs, the outputs are definitely going to a bucket. Ino S3 Download Video is the fetch side of that: give it a bucket key and it downloads the clip and returns it as a native ComfyUI VIDEO type - the same type the video models and preview nodes speak - so you can play it, re-encode it, or feed it into the pack's other video tooling.

It's part of ComfyUI Ino Nodes (nobandegani/ComfyUI-InoNodes), the 125+-node V3-schema pack, and one of its 16 S3 helpers. The pack even ships an Ino Preview Video node to view a VIDEO tensor in the graph, so this download node slots into a fully S3-native video pipeline.

How it works

Inputs:

• enabled - the pack-wide toggle.
• s3_key - the object key in the bucket (default placeholder: input/example.mp4).
• s3_config - optional; config string from Ino S3 Config, or leave empty for env-var credentials.

Outputs: success (boolean), message (string), and video (VIDEO).

Mechanically it's a download-then-load: the node pulls the file into a temp directory under temp/s3_download_video with a unique name, then constructs a VIDEO type from it via ComfyUI's video-loading API. Same result as loading a local clip, except the source was a bucket key you passed as a string - which is the whole point. Any node downstream that accepts VIDEO is fair game.

When you'd use it

Cloud-based video generation is where this earns its keep: generate on a GPU instance, upload to S3, then on another box (or the same one later) pull clips by key for preview or post-processing. The temp-file path also means you can process a video without it ever landing in a folder you have to remember to clean. If you're mostly doing image work, you can safely skip this one - it's niche-on-purpose for the video crowd.

Common issues

• Key not found → success: False with a message; check case and path exactly.
• Unsupported format. If the bucket holds a container the video loader doesn't recognize, expect a load failure on that side. MP4 (the default's format) is the safe bet.
• Temp files accumulate. It writes to temp, which ComfyUI clears on restart; for long-running servers you may still want the pack's Ino Remove File in a cleanup branch.

Installing it

ComfyUI Ino Nodes installs like any custom node pack:

• ComfyUI Manager (easiest): search for "ComfyUI Ino Nodes", install, restart.
• Manual:

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

  Then restart ComfyUI.

Requires inopyutils and a current ComfyUI with video support. It's a niche pack with almost no Reddit footprint, so expect to rely on the README - but if your video lives in S3 and you want it back as a VIDEO tensor, this is the one-hop answer.