Motion fieldnotesOpenAI film study
Artifacts & handoffs · Rendered draft

Share dialog · pointer continuity and independent focus

Study the source, inspect the editable build, then adapt the treatment to your own content.

01 / OpenAI source 2:01.0–2:02.9 · Silent research excerpt
02 / Remotion draft Original illustrated content · Editable code

Use this example

  1. Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
  2. Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
  3. Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
  4. 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 match retained bytes and all114 RGB/YUV frames/clocks. The source-only kit includes128 SVGs and specific layer/frame controls, with122 portable checks and20 publication assertions. All57 retained native source crops and the next boundary are available; three full-frame witnesses verify the off-center crop. The source master was not freshly probed. The source comparison ties both variants after228 static movie-frame instances; no moving review occurred. Kit r02 repairs the missing-heading-measurement contract while reusing both existing movies unchanged. CPU assembly is nonidentical—0/114 exactRGB frames, maximum72 channel levels—with no acceptance threshold. Resolve remains guidance, not a tested native project. The independent r02 recheck closes SF-CONTENT-01:40 targeted,122 retained and32 independent tests pass, plus two original-reproducer repeats. All888 tracked inputs stay unchanged.
  • The existing package is retained unchanged. Local checks verify its bytes, archive, media, and route; no new fidelity approval is asserted.

Inspect the original verification record ↗