A crowded plan table against two named lines
One of these entries puts two house generations and licensed models from several makers on a single plan table. The other names a current generation and a real-time line. Neither marks any row as leaving, and neither says what the route off any of them would be. From 2 source pages, read 2026-09-22; no maker pays to be listed.
| On this point | Luma | Vidu |
|---|---|---|
| Rows on the published menu | Two house generations plus licensed models | Two lines, split by speed |
| Whose schedules apply | This company's and several others' | This company's only |
| Is an earlier generation named | Yes, a second house line | Not addressed on the page read |
| Is the licensed half marked | Only in the plan wording | Not applicable |
| Is a successor named | No row names one | Neither line is one |
Inclusion rule. Both cells on a row come from the entry's own public pages. A model reachable in the product but unnamed publicly does not fill a cell. Order. Menu size first, then whose schedules are involved.
1A long menu is more exposure and more evidence
Listing several makers means several schedules a production is subject to, and it also means a page detailed enough to notice a change on. A short menu inverts both: fewer schedules, and almost nothing to compare across two readings.
So the crowded table is riskier and more auditable. Neither property is a judgement about the products, and both matter to somebody trying to watch a model line.
2Two house lines against a speed split
One entry's second house line is an earlier generation, which gives a production somewhere to stand. The other entry's second line is a real-time model, which is a different capability rather than a fallback.
That distinction decides whether a menu of two has a cushion in it. The reading for the shorter menu sets out why a capability split is not a version cushion.
3Neither marks the licensed rows
On the longer menu the licensed lines sit in the same type as the house ones, with only the plan wording acknowledging the mixture. On the shorter menu there is nothing licensed to mark.
A reader therefore cannot tell, on the crowded page, which rows fail on somebody else's decision. The two unmarked tables read against each other show how common that arrangement is.
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 Q1 and Q2 are still offeredNot stated (as of 2026-09-12)not stated
5Sources
Both readings come from the pages the entries publish themselves: Luma and Vidu, read 2026-09-22. The column being compared is Named replacement. Other pairs: fal and SceneMixer, fal and Pika.