LLMSwaps

Announced end dates for video models, and which apps still carry them

Why SceneMixer publishes no notice period either

SceneMixer publishes no notice period. What it publishes instead is specificity: each price tier names its model and version, so a reader comparing two readings of the same page can see a swap after the fact. That is detection rather than warning, and the two are not interchangeable. From 2 source pages, read 2026-09-12 to 2026-10-26; no maker pays to be listed.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryWhat SceneMixer publishesWhat SceneMixerpublishesWhat that leaves openWhat that leavesopenIs warning promised before a changeIs warning promised before a change — What SceneMixer publishes: Nothing published about noticeIs warning promised before a change — What that leaves open: Work in progress falls back to a listed tier, as a separate guide statesCan a change be detected afterwardsCan a change be detected afterwards — What SceneMixer publishes: Yes, each tier names a model and a versionCan a change be detected afterwards — What that leaves open: Detection needs two dated readings to workWhich tier moves the most workWhich tier moves the most work — What SceneMixer publishes: The default is a named 480P lineWhich tier moves the most work — What that leaves open: A change there reaches untouched projectsIs the naming itself a commitmentIs the naming itself a commitment — What SceneMixer publishes: No statement promises the naming continuesIs the naming itself a commitment — What that leaves open: A page can stop naming models at any point
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the price list settles about a tier changing model, and what it does not. Recorded 2026-09-22.
What the page is askedWhat SceneMixer publishesWhat that leaves open
Is warning promised before a changeNothing published about noticeWork in progress falls back to a listed tier, as a separate guide states
Can a change be detected afterwardsYes, each tier names a model and a versionDetection needs two dated readings to work
Which tier moves the most workThe default is a named 480P lineA change there reaches untouched projects
Is the naming itself a commitmentNo statement promises the naming continuesA page can stop naming models at any point

Inclusion rule. Read from the public price list. A tier is counted as naming a model only where the model and its version appear beside the rate, not where a house label implies one. Order. What is promised first, then what can be observed instead.

1Detection and warning are different products

Every entry in this column publishes one or the other and nobody publishes both. A warning lets a production act before the change; detection lets it explain the change afterwards. Only the first prevents a season splitting across two looks.

Detection is still worth recording, because the alternative is an output difference nobody can attribute. A team that can point at a page and a date has a problem; a team that cannot has an argument about whether anything happened.

Warning prevents a split; detection only explains oneA notice period lets a production act before the model changes. A named tier and version lets it prove afterwards that the change happened. This entry publishes the second and not the first, and the two are not substitutes for each other.WarningDetectionArrivesBefore the changeAfter it, on a second readingLets youFinish on the old modelSay which model made which fileNeedsA published periodA named model and versionPublished hereNothingModel and version beside each rateWhy an empty cell here sits next to an unusually specific page
Fig. 2 Detection still beats an unattributable difference in output, which is what an unnamed tier leaves a reader with.

2Naming the version is what makes the reading possible

A tier called fast cannot be compared against anything. A tier that prints a model name and a version number can be checked against the maker's own notices, which is how a date published one layer up ever reaches the person paying for seconds.

That is the link the register is built to expose. The maker publishes a date, the app names the model, and a reader who has both can tell whether the date applies to the tier they are buying.

3The default is where the exposure concentrates

A tier nobody selects is where most delivered work comes from, so a change to the starting line reaches more finished material than a change to any other row. The register keeps that in the default tier column for that reason.

Nothing here promises the default stays put. What happens to a project started on it is described in a guide on withdrawn tiers: the episode keeps the tier it last used while that tier is listed, otherwise the default, at the price shown. The notice itself is still unpublished, which is why this reading is recorded as empty.

  • Notice before a tier changes
    No notice period published (as of 2026-09-12)nothing publishedSceneMixer, price list / recorded 2026-09-12
  • Models carried
    Wan 3.0 at 480P, 720P and 1080P; Seedance 2.5 Pro, Lite and 480P; Seedance 2.0, Fast and 480P; MiniMax H3 and H3 Fast; Kling 4.0 and Kling 4.0 Flashnamed per tierSceneMixer, price list / since 2026-10-15 / checked 2026-10-26
  • Default tier
    Wan 3.0 at 480Pwhat a new project getsSceneMixer, price list / recorded 2026-09-12
  • Work in progress when a tier goes
    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 runSceneMixer, withdrawn tier guide / recorded 2026-10-13

4Sources

Read from the price list on scenemixer.com, 2026-09-22. The whole entry is on SceneMixer, and the column it sits in is on Notice period. Same column, other entries: Runway, Sora.