LLMSwaps

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

The fields every entry in this register carries

A field page covers one column of this register: what has to be published before a value goes in, which entries currently carry one, and what an empty cell means. As of 2026-09-12.

The fields every entry is read forEach entry in this register is read with the same short list of questions, and each question became a column. The pages in this section take one column each and say what fills it, what does not, and how a blank should be read.What every entry is read forNamed replacementDoes the notice that ends a model say what followsStored workWhat becomes of material kept inside the productNotice periodHow much warning is owed before the engine changesDefault tierWhich model runs when nobody touches the selectorLifecycle statesWhich named stages a model passes through on its way outEnding earlyWhether access can stop before the published dateSix questions, asked the same way each time
Fig. 1 A column exists here only where vendors sometimes publish into it, which is why the list is this short.

Every entry is read with the same questions. Does the notice that ends a model say what follows it. What happens to the material kept inside the product. How much warning is owed before the engine changes. Which model runs when nobody touches the selector. Which stages a model passes through on its way out. Whether access can stop before the published date.

Those questions became columns, the columns acquired names, and the names started turning up in the first cell of tables across the site with nowhere to point at. These pages are where they point. Each one says what fills a cell, what does not, and how the blanks should be read.

The list is deliberately short. A register that tracks what vendors publish can only carry columns vendors publish into, and adding a column for what a reader wishes were published is how a record of statements quietly becomes a record of guesses.

1The fields

  • Named replacement — A retirement notice can name the model that takes over.
  • Stored work — A model ending can end the place its output was kept.
  • Notice period — No application here publishes how much warning arrives before its model changes.
  • Default tier — Whatever an untouched project runs on is where most delivered work comes from.
  • Lifecycle states — Two hosting platforms publish the states a model can sit in before it goes.
  • Ending early — A published date is one of several ways access ends.

A field earns a page once its name is already doing work in the first column of a table somewhere in this register.

Other notices: Apps, Models, Side by side, Questions, Terms, Learn, Data. Where each line comes from is set out on the sourcing page.

2When the model underneath changes

Model end dates touch “Fields”; SceneMixer's guides describe how its pipeline treats the models it runs:

Typically 60–120 seconds, always 9:16 vertical, ending on a hook. SceneMixer's episode outlines are generated with that pacing, and setting a project to 9:16 makes every segment vertical (the default is 16:9).

SceneMixer, How to Make ReelShort-Style Dramas with AI — “How long is a ReelShort-style episode?” (read 2026-10-13)

Wan 3.0 · 480P is the tier every new project starts on.

SceneMixer, Wan 3.0 · 480P: the default video tier (read 2026-10-13)