A reverse prompt can describe how slowly an action appears in the supplied video, but the image alone may not reveal whether it was filmed at high frame rate or performed slowly. Use the source's playback timeline for the recreation. Treat capture speed, shutter settings and later retiming as unknown unless reliable metadata or production information supports them.
Keep three clocks separate
The recorded event has a real-world duration. The exported clip has a playback duration. The generated shot has its own delivered duration. These can differ. A four-second shot of a falling ribbon does not establish that the physical ribbon fell for four seconds, or that the original camera recorded at a particular frame rate.
Adobe's frame-rate explainer distinguishes image cadence from exposure and discusses slowed playback. That background helps interpret motion; it is not a method for recovering camera metadata from appearance alone. Ask for the visible result you need rather than copying unsupported numbers into a prompt.
Describe the timing you can actually inspect
Break the supplied action into visible phases. For a person turning toward camera, these might be a still opening, the turn and a settled expression. Record approximate times on the exported source timeline. If a cut interrupts the turn, describe two shots rather than one continuous movement.
Playback reference: the subject remains still for approximately the first second, turns the head gradually over the next two seconds and holds a relaxed smile for the final second. Recreate that pacing in one continuous shot with a fixed camera. The original capture frame rate and any speed adjustment are unknown.
This brief is useful without a claim about how the source was filmed. Its timestamps are illustrative, not evidence from an uploaded clip. Replace them with the actual observed intervals before generating. For short or rapid gestures, check the original frame by frame rather than relying on an analysis summary alone.
Avoid impossible combinations
Do not request an entire walk, greeting, embrace and departure inside a duration that only fits a small gesture. Saying slow motion does not create more narrative time. If the recreation needs several actions, split them or change the intended total duration deliberately.
Also inspect secondary movement. Fabric, hair and falling objects can reveal a mismatch between the requested pacing and the scene. A slowly turning face with violently fluttering hair may not match a calm reference. Describe important environmental motion separately from the person and the camera.
A timing verification sheet
- Record the source file's playback length.
- Note visible shot boundaries and whether motion continues across them.
- Mark the beginning, main action and settled end of each shot.
- Distinguish observed timing from inferred capture settings.
- Compare a generated candidate at ordinary playback speed.
- Check whether the final hold is usable for the next edit.
Keep the source and the annotated brief together. A later editor should know whether an interval was measured, estimated or chosen creatively. Do not silently stretch an event to fit a template and still label it an exact reconstruction.
Does a 60 fps file prove the scene is slow motion?
No. A delivery frame rate does not by itself explain the capture rate or playback transformation. It can be ordinary real-time footage, retimed material or a converted export.
Can I ask for the same apparent rhythm without knowing the camera?
Yes. Use Reverse Prompt to draft the visible timing and specify the desired pacing directly. Check the generated file and provider's supported settings instead of assuming the prompt can set arbitrary frame rates.