Vizard Agent

How to make a high-energy recap of a night out

Last updated 2026-08-19 · 6 min read

Upload the footage and tell Vizard Agent you want a high-energy recap. Vizard Agent surveys every second of the night, analyses the beat grid and energy arc of candidate tracks, cuts the shots to the beat, and builds the whole minute so it peaks where the music does.

What is the short version?

A night out lives on a phone as a pile of dark, shaky, vertical clips. The recap that makes people wish they had come is not the best clip played long; it is many short ones cut hard to a track that is going somewhere.

  1. Go to Vizard Agent and upload everything from the night.
  2. Say you want high energy and what it should make people feel.
  3. Say the length and the shape.

What do you need before you start?

Very little, which is the point of this format. Vizard Agent surveys the footage second by second and picks the moments itself, so what actually matters is telling it the feeling you are going for, because that decides both the music and how hard the cuts land.

What do you type into Vizard Agent?

Describe the energy, not the cuts. Vizard Agent reads a line like "high energy, make people wish they'd been there" as a direction for pacing, music choice and grading all at once, and that gets you a better recap than a list of which clip to use when.

Prompt

Make a [60] second recap of [the night] from my footage — high energy, make people wish they'd been there. [Vertical].

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real night-out recap. The first third is not editing at all: the upload was damaged, and Vizard Agent rebuilt the video stream before it could look at a single frame.

  1. Probes the upload and finds the file will not play.
  2. Reads the raw bytes, scans the container boxes and analyses the parameter set to work out what survived.
  3. Locates every keyframe, traces the frame boundaries and recovers the full stream, then rebuilds the audio packets and remuxes a playable file.
  4. Extracts one frame per second across the whole night and reviews the survey in two halves.
  5. Searches for candidate tracks, analyses each one's beat grid and maps its musical structure and energy arc.
  6. Builds a shot catalogue, then samples finer frames around the planned cut points.
  7. Renders animated title and end-card graphics and checks them frame by frame.
  8. Calculates the beat grid across the sixty-second timeline, measures the music's loudness and generates transition sound effects.
  9. Renders the cut, measures the mix, re-renders with the audio normalised and watches the finished recap back.

Steps 1 to 3 are the ones worth knowing about. A corrupted phone upload usually means the night is gone; Vizard Agent treated it as a file to be repaired rather than a job to be refused, and the recap exists because of it.

What does the result look like?

From the run this page is written from, probed on the delivered file: 1080x1920, H.264, 30fps, 60.17 seconds, AAC audio. Vertical, one minute, cut to the beat grid of the chosen track with animated titles and transition effects over recovered footage.

Sixty seconds at this pace is a lot of shots. Vizard Agent times the cuts against the measured beat rather than an even interval, which is why the recap accelerates into the drop instead of running at one speed the whole way through.

When does this not work well?

Night footage is the hardest material there is, and the recap format hides some of that and not all of it. Vizard Agent grades and paces around the problems, and the source still sets the ceiling on how good it can look.

How do you fix a result that came back wrong?

Say what is off — the track, the pace or a specific shot. Vizard Agent keeps the recovered footage, the survey sheets, the beat grids for every candidate track and the rendered graphics, so a change is a re-cut against measurements it already holds.

How does Vizard Agent compare to doing it yourself?

By hand this is scrubbing forty clips in a phone editor, tapping cuts roughly in time with a track, and often finding out that the file will not import at all before any of that work even starts. Vizard Agent measures the track and repairs the source, so neither problem stops the recap.

By hand Vizard Agent
A broken upload The night is gone Stream rebuilt from the raw bytes
Choosing the track Play a few and guess Beat grid and energy arc measured
Cutting to the beat Tap it by ear Timed against the calculated grid
The mix Whatever the app does Loudness measured, then normalised

Common questions

What if my video will not play? Upload it anyway. Vizard Agent will try to recover the stream before giving up on it.

Does it pick the music? Yes. Name a genre if you have one and Vizard Agent measures candidates before choosing.

Will it add titles? Yes, animated, if you give it a name for the night.

How long should a recap be? Sixty seconds. Long enough to build, short enough to rewatch.

Can it avoid showing faces? Say so and Vizard Agent selects around the shots people are recognisable in.

Can I get a shorter cut too? Yes. Ask for both and the thirty-second version is re-cut rather than trimmed.

Does it add sound effects? Yes. Vizard Agent generates transition hits and places them on the beat grid it calculated for the track.

Will it grade the dark footage? Yes. Vizard Agent lifts the night shots as part of the render, within what the phone sensor actually captured.

Can I use my own music? Upload the track and Vizard Agent analyses its beat grid the same way before cutting to it.