NodeValid

Published video-model weights, licences and hardware notes

Pixels from a memory table against an output row

HunyuanVideo's pixel figures, 720px1280px and 544px960px, are the configurations two memory measurements were taken at. Allegro publishes 720 x 1280, 88 frames, six seconds at 15 FPS as an output. As of 2026-09-22.

HunyuanVideo and Allegro on the same columnA pixel size can enter a repository as an output specification or as a row label on a memory table, and the two are not the same claim.HunyuanVideoAllegroResolution, as each vendorstates itNo output size recorded720 x 1280The detail published beside itIts pixel dimensions size the memoryfigures insteadFrom the model info table on the cardHardware, from the same pages60GB peak at 720px1280px, 129 frames9.3G BF16 with cpu_offloadA measurement setting, or a product
Fig. 1 The same kind of number doing two different jobs on two cards.
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 stateHunyuanVideoAllegroResolution, as each vendor states…Resolution, as each vendor states itResolution, as each vendor states it — HunyuanVideo: No output size recordedResolution, as each vendor states it — Allegro: 720 x 1280The detail published beside itThe detail published beside it — HunyuanVideo: Its pixel dimensions size the memory figures insteadThe detail published beside it — Allegro: From the model info table on the cardHardware, from the same pagesHardware, from the same pages — HunyuanVideo: 60GB peak at 720px1280px, 129 framesHardware, from the same pages — Allegro: 9.3G BF16 with cpu_offloadLength, from the same pagesLength, from the same pages — HunyuanVideo: 129 frames, as a measurement settingLength, from the same pages — Allegro: 88 frames, 6 seconds at 15 FPS
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
HunyuanVideo and Allegro on the resolution column, read from github.com/Tencent-Hunyuan and huggingface.co/rhymes-ai. Recorded 2026-09-22.
PointHunyuanVideoAllegro
Resolution, as each vendor states itNo output size recorded720 x 1280
The detail published beside itIts pixel dimensions size the memory figures insteadFrom the model info table on the card
Hardware, from the same pages60GB peak at 720px1280px, 129 frames9.3G BF16 with cpu_offload
Length, from the same pages129 frames, as a measurement setting88 frames, 6 seconds at 15 FPS

Inclusion rule. Two families whose published values in this column lead to opposite decisions. A pair that happens to agree is not listed, because agreement is already visible on the column summary. Order. The column itself first, then its detail, then the columns that qualify it.

1Where a figure sits decides what it claims

A resolution stated as output says this is what comes out. The same number labelling a memory measurement says a run at that size finished, and implies nothing about other sizes.

Both repositories publish 720 by 1280. Only one of them is asserting it as a frame the model produces, and the register records only that one in this column.

2What the memory table does establish

That both of HunyuanVideo's sizes were run to completion on a single 80G card, with 129 frames at the larger. As a capacity statement that is specific and reproducible.

It also fixes the aspect ratios actually exercised, which is useful for anyone planning vertical output and is not an output specification.

3The complete row is complete in four values

Allegro gives the size, the frame count, the duration and the rate, and the memory figures for the same run sit beside them. Nothing about that output needs inferring.

That is the shape this column wants. The other row is not careless; it is a release documented through measurements of runs rather than descriptions of outputs.

4Sources

Read from github.com/Tencent-Hunyuan and huggingface.co/rhymes-ai on 2026-09-22. Full entries: HunyuanVideo and Allegro. What this column is quoting is on resolution. Nearby pairs: 6GB against 78GB, Same size, one answer.