Files
comfyui-workflows/optimized/notes/ltx.md
T

1.8 KiB

LTX Notes

Current default assumptions

  • Low-VRAM practicality matters more than graph sophistication.
  • The first question is whether LTX 2.3 is usable at all on Chris's 3070.

Strong current source workflows

  • models/ltx/ltx23-i2v-t2v-simple-single-pass/
  • models/ltx/ltx23-t2v-simple-single-pass/
  • models/ltx/ltx23-first-last-frame/
  • models/ltx/ltx23-character-sheet-best-face-id/
  • models/ltx/ltx25-multiple-subject-reference/

Strong current heuristics

  • Start with simple single-pass before trying larger consistency graphs.
  • Prefer split-model and extracted-model routes when the source pack says they are easier locally.
  • Treat first-last-frame and character-sheet workflows as second-wave tests, not the baseline.
  • Keep the LTX-2.5 multi-subject reference pack as the best current donor for heavier consistency work, but do not let it displace the simpler LTX 2.3 master until we have proof on the 3070.

Current weak areas

  • No real proof yet for what is genuinely practical on Chris's box.
  • Community packs bundle lots of helper nodes, which raises import fragility.
  • The newer LTX-2.5 reference pack looks promising, but it is not yet a clean default candidate.

Best current optimization direction

  • Keep LTX in models/ltx/ and notes until it earns a real maintained optimized slot again.
  • Only promote first-last-frame or character-sheet variants after the simple master proves viable.
  • Use the LTX-2.5 multi-subject reference workflow as a future donor for reference-heavy jobs, not as the baseline.

What needs Monday proof

  • whether the simple master loads and runs at all on the 3070
  • whether preview/decode or the core model path is the real bottleneck
  • whether LTX has any realistic chance of displacing MiniMax for local use