How to move the camera in a generated shot without the scene moving too

Last updated 2026-09-17 · 8 min read

What is the short version?

A camera move sounds like a purely geometric request and is not. The generator is producing new frames, and new frames contain a scene that has to be decided again — including the parts you had already established.

1. Tell Vizard Agent that only the camera moves.
2. Name the state that must survive — what is broken, spilled, moved.
3. Ask it to start from a frame of the existing shot.

What do you need before you start?

The existing shot and a clear description of the move. Vizard Agent starts the orbit from a real frame of your footage, so the more precisely you say where the camera ends up, the less it has to invent about what is there.

• The existing shot. Not a description of it.
• The move. Orbit, push, rise, and to where.
• What must not move. The subject, usually.
• The state of the scene. Knocked over, open, spilled.
• The transitions around it. It has to match them.

What do you type into Vizard Agent?

List for Vizard Agent the things that should stay still. It reads as pedantic when you write it out, and it is the entire difference between a camera move and a new shot: anything you leave off the list is something the generator is free to animate.

Prompt

Variants worth knowing:

• "Only the camera moves." The instruction that matters.
• "The cans stay knocked over." Names the state.
• "Start from the existing frame." Anchors it to your footage.

What does Vizard Agent actually do?

Here is the Vizard Agent sequence on a real shot extended with an additional camera angle. It takes three attempts in all, and each one fixes a different thing the generator had felt perfectly free to change on its own.

1. Prepares a matching reference frame for the new view.
2. Creates the side profile as a still first.
3. Animates the move into that profile.
4. Adds the new beat after the original ending.
5. Reviews the three-angle sequence as a whole.
6. Prepares the original front frame as the orbit's starting point.
7. Generates a true orbit rather than a cut to a new angle.
8. Regenerates the orbit with the subject and the objects locked.
9. Verifies there is no walking and no reset in the final cut.
10. Removes the seam while preserving the angle change.

Step eight is the fix and it is worth naming precisely. The first orbits were geometrically correct and the world inside them was alive: locking the subject and the objects turns the shot into a camera move rather than a new performance.

Step six is what ties it to your footage. Starting the move from an actual frame means the orbit is going round the scene you filmed rather than a plausible reconstruction of it.

Step ten is the last thing anybody notices. A generated angle change often arrives with a wipe or a dissolve built into it, and if the rest of the film cuts hard, that seam is the only place the join shows.

What does the result look like?

The same scene seen from a new position. Nothing has stood back up, nobody has taken a step, every object is where the earlier shot left it, and Vizard Agent has matched the move to the transitions the film was already using elsewhere.

When does this not work well?

Large moves invent more. A small orbit around a subject can be anchored to what is visible; a move that travels to the far side of the room has to generate a wall nobody has seen, and the state of the scene there is a guess.

• Long travels. Most of the destination is invented.
• Complex scenes. More state to hold still.
• Subjects mid-action. Freezing them looks unnatural.
• Reflections. They show the parts being invented.
• Fast moves. Motion blur hides the state, then reveals it.

How do you fix a result that came back wrong?

Name the thing that moved when it should not have. Vizard Agent locks items individually rather than as a group, so a note like "the cans stood back up" simply adds one more item to the lock list instead of restarting the shot from scratch.

• "It started walking." The subject is locked and the move regenerated.
• "The cans reset." Those objects are added to the locked state.
• "There is a wipe on it." The built-in transition is removed.
• "It does not match the other angle changes." The transition style is matched.

How does Vizard Agent compare to doing it yourself?

By hand you describe the new angle and get a new shot, which is a reasonable shot of a subtly different scene. Spotting what changed means comparing it against the previous shot object by object, which almost nobody does before the client asks why the cans are upright.

Common questions

Why does the subject move at all? Because the frames are being generated. Vizard Agent has to be told to freeze them.

What should I list as locked? Anything whose state matters. Vizard Agent holds a spill, a broken thing or an open door.

Does it have to start from my footage? Not necessarily, but it anchors the scene. Vizard Agent prefers it.

Can it do a full orbit? Short ones hold up best. Vizard Agent will say where invention takes over.

Why does it arrive with a wipe? Generated angle changes often include one. Vizard Agent removes it if you ask.

Can the subject move a little? Yes, if you tell Vizard Agent how. Unrequested movement is the problem, not movement.

What about the lighting? It can drift too. Vizard Agent checks it against the original frame.

Will it match my other cuts? If you say what they look like. Otherwise the new one has its own style.

Can it do a push instead of an orbit? Yes, and a push invents less because it stays on the same side.

What if the scene is complex? More to hold. Vizard Agent will tell you which parts it cannot lock.

Does this apply to live footage? No — there a camera move is a real reframe, which is a different job.

Can I see the still first? Yes, and approving the end frame before animating saves a round.

What about shadows on the ground? They should follow the camera, not the scene. Vizard Agent checks them.

How many attempts does it take? Usually two or three, each locking something the last one moved.