How to show a moment again in slow motion without it reading as a mistake
Tell Vizard Agent you want the moment twice — once at full speed and once slowed. It locates the action's exact frames in both versions, writes narration that explicitly introduces the replay so nobody thinks the video repeated itself, times the captions across the change of speed, and checks the finished render still contains both passes.
What is the short version?
Repetition is a strong device and an ambiguous one. Shown the same three seconds twice with nothing to explain it, a viewer's first thought is that something went wrong, and by the time they work it out the moment has gone.
- Go to Vizard Agent with the footage.
- Ask for the action at full speed, then slowed.
- Ask for narration that says the replay is a replay.
What do you need before you start?
The footage and, ideally, the moment shot at both speeds. Vizard Agent can slow a full-speed clip, but a source recorded in slow motion has frames that a slowed clip does not, and knowing which you have decides how far the replay can stretch.
- The footage. Both speeds if you have them.
- The moment. Named, not timecoded.
- How slow the replay should be. Half, quarter, held.
- Whether narration carries it. Usually it should.
- The target length. A replay doubles the beat.
What do you type into Vizard Agent?
Ask for the replay and the signposting together. The device only works when the audience is told, and if you ask only for the slow motion you will get a beautifully slowed shot that looks like a duplicate.
Prompt
Variants worth knowing:
- "Then again slowed down." Names the structure.
- "Explicitly introduces the replay." The signposting.
- "Confirm both passes are there." They get lost.
What does Vizard Agent actually do?
Here is the sequence on a real short built around a single fast action. Most of the work is locating the moment precisely in both versions, because a replay that starts a fraction late is a replay of the wrong thing.
- Distinguishes the normal-speed and slow-motion sources.
- Reviews the action frame by frame in each.
- Inspects every tenth of a second around the key instant.
- Chooses the clearest pass for each speed.
- Writes narration that introduces the replay.
- Generates captions across the speed change.
- Renders the full-speed pass and the slowed one.
- Confirms both are visible in the finished file.
- Checks the narration still leads over the music.
Step three is what makes the replay land on the right thing. A fast action can be over in a few frames, and the difference between the moment before it and the moment itself is smaller than a scrubber can find, so the search is done at a tenth of a second rather than by eye.
Step four is a choice worth making deliberately rather than by default. The clearest full-speed pass and the clearest slowed pass are often not from the same take, and Vizard Agent picks each on its own merits instead of assuming one clip has to supply both halves.
Step five is the whole point of the article. Narration is the cheapest possible signpost — one clause telling the viewer they are about to see it again converts a confusing repeat into a deliberate device, and it costs nothing to include.
Step eight exists because replays go missing. A rebuild for some other reason can quietly drop one of the two passes, and since the video still plays and still makes a kind of sense, nobody notices until the structure is gone.
What does the result look like?
An action you see happen, and then see properly. The narration Vizard Agent wrote hands the viewer from one pass to the other, so the second reads as generosity rather than as a glitch, and the slowed version gets to run as long as it needs to.
When does this not work well?
A replay costs time twice. In a very short format it eats the whole video, and an action that was already legible at full speed gains nothing from being shown again — the device is for moments the eye genuinely missed.
- Very short videos. Two passes leave no room.
- Actions that were already clear. Nothing to reveal.
- Low frame rate sources. The slowed pass judders.
- Dialogue over the action. The voice slows with it.
- Several replays. The device wears out quickly.
How do you fix a result that came back wrong?
Say which of the two passes is wrong. Because Vizard Agent built them separately from different source material, "the slow one starts too late" and "the full-speed one is unclear" are entirely different repairs, and naming the pass avoids having to redo both of them.
- "The slow pass starts late." Its in-point moves.
- "It still looks like a repeat." The narration signposts harder.
- "Too slow, it judders." Less slowdown on that source.
- "Only one pass is there." The rebuild dropped it.
How does Vizard Agent compare to doing it yourself?
By hand the slow-motion pass gets added because it looks good, with nothing said about it, and the confusion is invisible to whoever made it — they know it is a replay. It only shows up when somebody watches cold.
| By hand | Vizard Agent | |
|---|---|---|
| The signposting | Usually absent | Written into the narration |
| Finding the moment | Scrubbing | Tenth-of-a-second frames |
| Which source | Whatever is to hand | The clearest at each speed |
| Captions | Break at the speed change | Timed across it |
| After a rebuild | Assumed intact | Both passes confirmed |
Common questions
Why does a replay confuse people? Because an unexplained repeat looks like an edit fault. Vizard Agent signposts it instead.
Does it have to be narration? No. A caption works too, and Vizard Agent will suggest one.
How slow should the replay be? Slow enough to read the action. Vizard Agent checks the source can take it.
Can it slow a normal clip? Yes, within limits Vizard Agent will tell you about.
What if I filmed it in slow motion? Better. Vizard Agent uses the real frames rather than inventing them.
Should the full-speed pass come first? Usually, and Vizard Agent builds it that way; a replay only means something after the event.
What about the audio? Vizard Agent keeps the narration at speed and slows only the picture.
Can it do more than one replay? It can, but Vizard Agent will warn that the device wears out.
Will the captions break? Not if they are timed across the change, which Vizard Agent does.
Can it hold the frame instead? Yes. Vizard Agent treats a freeze as a different device doing a similar job.
How does it find the exact moment? Vizard Agent inspects frames at tenth-of-a-second intervals around it.
Does the replay have to be the same shot? No. Another angle works, and Vizard Agent will say when it reads better.
Will it fit a thirty-second short? Sometimes. Vizard Agent will say when the two passes do not fit.
Why did mine feel like a glitch? Because nothing in the video told the viewer it was a replay.