Frame interpolation, a stage after the model
Interpolation creates frames between generated ones to raise the playback rate. It is a separate model with its own cost and its own artefacts, and no release in this register includes it. As of 2026-09-22.
| Property | Changed |
|---|---|
| Playback rate | Yes |
| Clip duration | No |
| Frames generated by the video model | No |
| Artefacts | Yes, of a new kind |
Inclusion rule. Properties affected by an added interpolation stage. Properties that do not change are listed, because they are the ones people expect to. Order. From the property it exists to change to the side effect.
1It does not lengthen anything
Interpolation raises the rate at a fixed duration, so the clip is not longer; it is smoother. A reader who needs more seconds needs a different release or an assembly stage.
That distinction is why the term is filed under length rather than treated as a length value. It touches the column and adds nothing to it.
2Low published rates make it likely
Releases here stating fifteen or sixteen frames a second will usually pass through this stage before delivery, which adds runtime and a second set of failure modes to every clip.
The register records the published rate. What a pipeline does afterwards is a decision by whoever runs it, and it is not something a repository can be quoted on.
3Why it is outside the length column
The column records the rate the released weights produce. Raising that rate afterwards adds a second model with its own runtime and its own artefacts, and it does not make the clip any longer.
Two releases in the register publish rates low enough that this stage is likely before delivery. That is a pipeline consequence of a published value rather than a value of its own.
A reading note, not an entry: no vendor value appears on this page. Where the register records this term for a particular release, it is on the length column and on that family's own page. Nearby terms: Temporal drift, Sequence packing.