How to stop the clothes changing between shots in a fast cut

Last updated 2026-09-10 · 8 min read

What is the short version?

Beat-matched cutting picks shots by rhythm. Nothing in that process knows that the jacket in shot four is the jacket from the second half of the day, so a thirty-second promo can change a character's clothes three times without anything looking obviously wrong on a timeline.

1. Go to Vizard Agent with the sources.
2. Say the story has to be logical, not just rhythmic.
3. Ask for a continuity pass on the finished cut.

What do you need before you start?

The footage and the story you want it to tell. Vizard Agent can cut to a beat grid without any of that, but continuity is a narrative constraint rather than a technical one, so it has to be stated before the shots are chosen.

• The source clips. However many there are.
• The story order. What happens before what.
• Which person matters. Continuity for them specifically.
• Whether wardrobe changes are allowed. Sometimes they are.
• The music. The cut is going to follow it.

What do you type into Vizard Agent?

Say it to Vizard Agent as a rule about the story rather than about the edit. "Make it dynamic" and "make it logical" pull in opposite directions, and if only the first of those is stated, the cut comes back rhythmically perfect and narratively incoherent.

Prompt

Variants worth knowing:

• "One journey." The constraint, in three words.
• "Must not change clothes." Names the failure directly.
• "Check the sections you fix." Fixes introduce new jumps.

What does Vizard Agent actually do?

Here is the shape of it on a real thirty-second music promo cut from three separate sources. The continuity work happens after the beat cut, because the beat cut is what creates the problem in the first place.

1. Samples every source into frame sheets.
2. Builds denser sheets to establish the real action order.
3. Detects the beat grid of the track.
4. Finds the natural shot boundaries in each source.
5. Assembles the beat-synced cut.
6. Uploads it and watches it back for motion and continuity.
7. Fixes the clothing continuity where it jumps.
8. Re-renders and re-uploads.
9. Inspects the affected sections frame by frame.
10. Confirms no wardrobe jumps remain across the joins.

Step two is what makes the fix possible at all. If Vizard Agent only has sparse frames it cannot tell which shots belong to which part of the day, so the denser sheets are what establish the order the story has to follow.

Step four matters more than it looks. Cutting on the beat without regard to where a shot naturally begins and ends produces fragments that could belong anywhere, so Vizard Agent finds the real shot boundaries first and then chooses among whole shots rather than arbitrary slices.

Step six is where the problem is actually found. A wardrobe jump is invisible on a timeline and obvious on playback, so Vizard Agent watches the render rather than inspecting the edit decisions.

Step nine is the step that gets skipped by hand. Fixing one jump by reordering shots frequently creates another one two cuts later, so Vizard Agent goes back over the sections it changed rather than assuming the repair was clean.

What does the result look like?

A cut that is still fast and still lands on the beat, in which the same person stays dressed the same way through each stretch of the story. Nobody ever notices continuity when it is right, which is precisely the point of doing it.

Vizard Agent also tells you which shots it moved, so you can check for yourself that the rhythm survived the reorder.

When does this not work well?

Continuity can conflict with the best shots. If the strongest close-up in the whole set is from the wrong part of the day, keeping the wardrobe consistent means giving that shot up, and sometimes that is the wrong trade.

• The best shot is out of sequence. Something has to give.
• Deliberate transformation stories. The change is the point.
• Very short sources. Not enough shots to reorder.
• Multiple people. Continuity for each of them multiplies.
• Heavily stylised edits. Rules bend where the look is abstract.

How do you fix a result that came back wrong?

Point at the pair of shots that disagree with each other. Because Vizard Agent is working from the assembled cut and knows where each shot came from, naming those two is enough for it to work out which one of them is out of sequence.

• "The jacket changes at 0:11." That pair gets reordered.
• "Keep that shot, move the other." Vizard Agent obeys the priority.
• "The rhythm broke." The reorder gets re-timed to the beat.
• "The change is intentional." Marked as allowed.

How does Vizard Agent compare to doing it yourself?

By hand a fast cut is assembled for rhythm and continuity is checked afterwards by watching, which works — until a fix reorders the shots and quietly breaks something else. The second pass is the one that rarely happens.

Common questions

Can it cut on the beat and stay continuous? Usually. Vizard Agent will tell you when the two genuinely conflict.

How does it know what the order is? From dense frame sheets of each source, read before cutting.

What if I want a transformation? Say so and Vizard Agent treats the change as intentional.

Does it check faces too? Yes, if you say the person matters. Wardrobe is one signal of several.

Will fixing it slow the cut down? No. Vizard Agent re-times the reorder to the same beat grid.

Can it flag jumps without fixing them? Yes. Ask Vizard Agent to report and you decide.

What about props and drinks? Same idea. Name what should stay consistent and Vizard Agent watches for it.

Does it work across three sources? Yes, and that is where the problem usually starts.

Will it drop my best shot? Only if it has to. Tell Vizard Agent which shots are protected.

What about generated footage? Same check. Generated sequences drift the same way.

Can it fix it without re-rendering? The reorder needs a render, but only of the cut.

How does it verify? Vizard Agent goes frame by frame across the sections it changed.

Does the music need re-editing? No. The track is untouched by a reorder.

Why did nobody catch it? Because at four cuts a second, each shot is gone before you can question it.