Video Tile Disk Indexes

The disk-backed workflow's one chore is bookkeeping: you have N tiles, you process them one at a time, and you need to tell the pipeline which tile you're on. Type the numbers by hand and you will slip up on tile 17 of 24, save the wrong file over the right one, and learn why automation exists. Video Tile Disk Indexes is the pack's answer - a node that just emits the list of tile indices for a job, so your graph (or your queue automation) never has to guess.

The inputs

• tile_job - the manifest from Disk Job (or from Disk Open Job).
• start_index - first tile index (default 0).
• end_index - last tile index; -1 means "the final tile", which is the convenient default: you don't need to know the tile count to request all of them.

The outputs

• tile_indices - an INT list. Feed this into a per-tile execution context or use it to drive your queue: one queued run per index, each run telling the graph which tile to fetch.
• tile_count - the job's total, handy when you're computing something like "how many runs is this going to be."

How it fits

The README's framing: use it for queue automation or list execution where your graph supports it. In practice that's the pattern of - read the job, fan the index list into your per-tile branch (Disk Get Tile + your upscale branch + Disk Save Tile), and let each run advance one index. It keeps the "manual path" (typing tile_index yourself and queuing per tile) as an option for when you specifically want to inspect or redo a single tile, but the whole point of this node is that you don't have to.

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 - pure bookkeeping on top of the manifest. Apache 2.0, vibe-coded for personal use, not actively maintained.

One thing to keep in mind: tile_indices reflects the job manifest, and the disk nodes number saved files to match - tile_00000.pt, tile_00001.pt, and so on, in the slicer's original tile order. So the index you emit here is the same index Disk Save Tile writes and Disk Merge expects. As long as every run uses this node's output, your numbering can't drift out of sync - which is precisely the failure this node exists to prevent.