NodeValid

Published video-model weights, licences and hardware notes

Upscaling, and what a register cannot record

Upscaling enlarges generated frames after the fact, using a separate model. It is a real part of many pipelines and it is not part of any release in this register, so it never enters the resolution column. As of 2026-09-22.

Where the register stopsThe published resolution describes what the weights produce; anything added afterwards is a different model with its own licence, memory and failure modes.Whose output is this frame sizeThe released weightsIn the registerQuoted from the repository, with therelease and the date it was read.A later stageOut of scopeA separate model with its own terms,requirements and behaviour.A second model, a second entry
Fig. 1 One boundary, drawn where the release ends.
What an upscaling stage brings with it. Recorded 2026-09-22.
ItemBelongs to the second model
LicenceYes, and it may differ
Memory requirementYes, in addition
ArtefactsYes, of its own kind
RuntimeYes, added per clip

Inclusion rule. Things an added stage contributes. Everything listed belongs to a model this register does not hold, which is why the stage is out of scope. Order. From the contractual items to the operational ones.

1Why the boundary is worth stating

A production comparing a 480p release with a 720P one may intend to upscale the first. That is a reasonable plan and it changes the licence surface, the memory total and the output characteristics.

None of those changes are recorded here, because none of them are published by the video release. The register holds what the repository states and stops at its edge.

2Upscaled output is not the same as generated output

Enlarging frames adds detail that was not generated, with its own texture and its own failure modes across a moving sequence. It is not equivalent to a model that produces the larger frame.

So a resolution comparison across this register compares what the weights produce. Anything after that is a pipeline decision the entries deliberately do not cover.

3The boundary in the register

The resolution column holds what the released weights produce. Anything added afterwards is a second model with its own licence, its own memory figure and its own artefacts, none of which any entry here records.

That is the same line drawn around interpolation. A production may well cross it, and the register stops at the edge of the release so that its own cells stay traceable.

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 resolution column and on that family's own page. Nearby terms: Frame count, Frame rate.