Two numbered generations, two unmentioned back catalogues
Both entries promote a numbered house generation, and neither says whether the versions before it remain selectable. A number implies earlier ones existed, so in both cases the page raises a question it does not answer, and a production already working on one cannot plan from any public page. From 2 source pages, read 2026-09-22; no maker pays to be listed.
| On this point | PixVerse | Vidu |
|---|---|---|
| Current line named | One house version, beside licensed models | A current generation and a real-time line |
| Earlier generations | Not stated on the page read | Not addressed on the page read |
| Licensed models present | Yes, several from other makers | No; both lines are this maker's |
| What the second line is | A licensed model, not a fallback | A speed variant, not a fallback |
| Is a successor named | Nothing names one | Neither line is presented as one |
Inclusion rule. Both cells on a row come from the entry's own public pages. A version reachable in the product but unnamed publicly does not fill a cell. Order. The current line first, then what is not said about earlier ones.
1The same gap arrived by different routes
One entry's page is crowded with licensed models and still silent about its own predecessor. The other names only its own two lines and is silent in the same way. So the absence is not a side effect of a busy page.
Two entries reaching it independently suggests the question is simply not one these pages are written to answer. Neither page is a lifecycle document, and neither claims to be.
2Neither second line is a cushion
On one page the second line is a licensed model from another maker, which carries somebody else's schedule. On the other it is a speed variant of the same generation. In neither case is there an older version to finish a season on.
Three entries elsewhere in this register do keep a previous generation on the price list. The arrangement exists in this market, so its absence here is a choice rather than a constraint.
3What a production can actually do
Record the version behind each delivered file while the page still names it, and archive the files. Neither page will warn anybody, and neither will confirm afterwards what was available when.
The ending early reading for one of the two explains why even after-the-fact detection is weak when a page lists a single version.
4The same question, put to a third entry
| On this point | SceneMixer | Source |
|---|---|---|
| When a tier is withdrawn | When a tier is withdrawn, text and image work falls back to the default tier and video to the tier the episode last used if it is still listed, otherwise the default; the price shown is the tier that will run | SceneMixer, withdrawn tier guide |
Inclusion rule. SceneMixer's own statements that bear on the column this pair was chosen for. Order. The statement closest to the column first.
All of its readings are on the SceneMixer entry.
- Whether V5 and earlier remain selectableNot stated (as of 2026-09-12)not stated
5Sources
Both readings come from the pages the entries publish themselves: PixVerse and Vidu, read 2026-09-22. The column being compared is Named replacement. Other pairs: Bedrock and Wan-AI, Hailuo AI and Pika.