Logging: how each behaviour was read

Each editor's official English pages were read on one day: tool pages, help centres, FAQs, guides and plan notes. Every statement about building, redoing or replacing units was logged with its page, the date and a short quote, then given one reading from a fixed list per behaviour. As of 2026-09-25.

Fig. 1 Every reading keeps the page it came from.

1Who is on the register

A tool is registered when its pages describe building one episode, film or story video out of several generated units inside the product, and say something about at least two of the five behaviours after the unit: redo charge, versions, single-unit redo, transitions and partial replacement. Single-clip generators do not qualify, however good their clips.

2Basis, not amount

The redo reading records whether a second generation is charged, and on what basis, never a price. A vendor that says every generation reaching the model is charged has told you a redo is charged; a vendor that refunds failed runs has said something narrower.

3Readings in use

Fig. 2 Each bar is one behaviour and reading; its length is the number of editors whose pages give that reading.

Every reading given, by behaviour, with the number of editors carrying it.
Behaviour: reading	Editors
Unit: Takes	1
Unit: Scenes	11
Unit: Shots	10
Unit: Clips	4
Unit: Segments	1
Unit: Beats	1
Redo charge: Charged again	11
Redo charge: No-credit mode	1
Redo charge: Failed runs refunded	2
Redo charge: None said	14
Versions: History kept	8
Versions: Pick from a set	6
Versions: Undo history	1
Versions: None said	13
One-unit redo: One unit at a time	24
One-unit redo: None said	4
Transitions: User picks	4
Transitions: Applied by the tool	8
Transitions: First and last frames	3
Transitions: Joined in order	2
Transitions: Suggested, user decides	1
Transitions: In another editor	1
Transitions: None said	9
Replace in cut: Timeline	10
Replace in cut: Recomposite	7
Replace in cut: By request, no editor	4
Replace in cut: None said	7

Inclusion rule. Readings actually given on the register; unused ones are not listed. Order. Behaviours in register order.

4None said

A behaviour the pages were read for and do not mention is logged as not said. It is not a verdict that the tool lacks the behaviour, only that its own pages do not describe it.

The full log is on the data page.

5Inside a generator's episode

The episode pipeline SceneMixer documents has its own answer to “Logging”; two lines from its pages:

Paste a scene or a short script and SceneMixer gives you a storyboard — numbered shots with framing and seconds — and then a moving version of each segment, which you can join into a rough cut of the scene.
SceneMixer, Using SceneMixer for Previs and Animatics Before a Live-Action Shoot (read 2026-10-13)

SceneMixer turns a novel into a watchable short-drama series in one pipeline: upload the novel (Chinese or English) → AI extracts characters, scenes, and an episode-by-episode structure → generates consistent character and scene art → writes storyboard scripts → renders video segment by segment (16:9 by default, 9:16 in one setting) → composites full episodes.
SceneMixer, Turn a Novel into a Video Series with AI (read 2026-10-13)

How the register is kept. The tables, counts and rankings on this site are computed by script from the register, and every figure links to the page it was read from, with the words quoted. No maker pays to be listed or to change a place, and each ranking states its rule, written before the places were computed. Entries are not edited at a maker's request: a figure that is out of date is fixed on the maker's own page and picked up when the pages are next read, at least every three months.