Nodes/ComfyUI Video Tiler/Video Tile Disk Get Tile
ComfyUI Node

Video Tile Disk Get Tile

Pull one tile out of the source for the expensive branch — the disk workflow's first half

By maDcaDDie2000·Created 6 months ago·Updated about a month ago· 19
Video Tile Disk Get Tile
  • images
  • tile_job
  • tile
  • tile_index
  • tile_job
tile_index0

The disk-backed workflow is built on a rhythm: fetch one source tile, process it, save it, move on. Video Tile Disk Get Tile is the "fetch" half - it reads the job manifest and extracts exactly one tile from the original images batch by index. What comes out is a single [B,H,W,C] tile ready to feed the expensive part of your pipeline (your upscale branch), with the manifest handle passed through so the next disk node in line has everything it needs.

The inputs

  • images - the original full IMAGE batch [B,H,W,C] (the frames your slicer saw; the node crops from this, not from disk).
  • tile_job - the manifest from Disk Job (or Disk Open Job).
  • tile_index - which tile to extract.

The outputs

  • tile - the single tile crop, ready for your upscale branch.
  • tile_index - the index you asked for (resolved), so downstream bookkeeping can trust it.
  • tile_job - passthrough, so you can chain straight into Disk Save Tile without re-wiring the manifest.

How it fits the pass-1 loop

The standard loop per tile: Disk Get Tile → upscale branch → Disk Save Tile. Set the index (from Disk Indexes if you're automating, or by hand for a one-off), and each queued run processes exactly one tile. That's the whole VRAM trick - the expensive branch sees one tile at a time, and nothing holds the processed results in graph memory. The original images still need to be in the workflow at this stage (this is pass 1, after all), which is why the README's separate pass 2 uses the folder-based merge nodes instead.

Install

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

Restart; it's under Video Tiler/Disk. No extra dependencies, no model downloads. Apache 2.0, vibe-coded for personal use, not actively maintained. The one real footgun is mismatched state: if the job manifest doesn't match the images you feed (say, you re-sliced with different settings but pointed the job at a stale manifest), the crops will be wrong. Keep the slicer's tile_config, the job it created, and the original images as one unit - that's the contract this node assumes.

CategoryVideo Tiler/Disk

Inputs (3)

NameTypeDefaultDescription
imagesIMAGEOriginal full IMAGE batch [B,H,W,C].
tile_jobTILE_JOB
tile_indexINT00–999999

Outputs (3)

NameTypeDescription
tileIMAGE
tile_indexINT
tile_jobTILE_JOB