LTX-Video publishes frames where others publish seconds
The model card states that quality holds below 257 frames and that the released model produces thirty frame per second video at 1216x704. It also requires frame counts divisible by eight plus one. A length is recoverable, but the card never prints one. As of 2026-09-22.
| Statement on the card | Value | What it contributes |
|---|---|---|
| Where quality holds | Frames below 257 | The ceiling, in frames |
| What the released model produces | 30 FPS at 1216x704 | The divisor |
| Accepted frame counts | Divisible by 8, plus 1 | Which values inside the ceiling are legal |
Inclusion rule. Statements on the model card that bear on how long one generation runs. A seconds figure is not recorded, because the card does not print one and this register does not convert. Order. Ceiling, then rate, then the rule that filters the values between them.
1A unit mismatch is a gap, not a detail
Every ad slot this register reads is written in seconds. This row is written in frames. The arithmetic is trivial and the register still declines to do it, because a converted figure would sit in the table looking exactly like a published one.
The reason to hold the line is the divisibility rule. Frames divisible by eight plus one means legal counts are 249, 241, 233 and so on, and a seconds figure computed from the ceiling would land on values the model refuses. The unit carries a constraint that the conversion loses.
2Below 257 is a quality statement, not a hard limit
The wording matters. The card says the model works best under that count, which is weaker than a refusal and stronger than a suggestion. A request above it may return something; the card declines to say what.
This register records the two kinds of statement differently wherever a page allows it. A ceiling that refuses is a planning fact. A ceiling that degrades is a risk, and the difference decides whether a shot list can be written against the number or only near it.
3What the card gives instead of a duration
What is published is unusually precise about shape and rate: 1216x704 and thirty frames a second, both as single values rather than ladders. This is a research artefact described for someone running it, not a product described for someone buying it.
Read that way the missing seconds figure is consistent rather than careless. Nobody running inference locally needs the length in the unit an ad slot uses, and nobody planning a campaign can use the card without doing a conversion the card never authorised.
4Where this cell sits in the column
| Generator | Duration |
|---|---|
| Amazon Nova Reel | 6 s increments, up to two minutes |
| CogVideoX | 6 s, at 49 frames |
| Google Veo | 4, 6 or 8 s |
| Grok Imagine | 1 to 15 s |
| Hedra | 10 minutes |
| HeyGen | 30 minutes per scene |
| Kling AI | Not stated |
| LTX-Video | Frames, never seconds |
| MiniMax | 4 to 15 s |
| Pika | 5 s and 10 s, 20-25 s on Pikaframes |
| PixVerse | 1 to 15 s on version 6 |
| Runway | 5 to 15 s on Gen-4.5 |
| SceneMixer | Thirty seconds on the Wan tiers, fifteen on H3 |
| Vidu | Not stated |
| Wan 3.0 | 2 to 30 s |
Inclusion rule. Every generator with a row in this register, carrying whatever its own page states as a length. A page that states none keeps its row and says so. Order. Alphabetical by generator name.
- Where the card says quality holds; length is published in framesWorks best on resolutions under 720 x 1280 and number of frames below 257not seconds
- Shapes and lengths the model acceptsResolutions that are divisible by 32 and number of frames that are divisible by 8 + 1
- What the released model produces30 FPS videos at a 1216x704 resolution
5Sources
Read from the Lightricks LTX-Video model card, checked 2026-09-22. The column itself is described on duration, and the rule that keeps surfaces and generators apart is on method. Next along this column: MiniMax, Pika.