Skip to content

Comparison Collision V05

0.0s

Previews are illustrative demonstrations of the technique — not your footage. Your real edit is produced later by Claude Code.

V05 · Visual Beats · intermediate · 1.5–6s

Two option cards fly in from opposite edges, collide in the middle with a small impact, and settle side by side under a VS divider for comparison.

Option A enters from one side, option B from the other; they meet at center with a short impact and bounce apart into an aligned two-column layout with a VS marker between them. The physical collision dramatises the contrast, and the settled alignment makes the comparison easy to scan — same size, same baseline, each with its own label and colour.

Try the parameters

Best used for

  • — Tool or product comparisons
  • — Myth vs fact
  • — Old way vs new way
  • — Two strategies head to head

Assets

  • ● Source video required
  • ○ Product image optional
  • ○ Screenshots optional
  • ○ Transcript with timing optional

Pairs well with

If assets are missing

If the script only names one option, use V03 Keyword Spotlight instead. Never add a competitor or a claim about either option that the speaker did not make.

Accessibility

Distinguish the two sides by position and label, not colour alone. Keep the impact shake ≤ 4 frames; disable it for motion-sensitive audiences.

Individual prompt

updates with the parameters above
# CES style instruction — V05 Comparison Collision

You are an experienced motion designer and video editor working in Claude Code. Apply the **V05 Comparison Collision** technique to the supplied footage as specified below.

**B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English

**Visual Beats** — Option A enters from one side, option B from the other; they meet at center with a short impact and bounce apart into an aligned two-column layout with a VS marker between them. The physical collision dramatises the contrast, and the settled alignment makes the comparison easy to scan — same size, same baseline, each with its own label and colour.

### V05 Comparison Collision

- **When:** ≈ 00:00.00 → 00:03.00 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V2+ (overlay above the picture)
- **What it does:** Two option cards fly in from opposite edges, collide in the middle with a small impact, and settle side by side under a VS divider for comparison.
- **Parameters:** Option A: (not set); Option B: (not set); Collision: Slam + bounce apart; Settled layout: Side by side; Option A colour: #FF7A6B; Option B colour: #779CFF; Impact shake: on
- **Steps:**
  1. Option labels are not fully set. Use the two things the speaker contrasts, named in their own words from the transcript; any attributes shown under each must also come from the script or supplied assets — never invented pros/cons.
  2. Build two equal cards (42% wide × 34% tall each, 3% radius) from 00:00.00 to 00:03.00. If product images or screenshots are supplied, place them in the cards; otherwise use the label only.
  3. Animate A from off-frame left and B from off-frame right, accelerating (ease-in) to meet at center in 11 frames, then rebound apart to their settled columns over 12 frames with a back-out curve with slight overshoot (cubic-bezier(0.34, 1.56, 0.64, 1)).
  4. On contact: a 4-frame positional shake of the card layer (≤ 1% of frame width) and a brief white flash line along the contact edge (2 frames, 60%).
  5. Once settled, pop a "VS" badge (Space Grotesk black, ≈ 7% of frame width) into the gap with scale 0 → 1.1 → 1. Hold the aligned comparison ≥ 1.5s (longer while the speaker compares), then slide both cards out.
- **Assets:** Source video (⚠ MISSING) · optional: Product image, Screenshots, Transcript with timing
- **Fallback:** If the script only names one option, use V03 Keyword Spotlight instead. Never add a competitor or a claim about either option that the speaker did not make.

**G. Asset integrity and restrictions:**
- Do not create or present invented testimonials, comments, quotes, reviews or endorsements.
- Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data.
- Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative.
- Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead.

**I. Quality verification:**
- Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly.
- Check the output frame rate and that the duration is within ±0.5 s of the target.
- Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame).
- Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations.
- Confirm the output file exists and plays — never claim a render is complete without an actual output file.
- Report any missing asset or unimplemented effect explicitly.

More visual beats styles

Insert a beat whenever the script changes idea, lists items or lands a key line.

Your recipe starts here.

Add a style to begin building.