NodeValid

Published video-model weights, licences and hardware notes

Pyramid Flow gives ten seconds and five

The card states ten seconds at 768p on one checkpoint and five seconds at 384p on the other, both at 24 FPS. Duration and rate are given per checkpoint, so nothing about the length needs inferring. As of 2026-09-22.

Pyramid Flow in the length column, as publishedLengths published per checkpoint with a shared frame rate let a reader choose a download from a target duration rather than the other way round.Length as published10 seconds at 768p, 5 at 384pframes, seconds or bothSeconds, at 24 FPS, for bothcheckpointsOutput size768p, with a 384p checkpointpixels per frameStated per checkpointMemoryNo memory figure recordedwhat holding them costOffloading is discussedwithout gigabytesOne clip, as this release describes itLength chosen by checkpoint
Fig. 1 Two durations, two resolutions and one rate, each attached to its own download.
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: 10 seconds at 768p, 5 at 384pThe detail published beside itThe detail published beside it — What the pages state: Seconds, at 24 FPS, for both checkpointsResolution, from the same pagesResolution, from the same pages — What the pages state: 768p, with a 384p checkpointHardware, from the same pagesHardware, from the same pages — What the pages state: No memory figure recorded
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Pyramid Flow in the length column, with the columns that qualify it. Read from huggingface.co/rain1011 on 2026-09-22.
ColumnWhat the pages state
Length, in the vendor's own words10 seconds at 768p, 5 at 384p
The detail published beside itSeconds, at 24 FPS, for both checkpoints
Resolution, from the same pages768p, with a 384p checkpoint
Hardware, from the same pagesNo memory figure recorded

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.

1Duration as the selection key

Ten seconds at 768p or five at 384p is a choice between output length and frame size, and the card presents it as exactly that. The reader picks a checkpoint by what they need.

Most families in the register make that choice on parameter count instead, which is a less direct way to arrive at the same decision.

2A shared frame rate keeps the pair comparable

24 FPS covers both, so ten seconds is 240 frames and five is 120. The two checkpoints differ in duration and resolution and not in rate, which makes the comparison clean.

It also means neither figure needs the conversion that three other rows in this register leave open.

3Ten seconds with no cost attached

Neither checkpoint has a memory figure, and the card publishes no parameter count. So the longest output this release offers cannot be costed from its own documentation.

The length column here is among the best filled in the register and the two columns that would let a reader act on it are empty.

4Sources

Lengths above are in the unit the vendor chose, from huggingface.co/rain1011 on 2026-09-22, with no conversion applied. The full entry is at this family's page; frames against seconds is on length. Nearby: A frames-to-seconds table, No ceiling on frames.