Video Tile Disk Job

The in-memory tiled workflow has a ceiling: ComfyUI has to keep the processed tiles around until the merge runs, and on a long LTX-2.3 or MiniMax H3 clip that cache is exactly what OOMs you. The disk-backed path in this pack removes that ceiling the old-fashioned way - it stops holding tiles in RAM and writes them to disk one at a time. Video Tile Disk Job is the node that starts that whole process, by turning your slicer's geometry into a job manifest on disk.

Think of it as "save the plan, then process tile by tile." The node takes the tile_config from either slicer, picks a job_name (a folder-safe name), and writes a folder containing a manifest.json that records frame size, tile geometry, tile count, and saved-tile metadata. From then on, every other disk node in the pack works against that manifest.

The inputs that matter

• tile_config - from either Video Tile Slice or Slice Fixed. This is the job's geometry contract.
• job_name - the folder name for this run. Use something meaningful; you'll be pasting this path (or a manifest path) into the merge step later.
• output_folder - where job folders are written. It defaults visibly to ComfyUI's output/video_tiler_tiles folder, which is where you'll find it later.
• audio (optional) - connect the source AUDIO once and it's stored as audio.pt with the job, so a later standalone merge/export can reproduce the clip's audio without the original loader.

What comes out

• tile_job - the manifest handle the other disk nodes consume.
• manifest_path - the actual path, for when you need to paste it somewhere.
• tile_count - how many tiles you'll be processing.
• status - a string you can log or inspect.

The workflow it starts

Slice → Disk Job → for each index: Disk Get Tile (pull one source tile), run it through your expensive upscale branch, Disk Save Tile (write tile_00000.pt, tile_00001.pt, ...) → later, Disk Merge / Disk Folder Merge assembles the saved .pt files and you export the video. The .pt files are exact PyTorch tensors - lossless, not PNGs - which is the point: nothing gets rounded away between passes.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/maDcaDDie2000/comfyui-video-tiler

Restart; disk nodes live under Video Tiler/Disk. No extra dependencies, no model downloads. Apache 2.0, vibe-coded for personal use, not actively maintained. The practical cost of the disk path: disk space (one .pt per tile) and two-pass workflow friction. The payoff is real - it's the lowest-VRAM way to run long clips on a smaller card, which is the whole reason the disk nodes exist.