Four questions before a season depends on it
Four questions, one afternoon. Is the engine named on the page you pay from. Is a notice period published anywhere. Is an older generation still purchasable. Could the season be finished if the engine disappeared in ninety days. The last one changes decisions. As of 2026-09-12.
| Question | What a bad answer means |
|---|---|
| Is the engine named where you pay | No announcement can ever be matched to your bill |
| Is a notice period published | The runway is whatever the seller feels like |
| Is an older generation purchasable | There is nothing to finish a season on |
| Could you finish in ninety days | The plan depends on a date nobody published |
Inclusion rule. Questions worth answering before a serial production commits to one engine. Order. In the order that narrows a decision fastest.
1Naming is the precondition for everything else
If the page you pay from does not say which engine a tier runs, no announcement anywhere can be matched to your work. Every other question becomes unanswerable, and a change arrives as output that looks different.
Two entries in this register name a model and version beside a rate. Most publish a tier name and leave the engine to be inferred.
2A period is rarer than it should be
No application in this register publishes one. Three hosting platforms do, and none of them is the party a production buys from, so the commitment exists and does not reach the person it would help.
Where no period exists, the substitute is bookkeeping rather than vigilance. There is no page to watch and no notice to wait for.
3An older generation on sale is worth more than it looks
A previous version still purchasable turns an emergency into a scheduled migration and lets a block in progress finish as it started. Four entries here offer that today.
None of them says how long. It is a fact about this month rather than a commitment, and it is still the most useful arrangement any application in this register offers.
4The ninety-day question is the one that changes plans
Most teams have never asked whether a production in flight could be finished if its engine vanished in three months. Asking it once usually changes something: a record, an archive, or which tier the season starts on.
It is also the question this register exists to make answerable, entry by entry, from pages anybody can open. The entry list is where it starts.
5Where each vendor's own wording lives
None of the above is a date. Announced end dates, and the apps still carrying the models they apply to, are kept on the calendar with the announcement each one came from.
- Every entry tracked here — what each one names, and what it publishes about the end
- The columns — the four questions above, asked of every entry in the register
Guidance rather than a dated entry. No line here is a vendor statement, and none should be read as an announcement. The sourced material is on the calendar. Related: Pinning a version, After a swap.
6A pipeline across model versions
Model end dates touch “Before committing a season”; SceneMixer's guides describe how its pipeline treats the models it runs:
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)
Wan 3.0 is Alibaba Cloud's video generation model on the Model Studio platform, called through an asynchronous submit-then-poll API, in two tiers: the standard wan3.0-video and the faster wan3.0-video-prime.
SceneMixer, Wan 3.0 for AI Short Drama (2026): Parameters, Reference Limits, Moderation Rules and the 30-Second Take (read 2026-10-13)