← Recipe index / Prove
R09_reading_hold / 120 frames / 30 fps
Protect a complete-result reading hold
Give the audience an interval in which the evidence is complete, stable and large enough to read. A container animation or unfinished output is not a reading hold.
Source evidence
Use ChatGPT Work to build custom creative tools ↗ · official OpenAI channel · published 2026-09-04
Inspected source window 133–145 s. Consecutive subset 133.5–134.5 s: 60 frames. A longer excerpt is not an every-frame edit list.
Source evidence, not a Resolve recreation. Silent excerpt; the player counter starts at zero.
Observed mechanic and limits
The native subset is a result hold. Later scrolling and the context cut are outside that subset.
A completed page hero remains readable in a desktop browser.
Hero holds, then the broader excerpt tours two sections before returning to the editor.
Completed result → reading → result tour → editor context.
The 133.5–134.5 s consecutive subset is a hero hold; this is not a comprehension measurement.
Complete result at hold start
Hero remains framed
No page scroll in this hold
Last inspected hold frame, not the later cut
Construct in Resolve
Documentation-checked; application-unverified. Use the environment, frame-counting, geometry and font setup first. Timeline timecode starts at 01:00:00:00. Tables use zero-based recipe-local frames and half-open intervals. Clip-local frame equals recipe frame minus that clip’s In; add any Fusion composition offset separately. Values are chosen implementation defaults.
| Track | Asset / native tool | In (inclusive) | Out (exclusive) |
|---|---|---|---|
| V1 | shell.png | 0 | 120 |
| V2 | result.png | 0 | 120 |
- Place shell.png and result.png with matching start and 120-frame duration. Inspector: Zoom 1, Position 0,0, Opacity 100%, Composite Mode Normal. No keyframes on either clip.
- Place a timeline marker at frame 0 named READ_START and one at the next cut named READ_END. Watch at actual meeting-view size, not only full-screen.
- If continuing result-reveal, use its final composite state without a framing reset. Treat this recipe’s 120 frames as additional hold only if the assembly explicitly calls for it.
Inspector and keyframes
| Control | Recipe-local frames | Value and interpolation |
|---|---|---|
| All layers | 0–119 | Unchanging framing; no transition; no cursor movement |
Hold, handles and retiming
120 frames (4 s) are chosen for the short neutral fixture. No empirical human-reading threshold is claimed. Dense evidence needs a longer timed-recording pause or a simpler crop.
Stills/generators need no temporal handles. For real captures reserve 15 source-time frames before and after each used interval at a 30 fps capture rate; keep those handles outside the edit. No dissolve or optical-flow handles are needed here.
100% speed. No Optical Flow, Speed Warp, frame interpolation or simulated product wait.
Replace assets / change duration
Replace the content and test the smallest relevant labels at intended playback size. Extend this clip at 100% speed. For a real capture use a genuine stable interval; do not freeze a live clock or fake a finished app state without disclosure.
Compare the mechanic, not the branding
The cited native source subset verifies a short hero hold, not a universal four-second reading rule. The wider excerpt scrolls and later changes context; those later boundaries are not frame-exact here.
No application render or editable project has been produced. Timing, framing, motion, alpha, continuity and readability comparisons remain incomplete. A source clip or fixture PNG is not that verification.
Construction reference: official Resolve 21 manual, p. 967, p. 1246. Controls still need confirmation in the installed edition/version.
All recipe specifications · Original preparation kit · Import/export and verification procedure