Type a numbered list into a composer while the camera pushes in and older lines scroll out of the box
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
A grey composer with a row of tool glyphs sits mid-frame; 'An Im' is typing with a caret (f0). The first line completes by ~f15, '1.' starts ~f30 and by ~f45 the camera has pushed in so the composer fills the frame. Lines 2, 3 and 4 type on at ~f45–62, ~f70–90 and ~f96–115; as each new line starts, the earlier lines scroll upward out of the visible text area so roughly three lines stay in view above the glyph row.
A caret type-on of a multi-line list inside a fixed-height composer, with a slow camera push-in and stepped upward scrolling of completed lines.
Phase notes
- Frame 0 — Header line typing, wide framing
- Frame 16 — Camera push-in begins
- Frame 30 — Item 1 types
- Frame 50 — Push-in lands; item 2 types
- Frame 70 — Lines scroll up one step; item 3
- Frame 96 — Second scroll step; item 4
- Frame 119 — Hold
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.
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
- Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.
- Both variants rerendered after correcting unrevealed whitespace and the caret’s active line.