NodeValid

Published video-model weights, licences and hardware notes

Pyramid Flow states 768p and 384p separately

This release publishes two checkpoints: 768p on one and 384p on the other, with ten seconds and five seconds respectively at 24 FPS. The output columns are full while the size and hardware columns are empty. As of 2026-09-22.

Pyramid Flow in the resolution column, as publishedA card can be complete about what comes out and silent about what it costs, and this one is the clearest example of that split in the register.Output size768p, with a 384pcheckpointsizes the memoryfigureMemory it sizesNo memory figurerecordedheld over thismany framesClip length10 seconds at 768p, 5at 384pFull on output, empty on costStated per checkpoint
Fig. 1 Output documented per checkpoint; the machine and the file size left unstated.
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 pagesstateResolution, in the vendor's own wor…Resolution, in the vendor's own wordsResolution, in the vendor's own words — What the pages state: 768p, with a 384p checkpointThe detail published beside itThe detail published beside it — What the pages state: Stated per checkpointHardware, from the same pagesHardware, from the same pages — What the pages state: No memory figure recordedLength, from the same pagesLength, from the same pages — What the pages state: 10 seconds at 768p, 5 at 384p
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Pyramid Flow in the resolution column, with the columns that qualify it. Read from huggingface.co/rain1011 on 2026-09-22.
ColumnWhat the pages state
Resolution, in the vendor's own words768p, with a 384p checkpoint
The detail published beside itStated per checkpoint
Hardware, from the same pagesNo memory figure recorded
Length, from the same pages10 seconds at 768p, 5 at 384p

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.

1Per-checkpoint documentation is the right shape

Two checkpoints with their own resolutions and their own clip lengths is exactly how a multi-release family should be described. Nothing has to be inferred about which figure belongs to which download.

Several larger releases in the register are less careful about this, stating one figure for a family that publishes three variants.

2The 384p checkpoint is the one with no alternative

A reader whose hardware cannot handle the 768p checkpoint has a published lower option, and no way to find out whether their card manages either, because no memory figure exists on the page.

Offloading is discussed without gigabytes, which tells them memory was a consideration and not what it amounts to.

3Frame rate stated for both

24 FPS covers both checkpoints, so ten seconds and five seconds are convertible into frames without guessing. Two other releases in the register leave that conversion open.

Between the resolutions, the lengths and the rate, the output side of this entry is among the best filled here. The other three columns are among the emptiest.

4Sources

Output sizes above appear on huggingface.co/rain1011, checked 2026-09-22. The full entry is at this family's page; what counts as a stated size is on resolution. Nearby: 540P and 720P in pixels, A default set for speed.