“Make the title slower” can describe at least three different changes: delay its entrance, lengthen the entrance animation, or hold the finished title longer. An agent can implement any of them correctly and still deliver the wrong cut.
Specify the Version first. A note at 00:12 in V1 may point at a different shot in V2 after an earlier cut changes length. Keep the original Version and the marked frame together; use a section when the request concerns motion rather than a single image.
Here is an illustrative instruction for a 30 fps video. It is an example, not a completed revision:
Where: V1, frames 360–419, title entrance.
Change: Increase the entrance animation from 12 to 20 frames.
Keep: The entrance start at frame 360, the final position, typography, audio and the next cut at frame 420.
Check: At frame 380 the title has reached its final position. Compare the same section in V1 and V2. Check the next cut and listen to the transition before approving.
The keep-list is as useful as the change. It gives the agent a boundary: revise one entrance without quietly retiming the whole scene. If the request cannot fit inside those constraints, ask which constraint may move.
After the agent produces V2, inspect both the requested change and what was meant to stay. A diff helps locate changes; it cannot decide whether the pacing feels right. “Fixed” records what the agent did. A person checking the result is a separate action.
Lampo puts that direction on the cut: frame-specific notes and drawings, agent-readable context, Versions to compare, and a person’s approval. Watch the 90-second launch film. The tour is a designed product showcase, not a live agent-run recording.
Want to use this on your own cut? Every new account on Lampo Cloud starts with 14 days of Team, free, with no card.
Drafted with a Lampo marketing AI agent from the product documentation. The example is illustrative.