A current generation, and the earlier ones unaddressed
This page names a current generation and a separate real-time line, which is a product distinction rather than a lifecycle one. Whether the two earlier generations are still offered is not addressed. Neither of the named lines is presented as the route off the other. From 1 source page, read 2026-09-22; no maker pays to be listed.
| What the page is asked | What Vidu publishes | What that leaves open |
|---|---|---|
| Is a successor named | Nothing names one | Two lines are named, neither as a destination |
| Are earlier generations addressed | Not addressed on the page read | Numbered versions imply that they existed |
| What separates the two named lines | One is presented as a real-time model | A capability split, not a version sequence |
| What a reader can rely on | Only that both named lines exist today | With no statement about either continuing |
Inclusion rule. Read from the public home page. A version still reachable in the product but not named on a public page does not fill a cell. Order. The absence first, then what the two named lines are.
1Two lines that are not two generations
Naming a current model and a real-time model looks at a glance like an older and a newer version sitting together. It is not: the split is about how fast a result arrives, so neither line is a fallback for the other.
That distinction decides whether this entry has a cushion. A capability split gives a production two tools; a version split gives it somewhere to stand when one moves. This page publishes the first.
2Numbering invites a question the page leaves open
A generation labelled with a number tells every reader that lower numbers existed. Nothing here says whether they are still purchasable, which is the one thing a production already working on one of them needs.
The register records the silence rather than resolving it. Assuming the older lines are gone would be as unfounded as assuming they remain, and both guesses lead to a different plan.
3Production that outlasts a model
Model end dates touch “Vidu”; SceneMixer's guides describe how its pipeline treats the models it runs:
16:9 landscape (SceneMixer's default) and 9:16 vertical (the usual short-drama frame), chosen per project.
SceneMixer, Seedance 2.0 in a Real Short-Drama Pipeline — “Which aspect ratios does the pipeline generate?” (read 2026-10-13)
AI dubbing replaces the audio of a finished clip and then tries to match the lips. Native-language generation gives the video model the line in the target language before the shot exists, so mouth movement, pauses and shot length are produced for that language.
SceneMixer, Native-Language Dialogue vs. Dubbing in AI Video (2026): Why the Cast Should Speak the Line — “Is native-language generation the same as AI dubbing?” (read 2026-10-13)
4Where this leaves a series already in flight
A production mid-season on an unnamed earlier generation cannot tell from any public page whether it will be able to finish. The absence of a date is not reassurance, and the presence of a newer line is not a deadline.
The defensible response is the one this register keeps recommending in place of prediction: record which model made which delivered file, and archive the files themselves. Both are cheap now and impossible to reconstruct later.
- Whether Q1 and Q2 are still offeredNot stated (as of 2026-09-12)not stated
5Sources
Read from the home page on vidu.com, 2026-09-22. The whole entry is on Vidu, and the column it sits in is on Named replacement. Same column, other entries: Hailuo AI, invideo AI.