Timing & transitions · Rendered draft
Caret · one-frame return and coupled reset
Study the source, inspect the editable build, then adapt the treatment to your own content.
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
A runnable draft is not a fidelity approval.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- Both actual Remotion replays now match the retained movies byte-for-byte and on all44 decoded RGB/YUV frames. The sole replay change was full Chrome instead of HeadlessShell at the same reported version. The source player uses a lossless ledger-restored 33/34ms clock; all22 image payloads are unchanged. Its full master is unavailable, and the outputs retain their documented CFR clock. The independent all-frame static comparison was tie/tie, not a moving-source win. The guide prerequisite defect is independently resolved. Actual still preparation and native Resolve export remain unexecuted. Independent recheck passes72 clock/integrity checks. The22 frame starts have two agreeing retained records; the9.509s exclusive end is supplied by the guide only, not independently recovered from a master.
- The existing package is retained unchanged. Local checks verify its bytes, archive, media, and route; no new fidelity approval is asserted.