Vizard Agent

How to fix a generated shot that is too short for the line it carries

Last updated 2026-09-10 · 8 min read

Ask Vizard Agent to measure the script against your timing windows before it generates a frame. A line written for four seconds usually needs five, and the two ways out are compressing the delivery, which sounds rushed, or lengthening the shot — so it checks the fit first and extends the picture where the words need it.

What is the short version?

A shot script with timings is a plan made before anybody heard the words out loud. The lines are almost always slightly longer than their windows, and the video that results is a narrator gabbling to keep up with a picture that was cut too tight.

  1. Go to Vizard Agent with the script and its windows.
  2. Ask it to check the fit before generating.
  3. Ask for the picture to extend where a line overruns.

What do you need before you start?

The script written as lines against windows, and a view on which matters more. Vizard Agent can hold the total runtime or the pacing but rarely both — a script that overruns by four seconds either makes the film four seconds longer or loses four seconds of words.

What do you type into Vizard Agent?

Ask for the measurement before the work. Handing over the script and asking for the film means everything is generated to the plan, and the mismatch is discovered when the narration goes on top — after all the shots exist.

Prompt

Here is the script with timing windows for each shot. Before generating anything, measure the actual script length against each window and tell me which lines will not fit. Where a line overruns, extend the shot rather than speeding up the read.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the sequence on a real short built from a shot-by-shot script with four timed beats. The film was made at the planned length first, and then rebuilt at a calmer one — which is the honest way this usually goes.

  1. Reads the script and its timing windows.
  2. Checks the voice options and the one you want.
  3. Measures the actual script length against each window.
  4. Generates the narration beats in that voice.
  5. Fits them to the planned timeline and mixes.
  6. Reviews the result for pacing and clarity.
  7. Rebuilds the picture and the narration at a calmer pace.
  8. Re-measures the extended narration.
  9. Checks the longer version for natural pacing and sync.

Step three is the cheap check that changes everything downstream. Measuring a script against a window costs seconds and tells you whether the film you planned is the film that can exist, before any shot has been generated to a length that will not hold its line.

Step seven is the decision the article is about. Compressing narration into a window that is too small is technically possible and audibly wrong — the read loses its pauses first, then its emphasis, and a viewer hears somebody hurrying without knowing why.

Step nine matters because a longer film is not automatically a better one. Extending the shots can make the picture feel slack, so the calmer version gets checked for pacing rather than assumed to be an improvement.

What does the result look like?

A film whose narration sounds unhurried, usually a little longer than the script imagined, with each line sitting comfortably inside its own shot. Vizard Agent tells you which windows it extended and by how much, so you can trade a few of them back if the runtime is fixed.

When does this not work well?

Sometimes the runtime simply cannot move, and Vizard Agent will say so rather than quietly stretching it. An ad slot, a platform maximum or a music bed of fixed length all mean the film is not allowed to grow, and the only remaining remedy is fewer words rather than more seconds.

How do you fix a result that came back wrong?

Tell Vizard Agent whether you would rather spend seconds or words. Because it already knows the overrun line by line, naming which of the two currencies you are willing to spend resolves the entire script in one pass rather than one shot at a time.

How does Vizard Agent compare to doing it yourself?

By hand the script is written to timings that were estimated by reading it in your head, which is faster than anyone speaks. The shots get made to those numbers, and the fix at the end is to speed the voice up, because everything else is already built.

By hand Vizard Agent
When the fit is checked After everything is generated Before anything is
The usual remedy Speed up the read Extend the shot
The estimate Read in your head Measured against the voice
What you are told That it does not fit Which lines, and by how much
The choice Made for you Seconds or words, your call

Common questions

Why is my script always too long? Because it was timed by reading it silently, which is faster than speech.

Can it just speed up the voice? It can, and Vizard Agent will tell you it is the worse of the two options.

How much overrun is normal? Often ten to twenty per cent. Vizard Agent measures rather than guessing.

What if the runtime is fixed? Then Vizard Agent trims the script instead and shows you what it cut.

Can it extend real footage? Only a little. Vizard Agent finds generated shots far more flexible.

Will the pacing feel slow? Vizard Agent checks the longer version rather than assuming it is better.

Does the voice matter? A great deal. A slower voice needs more seconds for the same words.

Can I choose per line? Yes. Tell Vizard Agent which lines get their seconds.

What about the music? If the bed is fixed, say so; Vizard Agent works within it.

Will the shots be regenerated? Vizard Agent regenerates only the ones whose length actually changes.

Can it show me both versions? Yes. Vizard Agent can deliver the planned length and the calmer one.

Does this apply to captions too? Yes. Vizard Agent retimes them to the narration's new timing.

What if only one line overruns? Vizard Agent extends that shot and leaves the rest alone.

Why does a rushed read sound wrong? Because compression removes the pauses before it removes anything else.