How to cut a bad moment out of a clip and still fill the same amount of time

Last updated 2026-09-15 · 8 min read

What is the short version?

A shot with a fault near the end is not unusable — the first two thirds are fine. The problem is that cutting the fault out leaves a gap, and the gap is in a timeline where everything after it is cued to something.

1. Tell Vizard Agent roughly where the fault is.
2. Say the shot has to stay its current length.
3. Ask for the loop blends checked individually.

What do you need before you start?

The clip, an approximate time, and the knowledge that the length is fixed. Vizard Agent will find the frame itself, so an estimate is enough, but it needs to know that shortening the shot is not an option or that is the fix it will reach for first.

• The clip. In the cut, or on its own.
• Roughly when. "Around six seconds" is plenty.
• What you saw. A step, a jump, a warp.
• That the length is fixed. And why, if it matters.
• What the motion is. A walk cycle loops differently.

What do you type into Vizard Agent?

Describe the fault in ordinary words. You do not need the frame number — finding it is part of the job, and a description like "a weird step" is enough to tell Vizard Agent what kind of wrongness it is looking for.

Prompt

Variants worth knowing:

• "Find where it actually starts." Your estimate is not the frame.
• "Repeat and blend the clean part." Names the method.
• "Still runs the full length." The constraint that rules out trimming.

What does Vizard Agent actually do?

Here is the sequence on a real clip of a walking figure that glitched two thirds of the way through. Most of it is spent locating the fault, because a fault you locate approximately gets trimmed approximately and shows up again two frames later.

1. Inspects the clip around the time you named.
2. Pulls the frame before the fault, the faulty frame, and two after.
3. Builds a motion strip of the region and probes the durations.
4. Confirms the last clean frame before the fault begins.
5. Grabs the opening frame to plan the loop blend.
6. Trims at the fault and crossfade-loops the clean take.
7. Rebuilds the background around the trimmed looping clip.
8. Composites the type and audio back onto the fixed cut.
9. Extracts frames at each loop blend.
10. Reviews the motion across the whole ending, blend by blend.

Step three is what makes the fault findable. A single frame tells you something is wrong; a strip of consecutive frames shows you which one is the first bad one, which is the frame you have to cut on.

Step five matters because a loop is a join between the end of the clip and its own beginning. Looking at the opening frame first tells Vizard Agent whether that join will work at all, or whether the loop needs to start somewhere else in the motion.

Step ten is the check people skip. One loop blend looking fine does not mean the second one does, and the last one often falls under a title where nobody is looking.

What does the result look like?

The same shot, the same length, without the fault. The motion carries through the ending, the joins are soft enough not to register, and Vizard Agent shows you each blend as frames so you can judge them rather than watch for them.

When does this not work well?

A loop needs something loopable. Motion that goes somewhere — a camera push, a subject crossing frame, a reveal — cannot repeat without obviously repeating, and a clip whose fault is at the start has nothing clean to loop from.

• Motion that travels. Repeating it jumps backwards.
• A fault near the start. Too little clean material.
• Speech or music in the clip. The audio loops audibly.
• Very short clips. The repeat becomes obvious.
• Changing light. A blend across a lighting change shows.

How do you fix a result that came back wrong?

Say which blend it is and what you can see there. Because Vizard Agent made each join separately and rendered frames at every one of them, a report like "the second blend stutters" points at one specific join rather than at the shot in general, and only that join gets rebuilt.

• "The second join stutters." The loop point moves in the cycle.
• "You can see it repeat." A different portion is looped.
• "The fault is still there." The trim moves to an earlier frame.
• "The blend is too soft." The crossfade is shortened.

How does Vizard Agent compare to doing it yourself?

By hand you scrub to the glitch, cut somewhere near it, copy the clip, and drag the copy to fill the gap. The seam shows because the copy starts where the motion was somewhere else, so you nudge it, and now the shot is two frames long.

Common questions

How exact does my timing need to be? Not very. Vizard Agent finds the frame from your estimate.

Will the loop be visible? Not if the motion suits it. Vizard Agent tells you when it will not work.

Can it loop a walk cycle? Yes, and that is the easiest case, because the motion returns to where it started.

What if the audio loops too? Say so. Vizard Agent can keep the audio running and loop the picture only.

What if the shot can get shorter? Then say that. Trimming is simpler and Vizard Agent will just trim.

Can it fix a fault in the middle? Yes, though there is less clean material each side. Vizard Agent will say if it is too little.

How many blends will there be? As many as the loop needs. Vizard Agent shows you each one.

Does it change the colour? No. Vizard Agent loops the same material, so the grade carries through.

What if the background was rebuilt? Vizard Agent rebuilds it around the new timing rather than leaving it behind.

Can it do this to several clips? Yes. Tell Vizard Agent which ones and roughly when in each.

Will the cut points move? No. The slot length stays the same, which is the point of looping.

What about a title over the ending? Vizard Agent checks the last blend under the title specifically.

Can I see the frames it used? Yes. Ask Vizard Agent for the motion strip and the blend frames.

Would regenerating be better? Sometimes. For a short clip Vizard Agent will tell you when that is the cheaper route.