Vizard Agent

How to find the clip that never made it into the edit

Last updated 2026-09-22 · 8 min read

Ask Vizard Agent to reconcile the edit against your upload list by filename rather than by count. A clip that fails one quiet step early on leaves no error behind, so the only reliable way to catch it is to compare the two lists name by name and pull the one that is absent.

What is the short version?

You uploaded a trip's worth of clips and asked for all of them, in order. The cut looks right, runs long, and is missing one. Nothing failed loudly enough to notice, so Vizard Agent compares names rather than trusting the count.

  1. Ask Vizard Agent to list what is in the edit against what you uploaded.
  2. Let it fetch the one that did not arrive.
  3. Rebuild with the full set in the order you sent them.

What do you need before you start?

The upload itself, and some sense of how many files you sent. You do not need to know which one is missing — that is the part Vizard Agent works out. If you remember a specific shot you expected to see and did not, say so, because a named expectation gives the reconciliation somewhere concrete to start and confirms the answer once it arrives.

It also helps to say whether you want every clip or only the good ones. Those are different jobs, and an edit built from a selection is supposed to be shorter than your upload. Vizard Agent will not go hunting for a missing file if the brief was to leave the weak material out, so be explicit when the brief changes from "the best of this" to "all of this, in order".

What do you type into Vizard Agent?

Plain description works. In the session this article is drawn from, the request began as a long cinematic cut of the talking moments and later became something stricter: every clip, in the exact order they were attached. That second brief is the one where a missing file matters, because the whole point is completeness.

Use all the clips I uploaded, in the order I attached them, and tell me if any of them are not in there.

That last clause is the useful half. Without it, Vizard Agent renders what it can find and the result looks finished. With it, the agent owes you an explicit account of the set, which is a different and much harder thing to fake.

What does Vizard Agent actually do?

It builds the running order as an explicit list first — one line per attachment, in attachment order, with the duration of each — and then compares that list against the files it actually has on disk. A count would have passed. The names did not, and the mismatch pointed at exactly one object rather than at a vague shortfall somewhere in eighty-three files.

The sequence in that session went:

The order of those steps matters. Vizard Agent did not re-download everything, and it did not ask for a fresh upload. It found the one name that had no local counterpart and went to get that one.

What does the result look like?

You get the edit you asked for with the full set in it, and a statement of what was missing and where it came from. The count in the delivered cut matches the count you sent, which is the only version of "complete" that survives a second look. The runtime lands where the totalled manifest said it would.

In practice the rest of that session carried on as normal — a cinematic grade applied consistently across all eighty-three clips, dissolves between them, and a music bed ducked under the original dialogue. The reconciliation was a two-minute detour in a long job, not the job itself. That is the right proportion for it.

When does this not work well?

When the file never reached the upload at all. Vizard Agent can only reconcile against the attachment list it was given; a clip that failed in your browser before it was ever attached does not appear on either side of the comparison, so nothing looks wrong. The reconciliation is honest about what was received, and that is the limit of it.

It also does not help when the brief was a selection. If you asked for the talking moments and a clip is silent throughout, its absence is the edit working correctly. Vizard Agent will tell you that a clip was excluded by the brief rather than lost, but only if you ask about that specific clip — a general "is anything missing" against a selective brief has no meaningful answer.

And a corrupt file is a different failure. If a clip arrived but will not decode, the fix is not reconciliation, it is a replacement copy. Vizard Agent will say which of the two it is hitting rather than reporting both as "missing".

How do you fix a result that came back wrong?

Name the clip you expected. If you can say "the one from the souvenir shop is not in there", Vizard Agent has something specific to find, and the search stops being a sweep. In the same session the user flagged a sideways shop clip and an abrupt ending, and both were fixed by going back to the specific source rather than adjusting the cut around them.

If the clip is present but you did not notice it, ask where it sits. Vizard Agent can give you the timestamp in the finished cut, which usually settles the question faster than rescrubbing. A clip that runs three seconds in the middle of a long sequence is easy to miss on a review pass and easy to confirm by timecode.

If the order is wrong rather than the contents, say that instead. Reordering is a cheap rebuild. Vizard Agent keeps the graded, normalised parts and reassembles them, so you are not paying for the full pass a second time.

How does Vizard Agent compare to doing it yourself?

You would notice eventually. An edit missing one clip out of eighty-three is not obvious on a first watch, and the usual way people catch it is by scrubbing the timeline against a folder in another window. That works and it takes a long time, and it is exactly the kind of counting task attention fails at.

The real difference is what happens after you find it. Doing it yourself, the fix is usually re-importing everything and rebuilding the sequence, because it is easier than finding the right insertion point in a timeline of that length. Vizard Agent rebuilds from the manifest, so adding one file back is the same operation as building it the first time and costs about as much as one more render.

Common questions

Why did it go missing without an error? A probe that gets skipped rather than failing leaves nothing behind. Vizard Agent catches it by reconciling names, not by looking for errors that were never raised.

Do I need to upload everything again? No. Vizard Agent fetches the individual missing file by its own address.

Can I ask for the check without rebuilding? Yes. Ask Vizard Agent for the reconciliation on its own and you get the list without a render.

Does this work on audio files too? Yes. The comparison is on the attachment list, so any file type you sent is in scope for Vizard Agent.

What if two clips have the same name? Vizard Agent distinguishes them by their upload position, which is why it works from attachment order rather than from names alone.

Will the order survive the fix? Yes. The clip goes back into its attachment position, not onto the end.

How long does the reconciliation take? Under a minute for a set this size. The re-render afterwards is the slow part.

Can I see the manifest? Ask for it. Vizard Agent will print the ordered list with durations before it renders anything.

What if more than one is missing? The same comparison finds all of them at once; Vizard Agent reports the full set rather than stopping at the first.

Does a missing clip affect the music? It does if the bed was timed to the old runtime. Vizard Agent re-times the mix to the corrected length.

Is the count enough on its own? No, and that is the point. Two files can be missing while a duplicate keeps the count right, so Vizard Agent compares names.

Can I check a cut I made elsewhere? Only if you give Vizard Agent both the cut and the source files. It compares what it can see.

What if the clip is missing on purpose? Say so and Vizard Agent leaves it out, and will not flag it on later passes.

Does the grade get reapplied to the recovered clip? Yes, the same grade as the rest, so it does not stand out when it goes back in.