NodeValid

Published video-model weights, licences and hardware notes

Open-Sora names 256px and 768px as supported

The repository states that the 11B model supports 256px and 768px resolution. It is a pair of supported sizes rather than one output, and only the larger of the two has a memory figure beside it. As of 2026-09-22.

Open-Sora in the resolution column, as publishedNaming two supported sizes and measuring one of them leaves the cheaper option documented as possible and not as costed.Output size256px and 768pxsizes the memoryfigureMemory it sizes60.3GB peak at 768px onone GPUheld over thismany framesClip lengthnum_frames of 4k+1,under 129Supported is not the same as measuredThe pair the 11B model is stated to support
Fig. 1 Two sizes offered, one of them measured, and the gap between them unpriced.
Open-Sora in the resolution column, with the columns that qualify it. Read from github.com/hpcaitech on 2026-09-22.
ColumnWhat the pages state
Resolution, in the vendor's own words256px and 768px
The detail published beside itThe pair the 11B model is stated to support
Hardware, from the same pages60.3GB peak at 768px on one GPU
Length, from the same pagesnum_frames of 4k+1, under 129

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.

1Supported is a stronger word than stated

Most resolution values in the register are descriptions of what a release does. This one is a claim about what it accepts, which is a wider statement and a more useful one for a pipeline.

The wording is the vendor's own and the register keeps it. A supported list implies choice; an output figure implies a single behaviour.

2The small size is the interesting one and the unmeasured one

60.3GB is stated at 768px on one GPU and 44.3GB across four. Nothing is stated at 256px, which is the size somebody with a smaller card would reach for first.

That is the reverse of the usual omission. Vendors normally document the cheap configuration and leave the expensive one implied.

3Frames are a rule rather than a size

The repository writes the length constraint as candidate values of 4k+1 under 129, which is what the code enforces rather than a clip length. Combined with two resolutions, the output space is described by rules.

That is a developer's documentation and it is precise. It also means the register cannot record a single output specification for this release, only the boundaries of one.

4Sources

Output sizes above appear on github.com/hpcaitech, checked 2026-09-22. The full entry is at this family's page; what counts as a stated size is on resolution. Nearby: 576x1024 from training, No frame size given.