Vizard Agent

How to cut action footage into a reel that tells a story

Last updated 2026-08-16 · 6 min read

Upload your footage to Vizard Agent and ask for a reel that tells a story rather than clips in order. Vizard Agent reviews the frames to find the beginning, the attempt and the payoff, analyses the music for the exact moment of its drop, and speed-ramps the cuts so the biggest shot lands on it.

What is the short version?

The difference between a montage and a reel people actually finish is an arc: something is attempted, something goes wrong, something lands. The footage almost always contains one already, and putting the clips in the order they were filmed is exactly what buries it.

  1. Go to Vizard Agent and upload the raw footage.
  2. Say the feeling you want and that it should tell a story.
  3. Say the length and where it is going.

What do you need before you start?

The footage and the feeling. Vizard Agent finds the story shape by looking at the frames, so what it needs from you is the register — adrenaline, triumph, calm — which decides both the music and how hard the cutting drives.

What do you type into Vizard Agent?

Ask for a story explicitly. The instruction "not just clips in order" genuinely changes what Vizard Agent builds, because it turns the arc into a stated requirement rather than a lucky outcome of good clip selection — and the feeling you name decides how hard the cutting drives.

Prompt

Cut my footage into a [30] second reel that tells a story — not just clips in order. It should have an [adrenaline] feel.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real story reel. Two measurements shape everything that follows: where the music's drop actually falls in the track, and how the phone's rotation flag behaves when the footage is cut and re-encoded rather than played back.

  1. Probes the file and runs shot transcription and speech recognition in parallel.
  2. Searches the music library for high-energy tracks and downloads the chosen one.
  3. Extracts a grid of frames and reads it to understand the sequence of attempts.
  4. Extracts the ending frames specifically to verify the payoff moment is there.
  5. Re-extracts those frames at one per second to see the whole final sequence.
  6. Tests a short cut to confirm the phone's ninety-degree rotation is handled correctly.
  7. Tests a slow-motion command on one clip to verify the output duration behaves as expected.
  8. Analyses the music to find the exact timestamp of the beat drop.
  9. Generates twelve speed-ramped vertical clips, concatenates them, and mixes the natural sound with the music so the drop lands where the payoff does.

Steps 6 and 8 are the two that decide whether this works. Phone rotation silently breaks vertical cuts, and a beat drop placed by ear is always a fraction late — Vizard Agent measured both rather than trusting either.

What does the result look like?

From the run this page is written from, probed on the delivered file: 1080x1920, H.264, 30fps, 30.13 seconds, AAC audio. Vertical, thirty seconds, twelve speed-ramped clips cut so the payoff lands on the music's drop, with the footage's own sound mixed under the track.

Vizard Agent then extracted a grid from the finished cut and ran an analysis over it to check the pacing, the transitions and the synchronisation of picture and sound.

How long it takes was not measured separately here. Comparable work runs a median of 28 to 38 minutes end to end, and the upper quartile is several times the median. Across all projects the median cost by tier is Flash 47, Pro 55, Max 242, Ultra 263 credits.

When does this not work well?

A reel can only ever tell a story the footage actually contains. Vizard Agent finds the arc that is there, verifies the ending exists in the frames and cuts hard to the music, and none of that can manufacture a payoff that nobody was filming when it happened.

How do you fix a result that came back wrong?

Say which moment is wrong. Vizard Agent keeps the shot analysis, the measured beat-drop timestamp and every speed-ramped clip separately, so moving the payoff or softening a ramp re-cuts against timings it already holds rather than starting the whole analysis over from the source footage.

How does Vizard Agent compare to doing it yourself?

By hand this is finding the drop by scrubbing, ramping twelve clips one at a time, and re-rendering the whole thing every time you move a cut by a few frames — plus discovering halfway through that the vertical footage exported sideways.

By hand Vizard Agent
Finding the story Watch and guess Frames read, ending verified
The drop Scrub to it by ear Timestamp measured
Speed ramps One clip at a time Twelve generated in one pass
Phone rotation Discover it sideways Tested on a short cut first

Common questions

Does it need me to pick the best moments? No. Vizard Agent reads the frames and finds the arc, and naming your favourite moment guarantees it survives.

Will it use the original sound? Yes. Vizard Agent mixes the natural audio under the music rather than muting it.

Can it do slow motion? Yes. Vizard Agent tests the speed change on one clip first to confirm the durations behave.

Will vertical footage stay upright? Yes. Vizard Agent tests how the rotation flag behaves before cutting anything.

How long should a reel be? Thirty seconds. Longer and the arc stops being one thing, and the drop has already happened by the time the clips run out.

Does it need high frame-rate footage? Only for slow motion. Vizard Agent tests the speed change first and standard footage softens when it is ramped hard.

Can I get a longer version? Yes. Vizard Agent re-paces from the same clips rather than adding filler, though the arc is usually tightest at thirty seconds.