Add temporal chunking to latent upscale

2026-09-04 06:41:03 +00:00
parent fbb5f799cd
commit a0d80bcc47
4 changed files with 107 additions and 8 deletions
@@ -1165,7 +1165,7 @@ What this really means:
 - the node then runs a short refinement pass over the upscaled latent with the sampler, scheduler, step count, denoise, and megapixel target you picked on the latent-upscale params node
 - if the target is larger than the spatial tile size, that refinement pass is processed in spatial batches using the same tile defaults as the upstream latent-split node
 - the spatial stitch mode follows the upstream overlap controls, including `linear`, `smoothstep`, `overwrite`, and `midpoint`
- the node also carries the upstream split compatibility knobs (`chunk_length`, `resize_conditioning`, and `anchor_strength`) so the control surface stays in one place
+- the node also carries the upstream split compatibility knobs (`chunk_length`, `temporal_overlap`, `resize_conditioning`, and `anchor_strength`) so the control surface stays in one place

 Good starting point:

@@ -1173,6 +1173,7 @@ Good starting point:
 - use the interpolation mode when you want a cheaper resize-only path
 - start with `euler_ancestral`, `simple`, `2` steps, and `0.2` denoise
 - leave width and height at `0` unless you want an exact override; otherwise `megapixels` drives the target size
+- for long shots on smaller cards, start with `chunk_length = 85` and `temporal_overlap = 17` so the latent upscaler works in shorter temporal passes
 - leave the spatial tile inputs at their defaults first: `512x512` tiles, `64` overlap, `0` fade width, `earlier` overlap mode
 - keep `linear` blend first unless you want to reproduce a specific upstream stitch style
 - leave the split compatibility knobs alone unless you specifically need to mirror the upstream node behavior