GateTrue

What each generator documents about marking its output

Frame-rate change: resampling a clip through time

A frame-rate change alters how many frames a second a clip carries, which resamples the picture through time rather than across the frame. It is named in one robustness claim in this register. As of 2026-09-22.

Three axes a transformation can work alongCropping and scaling act across a frame. Compression acts within one. A frame-rate change acts between frames, blending or discarding them, which reaches a signal distributed over time in a way spatial operations do not.Acting on spaceActing on timeOperationsCropping, scaling, filteringFrame-rate changes, retimingWhat is at riskA mark in a region of the frameA signal distributed across framesHow often it happensWhenever a shot is recomposedWhenever a timeline normalises cadenceNamed in this registerCropping and filters, onceChanged frame rates, onceNo generator page names any transformation at all
Fig. 1 Its presence in a robustness list suggests the signal it protects has a temporal component.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termFrame-rate change
What it namesChanging how many frames a second a clip carries
What it is notChanging the duration, which retimes the content
Where the register uses itOne published robustness claim

Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.

1A transformation that works along a different axis

Cropping and scaling operate across a frame; compression operates within one. A frame-rate change operates between frames, blending or discarding them to fit a new cadence. A signal distributed over time rather than over area is exposed to it in a way the other operations do not reach.

That is why it appears in a robustness list at all. A scheme that only had to survive spatial operations would not need to mention it, and the fact that one is named suggests the signal has a temporal component.

2Why it happens so often

Generated clips arrive at whatever cadence a model produces. Editing timelines run at their own, platforms normalise on upload, and slow-motion or speed-ramping in an edit changes it again. A delivered short-form video has usually had its cadence rewritten at least once.

So this is not an exotic threat. It is an ordinary consequence of putting generated material into a real edit, which is what makes its presence in a robustness list informative about what the scheme expects to encounter.

3What the register records

The vendor's wording and nothing more: designed to stand up to changed frame rates, in a list with cropping, added filters and lossy compression. No measurement, no threshold, and no statement about what happens beyond the designed range.

No generator page in this register names a single transformation. That material exists only on the pages of the organisation that publishes the scheme, which is why the scheme is recorded as a separate entry from the generators that name it.

Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the machine-readable column, what survives an export. Nearby terms: composite step, intermediate clip, deliverable.