LTX-2.5 native multishot: one prompt, or clips joined on Sume
LTX-2.5 adds native multishot: connected scenes in one pass, consistent characters. Sume has no LTX; its route is separate clips joined on Timeline 1.0.

LTX-2.5's model card on Hugging Face (read 2026-10-02) says the release introduces native multishot generation: connected scenes in a single pass, keeping character identity, environment and visual style across cuts. Sume does not list an LTX model, so the Sume route to a multi-shot video is to generate each shot as its own clip and assemble them with Timeline 1.0.
What the model card says
The Lightricks/LTX-2.5 card (read 2026-10-02) lists the items below. Other coverage dates the launch to Aug 11, 2026; this page relies on the card itself for the specs.
| Item | Listed on the model card |
|---|---|
| Transformer | 22B distilled DiT |
| Text encoder | Gemma 4 12B |
| Multishot | Native, connected scenes in a single pass |
| Frame count | num_frames % 8 == 1, up to 121 frames at standard frame rates |
| Resolution | Divisible by 32; from 544x960 (stage 1) up to 4K with spatial upscaling |
| Commercial use | Free under $10M annual revenue under the LTX-2.x Community License; above that a paid agreement |
One pass versus one shot at a time
A single multishot generation has one advantage: the model sees the whole sequence, so a character who appears in shots one and three is more likely to match. The cost is control. If shot two is wrong you regenerate the sequence, or use whatever per-segment tools the pipeline offers.
Generating shot by shot reverses that trade. You can fix one clip without touching the others, but you carry consistency yourself, with references, a fixed first frame, or a shared prompt block.
The Sume route
Sume's video API generates a clip per job. Limits vary by model: for example Wan 3.0 accepts 2 to 30 seconds and Seedance 2.5 4 to 30 seconds per the video docs. To join shots, Timeline 1.0 takes one audio spine plus ordered video[] slots and returns one MP4, handling sequencing and transitions.
Models that accept image references, such as those listed in the catalog, can help keep a character stable across separate shots. Sume has no single-pass multishot switch, and does not claim cross-shot consistency from the join itself.
Decision notes
Check the model card again before shipping; specs and license terms can change.
- Short sequence, one look, you control the GPU: LTX-2.5 multishot may suit.
- Many iterations on single shots, hosted: separate clips plus a timeline.
- Revenue above $10M: read the LTX license terms before you build on the weights.
Sources
Related posts
More in Models
- LTX-2.5 Pixel Spatial Upscaler: draft at 280p, then upscale 2x
The LTX-2.5 Pixel Spatial Upscaler re-renders a low-res draft 2x with invented detail. How the draft workflow works and how Sume's draft-then-final differs.
- LTX-2.5 quantization: fp8-cast, fp8-scaled-mm or NVFP4?
LTX-2.5's repo offers fp8-cast with bf16 checkpoints and fp8-scaled-mm on Hopper; the Hugging Face card lists NVFP4 and int8. Which flag fits which GPU.
- LTX-2.5 Refine Details: 22 minutes per clip on an RTX PRO 6000
The LTX-2.5 Refine Details LoRA rebuilds texture up to 4K but takes about 22 minutes for 121 frames on an RTX PRO 6000. A hosted upscale compared.
- LTX-2.5 Slow-Motion Control: speed 0.025 to 1.0, 40x slower
The LTX-2.5 Slow-Motion Control LoRA sets motion speed from 0.025 (40x slow) to 1.0 while playback stays 24 fps. Sume's video API has no speed field.
Written by Sume