NodeValid

Published video-model weights, licences and hardware notes

Mochi 1 records no clip length at all

There is no length figure in this repository: no seconds, no frame count, no frame rate. It states 480p, about 60GB of VRAM and a two-part parameter count, and leaves the duration unwritten. As of 2026-09-12.

Mochi 1 in the length column, as publishedThree columns filled and the length column empty means the output is half specified: a frame size with no indication of how many frames.Length as publishedNo length recordedframes, seconds or bothThe repository states apresent resolution insteadOutput size480ppixels per frameDescribed as the currentcapabilityMemoryAbout 60GB VRAM on a single GPUwhat holding them costAt least one H100recommendedOne clip, as this release describes itHalf an output specification
Fig. 1 An output described by its frame and not by its duration.
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: No length recordedThe detail published beside itThe detail published beside it — What the pages state: The repository states a present resolution insteadResolution, from the same pagesResolution, from the same pages — What the pages state: 480pHardware, from the same pagesHardware, from the same pages — What the pages state: About 60GB VRAM on a single GPU
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Mochi 1 in the length column, with the columns that qualify it. Read from github.com/genmoai on 2026-09-12.
ColumnWhat the pages state
Length, in the vendor's own wordsNo length recorded
The detail published beside itThe repository states a present resolution instead
Resolution, from the same pages480p
Hardware, from the same pagesAbout 60GB VRAM on a single GPU

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.

1Length is the column most often missing

Three releases in the register publish no clip length. It is the value that requires the maintainer to commit to something the model does variably, which is presumably why it is skipped.

For anyone planning production it is also the value that decides whether a shot can be generated in one call or has to be assembled. The gap has consequences.

2The resolution hedge points the same way

480p is described as the current capability, and a release whose maintainers hedge on the frame size is unlikely to commit to a duration. The two omissions are consistent with each other.

Both are honest about a release still moving. The register records the date it read them for that reason.

3What 60GB implies and does not say

A memory figure of about 60GB on a single GPU is high for 480p output, which suggests the clip is not trivially short. That is an inference and it stays out of the entry.

The cell records that no length is stated. A number derived from a memory figure would be the least defensible value in the register.

4Sources

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