Fade the composer out, fade a result card in, then jump to macro and pan across the card to its button

What the source does

The finished composer holds for a few frames (master 346-350), fades to about 40% by master 354 and is gone by 358 (local 12), leaving pure white. A wide schedule card (clock icon, title, 'Hourly', Open button) fades in at the same spot between master 358 and 366 (local 12-20). At master 370 (local 24) there is a hard jump to a macro view of the card's left end at roughly 3x. The camera then pans right across the card, slowly at first (icon still visible at 386) and faster from 390, passing the title, until the Open button slides in from the right edge at 426 and settles near the right third by 434 (local 88).

Cross-fade between two UI states followed by a jump cut to macro and a lateral camera pan that reads the card left to right and lands on its action.

Phase notes

1. Frame 0 — Finished composer holds
2. Frame 4 — Composer fades out
3. Frame 12 — Blank; schedule card fades in
4. Frame 24 — Jump cut to macro on the card icon
5. Frame 40 — Pan accelerates along the title
6. Frame 82 — Open button enters and settles

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.

Recorded limits

• Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.
• Both variants rerendered from the packaged text renderer to repair a prior code/preview mismatch.

Inspect the original verification record ↗