How to change one object in a video without the edit changing everything else

Last updated 2026-09-17 · 8 min read

What is the short version?

Asking for one object to be replaced sounds like a small edit, and in a video full of transformations and effects it is the opposite. Everything you did not mention is at risk, and the risk shows up as a slightly different crop or a missing first second.

1. Tell Vizard Agent the one element that changes.
2. List what must be preserved exactly — timing, camera, effects, logo.
3. Ask for a source-against-result comparison before delivery.

What do you need before you start?

The finished video and a precise description of the change. Vizard Agent needs to know not just what the object becomes but at which moment, because an object that splits, transforms or leaves frame has several identities over its life and each one has to be specified.

• The finished video. The version you are keeping.
• The object. Which one, and where it starts.
• What it becomes. And after which moment.
• What must not change. Camera, timing, effects, ending.
• Whether other elements transform. They often do.

What do you type into Vizard Agent?

Write the exclusions as a list. In a shot where an object cracks, transforms and becomes something else, "keep everything else the same" is not specific enough to test against — but "preserve the crack timing, the neon, the road transformation and the final logo" is.

Prompt

Variants worth knowing:

• "Replace only." Scope, in two words.
• "When it cracks, the left piece…" Timing for a change of identity.
• "Preserve the final logo." Names the end, which edits often lose.

What does Vizard Agent actually do?

Here is the Vizard Agent sequence on a stylised vertical clip where a falling ball cracks into two, and only one of the halves was meant to change. The route it ends on is not the route it starts with.

1. Extracts representative frames and locates each transformation.
2. Examines the fall, the crack and the transformation frame by frame.
3. Records the exact positions of both pieces before and after the break, so Vizard Agent can tell them apart later.
4. Prepares an identical copy of the original so there is always a clean reference.
5. Applies a targeted edit to one piece only and keeps the vertical format.
6. Compares source and result in a single control view.
7. Finds the opening has changed, locates the exact cut point and splices the original opening back.
8. Measures frame rates and timings to build a clean join between the two.
9. Inspects the left piece after the crack, on the road, and just before the final transformation.
10. Extracts a clean texture of the original ball to composite locally.
11. Measures the piece's path and calculates its position frame by frame.
12. Composites the replacement along that trajectory, then corrects the crop and the mask centre.
13. Delivers both versions — the local composite and the untouched original.

Step six is the step that catches the real problem. The new object looked right; the opening second was gone and the crop had shifted. Vizard Agent compares against the source rather than judging the output on its own merits, which is the only way that kind of drift is visible.

Step seven is the repair that follows. Rather than re-running the edit and hoping, Vizard Agent keeps the good part of the edited section and splices the original footage back over everything the edit should never have touched.

Steps ten to twelve are the fallback when a generative pass will not hold still. A texture lifted from the source, animated along the measured path of the object it replaces, changes exactly the pixels you asked about and nothing else.

What does the result look like?

The same video, with one object different. The crack lands on the same frame, the camera and the effects are as they were, the ending is intact, and Vizard Agent can show you the source and the result side by side at the moments where a change would be most visible.

When does this not work well?

Some objects cannot be changed in isolation. If the thing you are replacing casts light on the scene, is reflected in other surfaces, or is what the effects are reacting to, then changing it means changing everything it touches — and that is a regeneration, not an edit.

• Objects that light the scene. Their glow is on everything else.
• Reflections. The old object survives in every shiny surface.
• Heavy motion blur. The replacement reads as a sticker.
• Objects that deform. A texture cannot squash convincingly.
• Very short appearances. Not enough frames to measure a path.

How do you fix a result that came back wrong?

Say what changed that should not have changed. Vizard Agent treats that as a splice problem rather than an editing problem, and restores the affected range from the original file instead of re-running the whole pass and hoping for a better draw the second time.

• "The opening is different." The original opening is spliced back in.
• "The crop has changed." The result is rebuilt at the source dimensions.
• "The wrong piece changed." The positions are re-measured after the crack.
• "It drifts off the path." The object's trajectory is calculated frame by frame.

How does Vizard Agent compare to doing it yourself?

By hand you either roto the object for an evening or you feed the whole clip to a generative edit and accept what comes back. The second is quick and it quietly re-renders things you never mentioned, which you discover when someone asks why the logo at the end looks slightly different.

Common questions

Why does an edit change things I did not mention? Because it re-renders the shot. Vizard Agent limits the change and verifies the rest.

Can it keep the exact timing? Yes. Vizard Agent measures the frame rate and builds the join on frame boundaries.

What if the object splits into two? Say what each piece becomes and when. Vizard Agent tracks them separately.

Can I have the original back too? Yes. Vizard Agent keeps a clean copy from the start and can deliver both.

Does it work on generated video? Yes, and that is the common case — the source is a render you do not want to repeat.

How is the replacement made to match? Often from the source itself, so the lighting and grain already agree.

What about the audio? Untouched, unless you ask for it. Vizard Agent treats this as a picture-only change.

Will the effects still react to it? Only if they were baked in. Vizard Agent leaves anything driven by the original object exactly as it was.

Can it change two objects at once? Yes, though each one is measured and composited separately.

How do I check it myself? Look at the first and last second of what Vizard Agent returns — that is where drift hides.

What if the new object is the wrong size? Vizard Agent measures the original's size at each point and matches it.

Can it work from a still of the replacement? Yes. Give Vizard Agent a reference image and it builds the texture from that.

What if the object leaves the frame? Its path is measured only while it is visible, which is all the composite needs.

Is there a cheaper approach? A local composite is usually cheaper than a generative pass, and Vizard Agent will suggest one when it fits.