The Camera as Interface

For most of film history the camera was a physical object in a physical space. You could walk around it, measure its distance to the subject, and know that the light hitting the sensor was the light in the room. That version of the camera is still the one that matters on a shoot day. It is no longer the only one that matters before the shoot day.

The page this replaces had that right, then sat Industrial Light & Magic's StageCraft and Unreal's in-camera VFX next to AIM camera-state language until CineForge started reading as a volume. I am separating the lots.

CineForge is staging with numbers. It is not Unreal. It is not an LED wall. It is the room where you place the camera so the angle is a choice, not a lottery.

Two different cameras

In virtual production, the camera is often a witness inside a built world — tracking, LED volume, real-time composite. The Mandalorian made that grammar famous. ILM's StageCraft pipeline, and the wider use of Unreal for in-camera VFX, made it practical at scale for high-end series. That is industry. It is real. It is not PREVIZ.

In previz, the camera is a computational object you author before anyone loads a truck. Position. Height. Lens. Target. A path you can return to. You can reset it. You can fork it. You can hand the same numbers to a different engine underneath. The lens is still a lens. The space it sees is blocked, not found, and not a volume we own.

If you collapse those two sentences into one, you get a pretty confusion: AIM as a stagecraft house. We are not. AIM World is the studio. Previz is the OS. CineForge is one of six rooms.

What changes for the director

The director's job used to be to choose a camera position and live with it. In a computational room the director has to choose a camera state and keep it. That is a different discipline.

Position is cheap. You can put a camera anywhere in a blocked set in seconds. The hard part is deciding why it belongs there.

Iteration is continuous. A shot can be revised without moving a dolly. The risk is that revision never stops. Director exists so someone can lock.

Coverage becomes generative. The same scene can yield wide, medium, and intimate versions from one intention. Each version still needs a decision about what matters in the frame. More cameras are not more directing.

The old page said the camera is no longer a witness, it is an argument the director makes in real time. I will keep the first half. I will not keep "in real time" if it sounds like Live. Live Director is a named mode inside Director, and it is off. The argument is made in the rooms, then locked. Not spoken into a stream.

Numbers, not adjectives

Power creatives do not think in prompts. They think in images. They think in rooms. CineForge exists because text cannot hold an angle. "Heroic low" is a wish. One-point-six meters, 32mm, looking at her hands, is a call.

When the camera is numbers, it inherits some habits of software. You can version a state. You can branch a take. You can roll back a bad move without rebuilding the set. That is useful. It is also how people start writing "scene graph" and "release artifact" until the sentence could have been copied off an Unreal production report.

At AIM, in CineForge, the camera state is the thing we write down so we can come back. Coordinates. Lens. Focus if we set it. The blocked set it was aimed at. Re-runs are not bit-identical. Outputs may vary. What should hold is the call: same path, same height, same woman in the glass. If the pixels drift and the face holds, you still have previz. If the file hashes and she is someone else, you have a checksum and no picture.

PREVIZ is six rooms. Infinitum. Script. Storyboard. Keyframe. CineForge. Director. Sequence is not a room. Infinitum is the talk-on-ramp — never Infiniti — and it sits beside the craft rooms, not above them. A camera decision in CineForge is already true in Director. That is the architecture. Not a volume. Not a live composite.

Where the craft lives

The craft does not move to the engineer. It moves to the person who can hold an intention across a thousand possible frames. The director, the DP, and the previz artist now share one question: what is the camera saying, and why does it stay that way?

Industry volume work answered that question with tracking and walls of light. Fine answer for that lot. Our answer is slower on purpose. Approve the still in Keyframe. Place the camera in CineForge. Generate the take in Director. Come back tomorrow. Same lens. Same path. Same face.

Nescafé Worthy Of is a Previz-blocked AIM production. Same woman. Same kitchen. The camera is not supposed to flinch while the interruption changes. That is a camera argument. It did not require a volume to be true. Sketchbook stays personal practice. ATRBUTE stays off this argument. If the credit is not printed, it does not get said.

The work

The camera is becoming an interface. That is a good thing for directors who know what they want, and a trap for directors who do not. The tool will not supply the point of view. It will only make the point of view easier to keep... if you keep it as numbers, in the room that owns numbers, and you do not confuse that room with someone else's stage.

AIM World is the studio. Previz is the OS. CineForge is not Unreal.

That's the work.