blog/tutorials·Sep 27, 2026·7 min·by the eroq team

Continuity between shots: linked shots, cast, look and seed in Cinema

How Cinema keeps a film consistent from one shot to the next. Shots that continue from the previous shot's last frame or keep its scene from a new angle, character sheets as references, one look and one seed for the whole film.

The hardest thing about a generated film is not any one shot. It is the join between two shots: the coat that changes color, the room that gets a second window, the face that drifts. Every engine renders a clip in isolation, so continuity has to be built around the engine. Cinema stacks four layers to do it, and this guide is about what each one holds and where it stops.

Layer one: the links between shots

The strongest join is the one the engine cannot get wrong. In the Story, the line between two shots says how the second one is made. Click it and pick:

Continue the shot: the same shot goes on. Shot N+1 opens on the last frame of shot N's take in the cut.
Same scene, new angle: shot N's last frame rides as a reference picture, so the place, the people and the light carry over while the engine frames it anew.
Nothing (New shot): the shot renders on its own, its cast and elements by reference.

A new shot added inside a scene starts as Same scene, new angle on engines that read reference pictures; the first shot of a new scene starts on its own. The side panel can set every link of the film at once.

For a linked shot, Cinema does the hand-off itself:

When shot N has a take, the studio grabs its final frame right in the browser.
The frame is uploaded to your storage, in the Film frames folder.
It is sent as the start frame of shot N+1 (Continue the shot), or as a reference picture (Same scene, new angle).

A shot whose predecessor is still rendering shows waiting and starts as soon as the frame exists. If the previous take's link has expired, the studio re-signs it and tries again; if the frame genuinely cannot be grabbed, the shot renders fresh and says so in a note, rather than failing.

What Continue the shot buys you: the light, the set and the framing at the cut are identical, because they are the same pixels. What it does not buy you: a cut. It makes a long take, not a montage. When you want a hard cut (new location, new angle), use Same scene, new angle or a new shot, or write the shot so the first second is a move away from the frame (a whip pan, a push through a door).

Two rules keep the links honest:

Re-render shot N, or pick another of its takes, and shot N+1 is marked stale. Its take was built from a frame that no longer leads the cut. Re-render it or accept the join.
A link is inert where it cannot work: Continue the shot needs an engine that starts from a picture, Same scene, new angle one that reads reference pictures, and neither renders in the studio's private mode. The link says so on engines that cannot.

Price: a start frame bills as one frame on engines that price frames, and zero references; an angle adds the frame to the shot's reference pictures. The same arithmetic the server uses.

Layer two: the cast

Links hold the set. They do not hold a character who walks into frame in scene three. For that, the cast rides as references.

Add characters with Add character on a scene (they ride every shot of it) or on a single shot, or @mention them in the action. Each cast member's sheet — the reference picture from their character bible — is sent with the scene, and the engine prompt binds the name to the picture: "Mina (reference image 1)". Speakers of a shot's lines join its cast automatically; on engines that accept an audio reference (Seedance 2.x, Hailuo 3), the first voiced speaker's sample goes too, so the line comes out in their voice rather than one the engine invents. One catch: a shot linked with Continue the shot opens on a frame and sends no reference pictures or voice sample. Its cast carries over from the frame it opens on, and its voices ride as descriptors.

What a sheet holds: face, hair, build, the outfit on the sheet. What it does not: a change of outfit mid-film (make a second sheet), and — this is the important caveat — engines that read no references. Motion One, Motion Pro, Runway Gen-4.5, Grok Imagine, Veo 3.1 Lite and Hailuo 3 Max render from the prompt alone; on those the cast is redrawn every shot, and the Story warns you. If your film is about a face, pick an engine that reads references: the Seedance family, Kling 3.0, Hailuo 3, Veo 3.1, Wan 3.0. The character consistency guide compares them.

A character's persona (their personality, their speech) never rides a video prompt — only their age, gender and look. The engine renders a picture; it does not need to know how she argues.

Layer three: the look

Links and cast hold content. The look holds style: one engine, one frame format, one resolution, and the director's rack — film type, era, tempo, camera gear, lens, aperture, palette, lighting, plus a negative prompt. Set once in the film's settings, folded into every shot server-side as labelled sentences the engine reads the same way each time.

The look is why scene one and scene twelve cut together even when nothing else connects them. A film noir with an anamorphic lens at f/1.4 under practicals looks like that on every shot; nobody has to remember to write "neon noir" in scene nine. The director's rack guide explains the knobs.

Do not change the film's look mid-film unless you mean it (a night scene can use Override film settings for itself). Every scene rendered before the change now differs from every scene after, and Cinema will not re-render them for you — it marks nothing stale, because a look change is a decision, not an accident.

Layer four: the seed

A seed pins the engine's randomness. In the film's settings, one seed applies to every shot of the film on engines that honor it. Same seed, same prompt, same engine → the same clip, which is what you want when you fix a typo in scene four and re-render only that.

It is also the weakest layer. A seed does not make two different prompts render alike; it makes the same prompt render alike. Use it for reproducibility, not for continuity. The seeds and remix guide covers the arithmetic.

Putting the four together

A practical order, for a three-scene film:

Write the three scenes in the Story, cast in place, dialogue on the shot it belongs to.
Set the look. Pick an engine that reads references if the cast matters. Link the shots that should flow with Continue the shot.
Render scene one alone — one to four takes. Pick the best. This take's last frame is now the film's spine.
Render scenes two and three. Linked shots wait for the take before them. If two is right and three is not, re-render three; two does not move and you do not pay for it again.
Cut, add sound and titles, export.

Where continuity still breaks — a hand that changes, a prop that vanishes — the fix is the same as in any edit: cut around it. Trim the take, crossfade, or pick another take. The engine will not be perfect; the joins can be.

FAQ

Does Continue the shot work with every engine?

It needs an engine that starts from a picture: every video engine in Cinema. Same scene, new angle needs an engine that reads reference pictures: the Seedance family, Kling 3.0 and Pro, Veo 3.1 and Fast, Hailuo 3, Wan 3.0. Where the engine cannot, the shot renders on its own and says so.

Why is shot two "stale"?

Because shot one changed after shot two was rendered from it: a re-render or a different picked take. Shot two's take was built from a frame that is no longer the end of shot one. Re-render it, or keep it if the join still looks right.

Can a character keep the same voice across scenes?

On engines that take an audio reference (Seedance 2.x, Hailuo 3), yes — the character's voice sample goes with every scene where they speak. Elsewhere, the prompt carries a one-line voice descriptor and the engine does its best.