EpisodeReel

Serial work: what each tool documents about continuity

Handing the cast to the model, against making an artefact for it

One page attributes character consistency to the video model it runs on. The other states that a full-body reference sheet is generated per character while the script is analysed, with crops injected into every segment. The question both answer is who owns the problem. As of 2026-09-16.

Where the consistency problem is said to belongOne page hands the question to the video model underneath it; the other answers it with an artefact the product makes while the script is read. The fork decides what remains when the layer below moves.Who owns the cast?The model underneathA supplier with no contractA version change can alter a face, and nobody owes awarning.The product itselfA file a buyer can openThe reference outlives whatever generator sits beneathit.Both positions are honest; only one leaves something behind
Fig. 1 The branch is not about picture quality; it is about who owes the production an answer.
Medeo and SceneMixer on the cross-episode cast, point by point. Read 2026-09-12 and 2026-09-16.
Point at issueMedeoSceneMixer
Where the answer livesWith the underlying video modelWith an artefact the product makes
What a buyer can inspectNothing named on the pageA sheet, and which segments received crops
What a model update could changeThe cast, without noticeThe picture, but not the reference

Inclusion rule. One cell is a claim attributed elsewhere and one is a documented mechanism. The contrast is kept because both are honest positions about a problem neither page measures. Order. The attributed answer first, then the documented one.

1Attribution upward is candid and it moves the risk

Saying the model does it avoids claiming credit the product has not earned, which is more than several pages on this file manage. It also puts the answer with a supplier the buyer has no contract with and no release notes from.

For a season assembled over weeks that is a scheduling exposure. A model updated mid-run can change a face, and neither the product page nor the model vendor owes the production a warning.

2An artefact made by the product survives the layer underneath it

A reference sheet is a file. If the generator beneath it changes, the sheet still says what the character looks like, and the production still has something to compare a bad shot against.

That is not a claim about picture quality. It is a claim about what remains when something below you moves, and it is the part of continuity that a page can actually publish.

3Both pages are concrete somewhere else

The attributing page describes one story broken into numbered parts with recap clips and teasers, which is specific and useful. The other publishes a rate on the composite step. Vagueness here is not carelessness; it is a decision about which problems each product has taken on.

Reading the cells together is the point of a register. A page can be worth trusting on one column and silent by design on another.

4The wording both sides published

  • Cross-episode cast
    Character consistency is attributed to the underlying video model rather than to the productattributed to a modelMedeo, short drama page / recorded 2026-09-16
  • Cross-episode cast
    A full-body reference sheet is generated per character at analysis time, and its face and body crops are injected into every segment featuring that charactera stated mechanismSceneMixer, how-to guide / recorded 2026-09-12

5Sources

Read from the short drama page at medeo.app and the published how-to guide at scenemixer.com, checked 2026-09-16 and 2026-09-12 respectively. The full column is on cross-episode cast; the single readings behind this contrast are Medeo and SceneMixer. Other contrasts filed here: Kling AI and Arcloop, Genra and character.app, OpenArt and Vidu.