NodeValid

Published video-model weights, licences and hardware notes

Which releases publish frames and no frame rate

Five of the 15 families publish a frame rate. Three publish a frame count with no rate at all, three give frames and seconds without naming the rate, two give seconds only, and two publish no length. As of 2026-09-12.

Frames, seconds and the rate between themFrames are what the code produces and seconds are what a viewer experiences; the rate is the only thing that connects them, and it is missing from several rows.FramesWhat the run producesneeds a rateRateFrames per second ofplaybackgives secondsSecondsWhat a shot plan iswritten inNo default rate is safe hereRates stated in this register run from fifteen to thirty frames a second, so assuming avalue would be wrong on several rows.
Fig. 1 Two of the three values are published often; the one that joins them frequently is not.
How clip length is expressed across the register, by the units published. Recorded 2026-09-12.
ItemWhat is publishedDetail
A rate publishedFive families15 FPS, 16FPS, 24 FPS and 30fps, twice
Frames and no rateThree familiesUp to 204 frames; 129 frames as a setting; num_frames of 4k+1 under 129
Frames and seconds, rate unstatedThree families161 frames as five or ten seconds; 257 to 1457 frames against seconds; 25 frames in four seconds or less
Seconds and no framesTwo familiesUp to 60 seconds; a five-second clip
No length at allTwo familiesFrames are an argument with no maximum, or nothing

Inclusion rule. One row per combination of length units. A combination used by two families keeps its row, because the combination decides whether the value converts. Order. From the most complete combination of units to the least.

1Frames are the honest unit for memory

Activation memory scales with the frames held at once, so a memory table labelled in frames is internally consistent. One repository here labels its configurations that way throughout and never mentions a rate, which is coherent rather than careless.

The cost lands on anyone writing a shot plan. Two hundred and four frames is somewhere between seven and thirteen seconds depending on a number that was never written down.

2The middle row is the most misleading

Three releases publish frames and seconds together and never name the rate. One of them gives two durations for the same frame count, which means two rates are in play and neither is stated.

That reads as a complete answer and is not one. The register keeps both values as written rather than picking a rate to reconcile them.

3Why nothing is converted here

Published rates in this register include fifteen, sixteen, twenty-four and thirty frames a second. A register that assumed any one of them would be wrong about several rows and would not flag which.

So counts stay counts and seconds stay seconds. The rate, where it exists, is recorded beside them, and where it does not the cell says so.

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: Exact or rounded, Complete output, Two figures, one run.