tool/endpoint: templates/ltx2/* — no restoration pass exists; two-stage is the only sharpening route
repro: the family's only answer to a soft or noisy render is templates/ltx2/two-stage
(eight sigmas at 768x448, 2x latent upsample, three stage-two sigmas at 1536x896) or
templates/ltx2/generative-upscale. Both re-render. Neither cleans up an existing result.
what's now available: two LTX-2.5 IC-LoRAs from 2026-09-10:
why it is worth measuring rather than assuming. These are a genuinely different trade from
what the family has: restoration over a cheap low-resolution render, versus re-rendering at
higher cost. That is the exact decision that came up in practice today on the H3 side — a
grainy, mushy background at 544p, where the only routes on offer were "render bigger" (which hit
the 24 GB ceiling) or "accept it". Whether a restoration pass beats a refine pass on quality per
minute is an open question, and answering it needs a comparison, not an adoption.
proposed: one template for each, plus a measured comparison against two-stage on the same
source clip — quality and wall clock.
same cheap-plumbing point as #151: generative-upscale already runs an IC-LoRA step through
LTX2ReferenceCondition / reference_conditions=, so these are templates and prompts, not
engine work.
caveats: both weights are 0.9 previews (only Clean-Plate shipped at 1.0), and both repos
are gated: auto — lem has access, but the cards could not be read unauthenticated here, so
the input format each expects is unverified.
related: #151 (Ingredients, same IC-LoRA batch); full write-up on #151.
tool/endpoint:
templates/ltx2/*— no restoration pass exists;two-stageis the only sharpening routerepro: the family's only answer to a soft or noisy render is
templates/ltx2/two-stage(eight sigmas at 768x448, 2x latent upsample, three stage-two sigmas at 1536x896) or
templates/ltx2/generative-upscale. Both re-render. Neither cleans up an existing result.what's now available: two LTX-2.5 IC-LoRAs from 2026-09-10:
LTX-2.5-22b-IC-LoRA-Deblur—ltx-2.5-22b-ic-lora-deblur-0.9.safetensorsLTX-2.5-22b-IC-LoRA-Decompression—ltx-2.5-22b-ic-lora-decompression-0.9.safetensorswhy it is worth measuring rather than assuming. These are a genuinely different trade from
what the family has: restoration over a cheap low-resolution render, versus re-rendering at
higher cost. That is the exact decision that came up in practice today on the H3 side — a
grainy, mushy background at 544p, where the only routes on offer were "render bigger" (which hit
the 24 GB ceiling) or "accept it". Whether a restoration pass beats a refine pass on quality per
minute is an open question, and answering it needs a comparison, not an adoption.
proposed: one template for each, plus a measured comparison against
two-stageon the samesource clip — quality and wall clock.
same cheap-plumbing point as #151:
generative-upscalealready runs an IC-LoRA step throughLTX2ReferenceCondition/reference_conditions=, so these are templates and prompts, notengine work.
caveats: both weights are 0.9 previews (only Clean-Plate shipped at 1.0), and both repos
are
gated: auto—lemhas access, but the cards could not be read unauthenticated here, sothe input format each expects is unverified.
related: #151 (Ingredients, same IC-LoRA batch); full write-up on #151.