How to make a busy wide shot readable to a viewer

Last updated 2026-09-05 · 8 min read

What is the short version?

A wide shot of something busy shows everything and communicates nothing. Two changes fix it, and they have to happen together: get closer, so there is less to look at, and slow it down, so there is time to look.

1. Go to Vizard Agent with the clip.
2. Say you cannot tell what is happening in it.
3. Ask for a tighter crop and a slower speed.

What do you need before you start?

The footage at its original resolution and a sense of what the viewer is meant to notice. Cropping and slowing both spend picture quality, so the higher the resolution you start from, the more of both you can afford before it shows.

• The original file. Not a compressed export.
• What the viewer should see. The hands, the tool, the queue.
• How tight. Or say "tighter still" and iterate.
• How slow. Half speed reads very differently from quarter.
• Whether the length may change. Slowing makes it longer.

What do you type into Vizard Agent?

Describe the symptom, not the setting. "Zoom in and slow it down" is a pair of instructions with numbers you have to guess; "I cannot tell what is happening until it is much closer" is a description of the problem that the numbers can be derived from.

Prompt

Variants worth knowing:

• "Tighter still." Most first crops are too generous.
• "Slow it so I can follow it." A goal, not a percentage.
• "Keep it sharp." Tells it quality is part of the brief.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real clip of a busy workshop that read as noise at full width. The interesting part is the second half, where the first approach is thrown away and rebuilt in a different order.

1. Tests two slow-motion methods against the footage.
2. Compares the two tests rather than assuming one is better.
3. Builds the tight slow-motion shot from the chosen method.
4. Upscales the slowed shot to recover some sharpness.
5. Assembles the tighter, slower version with the new copy on it.
6. Has the slow motion checked in motion, not on stills.
7. Upscales the real-time shot instead, then slows that.
8. Rebuilds the clip with the clean slowdown.
9. Checks the rebuilt slow motion for artefacts and smoothness.
10. Re-mixes so the narration sits over the quieter bed.

Steps four and seven are the same idea attempted in two orders, and only one of them works. Slowing footage first and sharpening afterwards means the enhancement is applied to frames that were invented between the real ones; upscaling first means the interpolation has better frames to work from.

Step six is the standard being applied. Slowed footage looks fine on a still frame and falls apart in movement, so the test that decides whether a slowdown worked has to be watching it run rather than examining a frame out of it.

Step one matters more than it looks. Different slow-motion methods fail differently — one smears fast movement, another stutters on it — so the right one depends on what is actually moving in your shot, which is a question best answered by trying both.

What does the result look like?

A shot you can actually read: closer in, slower, and sharp enough that the crop Vizard Agent made never announces itself, paced so that a viewer following the action for the very first time can see what the activity in it actually is.

It is usually a few seconds longer than the original, which is the trade you are making.

When does this not work well?

Both of these moves spend resolution, so a low-resolution or heavily compressed source runs out of it quickly. Slowing the footage also exposes anything that was already wrong with the shot — a shaky camera, rolling-shutter wobble, or a frame rate too low for Vizard Agent to interpolate cleanly.

• Low-resolution footage. The crop goes soft immediately.
• A low frame rate. Interpolation has too little to work from.
• Handheld shake. Slowing makes it worse, not better.
• Very fast motion. Some methods smear it badly.
• Nothing to see. Slowing an empty shot just makes it longer.

How do you fix a result that came back wrong?

Say what you still cannot see, or what the slowdown did to the picture. Vizard Agent keeps the crop, the method it chose and the upscale it applied, so a correction changes one of those rather than restarting the shot.

• "Still too wide." The crop tightened again from the source.
• "It looks soft." Rebuilt with the upscale before the slowdown.
• "The motion stutters." The other slow-motion method tried.
• "Now it drags." The speed lifted while the crop is kept.

How does Vizard Agent compare to doing it yourself?

The manual version does both moves in the obvious order — crop, slow, then sharpen if it looks bad — and the sharpening arrives too late to help. It also tends to pick one slow-motion setting and stay with it, whichever way the footage happens to move.

Common questions

How tight should the crop be? Tighter than feels right. Vizard Agent will go further if you say.

Does slowing make the video longer? Yes. Say if the runtime is fixed and Vizard Agent trims elsewhere.

Will it look soft? Not if the upscale comes first, which is how Vizard Agent orders it.

Can it slow only part of the shot? Yes. Name the seconds and Vizard Agent ramps into them.

What about the audio during a slowdown? Usually replaced or dropped. Vizard Agent will ask or use music.

Can it track the action instead? Yes, if the activity moves. Vizard Agent can follow it.

Does it work on phone footage? Yes, within limits. Vizard Agent says when the source runs out.

Can I see both slow-motion tests? Yes. Ask Vizard Agent for the comparison.

What if the camera was shaky? Stabilise first. Vizard Agent can measure the shake and advise.

Can it add a caption pointing at the action? Yes. Say what to point at and Vizard Agent places it.

Will the crop work vertically too? Yes. Vizard Agent reframes the tight shot for the format you name.

How slow is too slow? When it stops reading as action. Vizard Agent checks it in motion.

Can it do this to one shot in a longer edit? Yes. Only that shot is rebuilt.

Why not just zoom in the player? Because zooming a delivered file enlarges compression, while cropping the original enlarges picture.