NodeValid

Published video-model weights, licences and hardware notes

Sequence packing, and the floor it explains

Sequence packing processes a long clip in sections rather than holding every frame at once. It is the kind of engineering that lets a thirteen billion parameter model state a six gigabyte floor for a full minute of output. As of 2026-09-22.

Holding a whole clip against holding a sectionMemory scales with the frames held at once rather than with the frames produced, so sectioning the sequence breaks the link between clip length and card size.Whole clip residentSectionedMemoryScales with total framesScales with a sectionLong clipsBounded by the cardBounded by timeConsistencyEasier within one passNeeds carrying between sectionsPublished floorHighCan be lowFrames produced, frames resident
Fig. 1 The reason the length column and the hardware column are not proportional.
What sectioning trades away for the lower requirement. Recorded 2026-09-22.
GainedGiven up
A lower memory floorLonger wall-clock time
Longer clips on small cardsExtra state carried between sections
Reach to consumer hardwareMore places for consistency to slip
A checkable claimA more complex implementation

Inclusion rule. Trades a sectioning approach makes. Rows pair a gain with what it costs, with no vendor figure attached. Order. From the trade about memory to the trade about implementation.

1It explains an otherwise puzzling row

The lowest memory floor in this register belongs to a release of the same nominal size as one that publishes no figure at all and one that needs over seventy gigabytes. The difference is approach rather than scale.

That is the clearest demonstration available that the hardware column measures engineering as much as it measures weights.

2The consistency cost lands in the length column

Carrying context between sections is where drift creeps in, so an approach that buys long output cheaply also has the most to lose across a minute.

No repository here publishes a measurement of that, so the register records the floor and the length as stated, and leaves the quality question to whoever runs a test.

3The row this explains

The lowest memory floor in the register belongs to a release of the same nominal size as one that publishes no figure and one that needs over seventy gigabytes. The difference is approach rather than scale.

That is the clearest demonstration available here that the hardware column measures engineering as much as weights, and the reason no figure is ever carried from one row to another.

A reading note, not an entry: no vendor value appears on this page. Where the register records this term for a particular release, it is on the length column and on that family's own page. Nearby terms: Permissive licence, Vendor-written licence.