# 15. Preserve Characters, Objects, and Space between Shots

Not every first video needs this lesson. For one short clip with one action, the main course route is usually enough.

But when a character returns in the next shot, a cup has moved, the camera suddenly looks from the other side of the room, and a jacket has dried between cuts, connected production begins.

Here, you will build a small continuity system for two connected shots. Its job is to stop characters, locations, props, and their states from being reinvented after the edit.

```learner-callout
{"stable_id":"aiv-c160-continuity-is-memory","role":"key-point","title":"Continuity is memory between shots","body":"Record how a shot begins, what changes in it, and how it ends. The next shot’s entry should inherit that exit instead of starting the story again."}
```

Records help plan the connection. Only the actual generated frames and edit can prove that it held.

## Minimum Input: Two Shots and One Simple Map

For independent practice, you need two timing rows, accepted character and prop files, and a simple diagram of where the characters, prop, and camera stand. The smallest useful result is a scene map and two shot records whose first exit becomes the second entry.

The **line of action** is an imaginary line between interacting characters or along the main movement. While the camera remains on one side, screen directions stay consistent: a character who looked right does not suddenly look the opposite way after a cut.

```learner-callout
{"stable_id":"aiv-c160-line-of-action","role":"technique","title":"Keep the camera side","body":"Before the second shot, mark the line of action and the camera side. The new angle may become tighter, but it should not silently reverse positions, eyelines, or the direction of action."}
```

### Two-shot practice example

| Field | Shot 1 | Shot 2 |
| --- | --- | --- |
| Timing | 00:00–00:02: the man places the cup | 00:02–00:04: he answers after a pause |
| Main identity file | `HERO-A-front.png` controls the face and gray jacket | Same file |
| Geometry | Man right, woman left, camera on the window side | Camera side and eyeline directions do not change |
| Entry | Cup in the right hand | Cup already stands on the table to his right |
| Action | Hand lowers the cup onto the table | Gaze stays on the woman; the answer begins |
| Exit | Hand has released the cup | Answer ends; cup remains on the table |

Use this practice example if you do not yet have inputs of your own. If you do, do not invent a missing frame or reference: prepare and accept the missing file first.

## When Connected-Scene Control Is Needed

Use this layer when at least one real dependency exists: a character appears in several scenes, a location is seen from different sides, a prop changes in a story-relevant way, an outfit or water/dirt trace must persist, dialogue continues across angles, or the edit depends on matching entry and exit states.

Duration alone decides nothing. A fifteen-second scene with two characters, a door, and a cup can need more control than a minute-long landscape with no recurring object.

Connected production is not a method for making everything harder. It is memory used where neighboring shots depend on one another.

## Four Kinds of Project Memory

You do not need to put all this information into every prompt. Store it first in a project map, then move only what affects the current shot into that shot.

| Layer | Main question |
| --- | --- |
| Project | What world is this, and which general rules govern the video? |
| Recurring materials | Who and what must remain recognisable? |
| Scene | Where is everything, and in which state does it enter the scene? |
| Shot | What is visible, happens, and changes now? |

```learner-callout
{"stable_id":"aiv-c160-current-shot-scope","role":"observation","title":"A shot does not need the whole project encyclopedia","body":"The map holds the world, identities, states, and geography. Move into the current shot record only what the viewer must see now and what must survive the cut."}
```

## Project Material: Appearance, Version, and State

A recurring character or prop is more than an image. Its working identity combines a clear description, an actual visual reference, a version, and a state history.

“A character in a gray jacket” is not enough for a connected scene. Preserve the face, proportions, notable details, base costume, selected images, and allowed states.

Keep the accepted base appearance. If the character needs a wet jacket, damaged sleeve, or another object in hand, create a separate state rather than running a strong source through endless global regenerations. After several rounds, a familiar character can easily become a distant relative.

| Object | State | What changed | What stayed the same |
| --- | --- | --- | --- |
| HERO-A | BASE | Nothing | Face, build, jacket |
| HERO-A | WET | Wet hair and fabric | Face, cut, clothing color |
| PROP-MUG | FULL | The cup contains coffee | Shape, color, logo |
| PROP-MUG | EMPTY | The liquid is absent | Shape, color, logo |

```learner-callout
{"stable_id":"aiv-c160-state-lineage","role":"caution","title":"Do not break the accepted base appearance","body":"For a controlled change, create and name a new state variant, preserve the source, and do not activate states that contradict one another in the same shot."}
```

## Location and Scene Record

A room reference can preserve architecture, materials, landmarks, and lighting direction, but it does not decide where the camera looks from in a new shot. For a recurring location, record fixed landmarks—door, window, table, stairs—character and important prop positions, line of action, camera side, eyelines, light, and the scene’s entry and exit state.

A separate geometry map is unnecessary for one simple isolated shot. Use it when the space must survive an edit.

A scene record is memory of the current state, not a large encyclopedia. Copy it for your scene.

```template
Scene:
Active characters and objects:
Location and fixed landmarks:
Time / weather / lighting:
Camera side and line of action:
Entry state:
What changes in the scene:
Exit state:
What must carry into the next scene:
```

The final three lines matter most: they connect shots causally, not only visually.

## Two Connected Shots

Scene: a woman questions a man at a kitchen table. He holds a full cup of coffee in his right hand.

In the first shot, the camera stays on the window side. The woman asks a question, the man holds the cup in his right hand, and at the end he places it on the table to his right. In the second shot, the camera moves closer without crossing the line of action; the cup stays on the right and now stands on the table, the right hand is free, and the man answers after a short pause. The woman remains off-screen left—her line preserves the direction of his gaze.

```learner-callout
{"stable_id":"aiv-c160-exit-to-entry","role":"inference","title":"Look for the missing exit state","body":"If the second shot puts the cup back in the hand, the problem may not be the model. First check whether the second record inherited the first shot’s recorded exit."}
```

## One Take or Several Shots

One continuous take works when one physically possible camera can show one action without hidden editing. Use several shots when place or time changes, a reaction needs its own angle, an important detail is unreadable in the wide view, the camera would need an impossible path, or separation makes generation and editing easier.

Do not treat one continuous take as mandatory proof of being “cinematic.” Sometimes the strongest editing decision is to split the task honestly into two simple shots.

## Iterate without Losing Memory

When a frame fails, change one meaningful variable and record it. After repeated failure, do not inflate the description: split the shot, remove one action, change the angle, prepare a stronger input, or move the effect into editing.

```template
Shot:
Version:
What changed:
Why:
What must remain unchanged:
Result:
Next action:
```

---

## Practice: Two Shots, One Memory

Choose a short scene with two characters and one prop.

1. Create records for both characters and the prop, including versions and current states.
2. Draw a simple location map with the line of action.
3. Record the first shot’s entry and exit states.
4. Build the second shot record from the first shot’s exit.
5. Mark what is visible, cropped, off-screen, and genuinely gone from the world.

```learner-callout
{"stable_id":"aiv-c160-two-shot-practice","role":"practice","title":"Build a two-shot plan","body":"Do not generate the second shot from memory. Before it, transfer the necessary identities, states, geography, and the first shot’s exit into the record."}
```

### Plan Check

Check that face, outfit, and prop use the same primary files and versions; the prop’s entry matches the previous shot’s exit; eyelines match character positions; the camera does not invisibly cross the axis; the second shot starts where the first ends; and its description contains only the information needed for that shot.

### Actual-Frame Check

If the frames exist, open both files beside each other and compare face, outfit, cup, eyelines, and camera side. Record the filenames and one visible defect. Correct one connection and compare again.

```learner-callout
{"stable_id":"aiv-c160-continuity-check","role":"checkpoint","title":"A plan does not prove a match","body":"Without generated frames, the result status is “continuity planned,” not “continuity confirmed.” When frames exist, confirm the connection by comparing the actual files after one corrected variable."}
```

**Takeaway:** you now have a continuity record, scene map, and two connected shot records. The next step is to describe observable performance and voice for them.