NodeValid

Published video-model weights, licences and hardware notes

MAGI-1 sets no ceiling on frames

The repository treats the frame count as an argument and states no maximum for it. There is no ceiling and no duration anywhere, on a release that is otherwise specific about cards, memory and resolution. As of 2026-09-22.

MAGI-1 in the length column, as publishedAn unbounded argument is not the same as an unbounded model, and a register cannot record either one as a value.Length as publishedNo ceiling recordedframes, seconds or bothFrames are an argument withno stated maximumOutput size720 x 720 as the 4.5B defaultpixels per frameSet for speed; arbitraryresolutions described assupportedMemoryH100 or H800 x 8 for the 24Bwhat holding them costOne RTX 4090 for the 4.5B;12GB for a distilled fp8buildOne clip, as this release describes itUnbounded is not a figure
Fig. 1 The length column empty on a release that fills the hardware column three times over.
What the repositories actually stateFilled where the repository states something, hollow where it does not. A blank is not an inference.What the repositories actually stateWhat the pages stateWhat the pagesstateLength, in the vendor's own wor…Length, in the vendor's own wordsLength, in the vendor's own words — What the pages state: No ceiling recordedThe detail published beside itThe detail published beside it — What the pages state: Frames are an argument with no stated maximumResolution, from the same pagesResolution, from the same pages — What the pages state: 720 x 720 as the 4.5B defaultHardware, from the same pagesHardware, from the same pages — What the pages state: H100 or H800 x 8 for the 24B
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
MAGI-1 in the length column, with the columns that qualify it. Read from github.com/SandAI-org on 2026-09-22.
ColumnWhat the pages state
Length, in the vendor's own wordsNo ceiling recorded
The detail published beside itFrames are an argument with no stated maximum
Resolution, from the same pages720 x 720 as the 4.5B default
Hardware, from the same pagesH100 or H800 x 8 for the 24B

Inclusion rule. The value this page is about, the detail the vendor attached to it, and the two columns that change how it should be read. A column the vendor left empty keeps its row and says so. Order. This column first, then its detail, then the two columns that qualify it.

1Why an absent ceiling is not generosity

A model that accepts any frame count will still degrade, run out of memory or drift at some point. Publishing no maximum leaves the reader to discover where, which is the expensive way to find out.

It is also consistent with the rest of the page, which describes arbitrary resolutions as supported. The release is documented by what it accepts rather than by what it guarantees.

2The hardware side is the opposite

Eight H100 or H800 cards for the 24B, one RTX 4090 for the 4.5B, at least 24GB for the 4.5B itself and at least 12GB for a distilled fp8 build. Four separate statements.

None of them names a clip length, so the most carefully costed release in the register has no output duration to cost.

3What the register records

That frames are an argument with no stated maximum. Reading a default out of a configuration file would produce a value the repository never presented as a limit.

The absence is filed as an absence, beside a resolution default of 720x720 that is explicitly a speed choice rather than a bound.

4Sources

Lengths above are in the unit the vendor chose, from github.com/SandAI-org on 2026-09-22, with no conversion applied. The full entry is at this family's page; frames against seconds is on length. Nearby: Five seconds, stated, Minutes, with no number.