NodeValid

Published video-model weights, licences and hardware notes

HunyuanVideo counts 129 frames as a setting

129 frames appears on these pages as part of the configuration a 60GB memory figure was measured at. It is not offered as a maximum, and no frame rate accompanies it, so the clip length in seconds is unstated. As of 2026-09-12.

HunyuanVideo in the length column, as publishedA frame count inside a memory configuration describes one run that finished, and says nothing about the longest clip the weights will produce.Length as published129 frames, as a measurementsettingframes, seconds or bothFrames, sizing a memoryfigure rather than a ceilingOutput sizeNo output size recordedpixels per frameIts pixel dimensions sizethe memory figures insteadMemory60GB peak at 720px1280px, 129frameswhat holding them cost45GB at 544px960px, on asingle 80G GPUOne clip, as this release describes itA test point, not a ceiling
Fig. 1 Frames appearing as a measurement setting rather than as a published limit.
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: 129 frames, as a measurement settingThe detail published beside itThe detail published beside it — What the pages state: Frames, sizing a memory figure rather than a ceilingResolution, from the same pagesResolution, from the same pages — What the pages state: No output size recordedHardware, from the same pagesHardware, from the same pages — What the pages state: 60GB peak at 720px1280px, 129 frames
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
HunyuanVideo in the length column, with the columns that qualify it. Read from github.com/Tencent-Hunyuan on 2026-09-12.
ColumnWhat the pages state
Length, in the vendor's own words129 frames, as a measurement setting
The detail published beside itFrames, sizing a memory figure rather than a ceiling
Resolution, from the same pagesNo output size recorded
Hardware, from the same pages60GB peak at 720px1280px, 129 frames

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.

1Two things a frame count can be

A ceiling is a claim about the model. A configuration is a record of what somebody ran. This number is the second kind, and treating it as the first would invent a limit the repository never asserted.

It also means a reader cannot tell whether 200 frames works. The measurement establishes that 129 completed on an 80G card and stops there.

2No frame rate anywhere

Without a rate, 129 frames cannot be converted into seconds. At 24 FPS it is about five and a half; at 16 it is eight. The register does not choose, because choosing would mean publishing a number the vendor did not.

Two other releases here have the same gap. Three publish frames, seconds and a rate together, which is what closes the conversion.

3What the pairing with 60GB does establish

That 129 frames at 720px1280px fitted inside 60GB of peak memory on a single 80G card. As a capacity statement that is specific and reproducible.

As a length statement it is silent. The register files the number under length because that is what it measures, and marks it as a setting so nobody quotes it as a maximum.

4Sources

Lengths above are in the unit the vendor chose, from github.com/Tencent-Hunyuan on 2026-09-12, with no conversion applied. The full entry is at this family's page; frames against seconds is on length. Nearby: 161 frames in seconds, No length recorded.