Which releases state size, rate and length together
Four of the 15 families publish a frame size, a frame rate and a clip length together. The others leave one or more of the three unstated, and one publishes none of them as an output at all. As of 2026-09-12.
| Item | What is published | Detail |
|---|---|---|
| All three stated | Four families | 720 x 1280 at 15 FPS in six seconds; 720P at 16FPS in five seconds; 768p and 384p at 24 FPS; 720P at 24fps in a five-second clip |
| Size and rate, length described | One family | 720p at 30fps, output called minutes-long |
| Size and length, rate unstated | Three families | 1360x768 with up to 161 frames; 544 x 960 with a frame table; 576x1024 with 25 frames |
| Size only | Four families | 480p; two memory-table configurations; 256px and 768px; a 720x720 default |
| Length only | Two families | A minute at 30fps with no frame size; up to 60 seconds |
| Neither, as an output | One family | Pixel sizes appear only as memory settings |
Inclusion rule. One row per combination of the three output values. A combination used once keeps its row, because the incomplete cases are the finding. Order. From the most complete specification to the least.
1Completeness is not the same as ambition
Three of the four complete rows describe short output: six seconds, five seconds, and ten seconds on one checkpoint. The releases making the longest claims are among the least completely specified.
That inversion is worth naming. A fully described five seconds is more useful to a production than an undescribed minute, and the column does not rank the two.
2The missing value is usually the rate
Eleven families publish a frame size and five publish a rate. A frame count with no rate cannot be turned into seconds, and a duration with no rate cannot be turned into frames, so the rate is the value that closes the specification.
It is also the cheapest of the three to publish, which makes its absence a documentation habit rather than a technical limit.
3Why the register does not fill the gaps
A frame size could be read off a demo clip and a rate could be assumed from convention. Both would put values in the register that no vendor stated, on rows where readers would be most likely to rely on them.
The absences are recorded as absences, and the qualifying columns keep whatever the vendor did publish. An uneven column is the honest result.
- Resolution and length720 x 1280, 88 frames, 6 seconds at 15 FPSfrom the model info table
- Resolution and lengthProduces 720P video with 16FPS, as a 5-second clipboth stated on the card
- Length10-second videos at 768p resolution and 24 FPS, with a 384p checkpoint that generates 5-second video at 24FPSstated per checkpoint with the frame rate
- Smallest published modelA 5B text-to-video and image-to-video model at 720P and 24fpsTI2V-5B
- Resolution720p, 30fps videosstated with a frame rate and no memory figure beside it
4Sources
Repository statements and hosted rates are linked from the model pages and the how read page, checked 2026-09-12. Hardware figures are set out on requirements. Nearby: Two figures, one run, Which variant, Consumer cards.