Duration — ×720 · 16:9 landscape HyperFrames Remotion + HyperFrames (comparison)
Run log
ModelClaude (agent build)
Renderer / stackRemotion + HyperFrames (comparison)
Iterations to final2
Render time62s + 28.2s (two halves, final renders)
Format×720 · 16:9 landscape
Published2026-10-25
What broke (and the fix)
- Nothing broke. Both halves were still-checked separately (30% / 70% / final) and the combined 16s film was frame-checked at 4s and 12s — REMOTION and HYPERFRAMES labels both burned in and legible, no overlap.
Original prompt Tested
Same prompt, two renderers — Remotion vs HyperFrames (tested) — Remotion + HyperFrames (one brief, two stacks)
by MotionPrompts (own run)
Prompt
Banned list —Beat grid —Build method —Self-review —
<direction>
An 8-second landscape showreel for a showreel, built TWICE from this one prompt — once in Remotion, once in HyperFrames. Kicker: ONE PROMPT — ONE SHOWREEL. Headline MAKE IT MOVE. slams in with a hard settle. Three chips land in stagger: HOOK / BUILD / PAYOFF. End line: TESTED, NOT CLAIMED. Each half carries its renderer name burned into a corner pill in accent #ff5c1a (REMOTION / HYPERFRAMES). House style: near-black #0a0a0a background, white type, ONE orange accent #ff5c1a, Arial/Helvetica bold, no webfonts. Fictional brands/data only.
Banned: glows, gradients, particle bursts, bouncy cartoon easing, and any claim that one renderer is "better" without evidence in the film.
</direction>
<structure>
0–0.5s: kicker + label in. 0.3–1.2s: headline slams. 1.2–2.5s: chips stagger in. 4.6s: end line holds to 8s. The two halves are concatenated as sequential halves with ffmpeg — Remotion first, HyperFrames second.
</structure>
<build>
Two independent builds, no shared code: a Remotion + React component (springs for the headline, staggered springs for the chips) and a HyperFrames + GSAP composition (timeline tweens), both 1280x720 landscape, 30fps.
</build>
<gotchas>
- Keep the two halves' geometry identical (same headline size, same chip positions) or the comparison compares layouts, not renderers.
- Burn the renderer label INTO each half; a caption added later can be stripped, a burned label cannot.
</gotchas>
<methods>
Methods note: one prompt text, two independent builds — a Remotion + React component and a HyperFrames + GSAP composition — concatenated as sequential halves with ffmpeg. No code is shared between the halves; the comparison is of the two renderers' output for the same brief. Final render times: Remotion ~62s (wall time, tool log) + HyperFrames 28.2s. Iterations: 1 per half, 2 total.
</methods>
Before you finish: step through the timeline at five points and fix anything that overlaps, clips the frame, or drifts off the beat grid.
Use this prompt
Honest verdict: both halves land the same beats, and the visible difference is settle character, not capability — Remotion's springs give the headline a softer settle, HyperFrames' timeline gives the chips a harder, more metronomic stagger. For this 8-second showreel, pick the stack your team already ships in. Render times: Remotion ~62s (wall time, tool log) + HyperFrames 28.2s; 1 iteration per half.
