Why one repository publishes two hardware answers
One repository states that its smallest release runs on a consumer 4090, and that other commands in the same repository require at least 80GB of VRAM. Those describe different commands, and a reader who takes away one number has the wrong one half the time. As of 2026-09-12.
| Item | What is published | Detail |
|---|---|---|
| Smallest release | A consumer 4090 | Text and image to video, 5B |
| Other commands | At least 80GB of VRAM | Stated in the same repository |
| Gap between them | A desktop against a rented server | Not a rounding difference |
Inclusion rule. Both figures are recorded as stated. The register does not resolve them into a single requirement. Order. From the smallest requirement to the largest.
1Recording both, because picking one would mislead
Picking the consumer figure would make local deployment sound easy; picking the 80GB figure would make it sound out of reach. Both appear in the same document and they apply to different commands, so the register carries both and says which is which.
Resolving them would require deciding which command a reader intends to run, which is a decision about their project rather than a fact about the repository.
2Open weights do not have one hardware answer
The useful generalisation is not a number but a shape: a family of published models spans from a card somebody owns to a server somebody rents, and the label open source covers the whole range without distinguishing it.
Anyone budgeting a local deployment has to pick a specific release and a specific command before any hardware figure means anything, and this page exists to make that unavoidable.
3The LTX-Video repository takes the opposite approach
No stated minimum at all, and distilled and fp8 variants published specifically to run in less memory. That is intent rather than specification, and it leaves a reader to find their own floor by trying.
Neither approach is better. A stated figure can be wrong for your command; an unstated one cannot be wrong and cannot be planned against either.
- HardwareThe repository states TI2V-5B runs on consumer-grade graphics cards such as a 4090, generating a 5-second 720P video in under 9 minutes on a single consumer GPUvendor's own figure
- HardwareOther commands in the same repository state a requirement of at least 80GB of VRAMthe larger models
4Open weights, hosted
Instead of local hardware for “4090 or 80GB”, SceneMixer runs hosted models; its guides describe the result:
Image and video models take a description as a list of things to put in the frame.
SceneMixer, Describe the Cause, Not the Result: The One Rule Behind Good Sheets and Good Shots (read 2026-10-13)
In the editor this tier is greyed out for such a segment; pick a Seedance 2.5 or Wan tier.
SceneMixer, Seedance 2.0 (standard tier) — “Can a segment longer than 15 seconds use this tier?” (read 2026-10-13)
5Sources
Repository statements and hosted rates are linked from the model pages and the method page, checked 2026-09-12. Hardware figures are set out on requirements. Nearby: Clip length, Buy or run, Same licence, different reach.