Logging what went into a generated clip
Grants and disclaimers address the output. The material that brings somebody else's rights into a clip arrives at the input end, and on some documents the prompt text counts as an input too. As of 2026-09-12.
| Entry | What it is for |
|---|---|
| Files supplied, with their source | Answering where a frame came from |
| Prompt text as sent | Some documents condition a grant on it |
| Reference images and their permissions | Consent and likeness questions |
| Which model and version produced it | Matching the clip to the terms that applied |
Inclusion rule. Entries that cannot be recovered from a finished file and that a rights question is likely to ask for. Order. From the entry most often kept to the one almost nobody keeps.
1Almost nobody logs prompts, and some documents care
Where a permission holds provided the inputs follow guidelines, the text typed into the box is an input. It is also the one part of the pipeline that leaves no trace once a session is closed.
Keeping it is a two-line change to a delivery script and it converts an unanswerable question into a lookup. The cost of not keeping it only appears once.
2Reference material is where consent lives
A photograph of a person, a client's footage, a competitor's frame: each arrives with rights attached and none of them is created by the generator. A log that lists files without their permissions has recorded the easy half.
Where a supplier refuses a category of input altogether, this becomes simpler rather than unnecessary. The log still shows that nothing of that kind went in, which is the evidence somebody will want.
3Model and version tie a clip to a document
Terms change, and so do models. A clip that records which model produced it can be matched to the licence that applied, which matters most on self-hosted pipelines where a checkpoint file carries its own conditions.
On hosted products the same entry answers a duller question well: whether a deliverable was made before or after a page was rewritten.
4Where the vendor statements are kept
The mechanics above apply to anyone. What a given vendor has committed to in writing is held on the register instead, each line with the plan page it came from and the date it was checked.
An explainer, not an entry in the register. Vendor statements are held, with their sources, on commercial use, and nothing on this page is legal advice. Related: Briefing a freelancer, Contract mismatch.
5From the making side
Alongside the terms behind “Input logs”, SceneMixer's guides describe the work itself this way:
The spoken lines and the end card follow your interface language across fifteen dialogue languages, with the cast and setting adapted to that market. The end card falls back to a language it can typeset when a script needs shaping or right-to-left layout.
SceneMixer, AI Ad Video Generator — “Which languages can the ad be in?” (read 2026-10-13)
You can recomposite with different end-card text, and in step-by-step mode you can reshoot individual segments. The finished file can also be downloaded and shared with a link.
SceneMixer, How to Make an Ad from One Photo — “Can I change the ad after it is finished?” (read 2026-10-13)