On-set Recording / W8 · Camera Parameters

Which Camera Parameters Carry Forward When You Add a Camera

Adding a camera in SlateX does not copy the previous camera’s entire parameter set. A new camera inherits reel number, clip number, frame rate, shutter, white balance, and sound roll. Lens, aperture, ISO, focus distance, composition fields, and VFX count are not inherited when the new camera is created. Camera model, resolution, aspect ratio, and LUT begin from empty defaults.

Inheritance is a field-copy rule. It does not prove that the copied values have been verified on set, and it should not be turned into a claim about faster entry or fewer errors.

The new camera ID uses the first unused letter

When a camera is added, the code looks for the first unused letter in the camera alphabet and assigns it as the new camera ID. If no unused letter is found, it falls back to the default camera ID. This defines how the identifier is chosen; it does not provide a custom camera-naming template.

Camera deletion also has a hard limit. The delete action is offered only when more than one camera remains, so the current form cannot be reduced to zero cameras. That rule controls the current camera set and should not be read as a statement that historical take snapshots are rewritten.

Parameters that carry forward

The new camera inherits reel number, clip number, frame rate, shutter, white balance, and sound roll from the previous camera. These values become initial fields in the new-camera draft. Whether they have already been committed still depends on the save path of the current screen.

This should not be described as automatic synchronization across all cameras. The code copies selected values at camera creation time; it does not create an ongoing linkage that keeps every camera parameter synchronized afterward.

Parameters that do not carry forward

Lens, aperture, ISO, focus distance, composition fields, and VFX count are not inherited for a newly added camera. Camera model, resolution, aspect ratio, and LUT also do not copy from the previous camera; they start from empty defaults.

A lens or aperture value on the previous camera therefore does not establish that a newly added camera receives the same value. If those parameters matter for the new camera, they need their own recorded values.

Adding a camera copies a defined subset of fields, not a complete camera-parameter snapshot.

The quick-capture path clears four composition fields

When a take is created through the quick-capture path, shot size, shot angle, movement, and focus distance are cleared. The mechanism does not claim to determine whether the shot has changed; it simply does not carry those four composition values through that creation path.

The shot-size vocabulary should not be described as a fixed enum either. The vocabulary can be edited by the user, so the supported statement is only that these fields are cleared on this path, not that they belong to a closed list of options.

Inheriting from the previous take depends on whether the shot is the same

A different path, inheriting from the previous take, first checks whether the new take is still on the same shot. For a continuation on the same shot, the composition-related state is retained, including focus distance. When the shot changes, focus distance is cleared while lens and aperture can remain.

This is easy to confuse with adding a camera. A new camera does not inherit lens and aperture from the previous camera, while a new take created from the previous take can retain those values under its own inheritance rules. They are separate mechanisms and should not be collapsed into a statement that lens and aperture always follow automatically.

What these rules establish

These code paths can establish which fields are copied, cleared, or initialized empty. They do not establish claims about reduced typing, faster work, or fewer errors, because the evidence is about field behavior rather than measured production outcomes.

The current evidence also does not support a custom default-parameter template for new cameras. Camera creation begins with the defined inheritance subset and the specified empty defaults.

FAQ

Which parameters are inherited when a camera is added?

Reel number, clip number, frame rate, shutter, white balance, and sound roll are copied as initial values for the new camera.

Do lens, aperture, and ISO carry over from the previous camera?

No. Those fields are not part of the new-camera inheritance set and need to be recorded for the new camera as needed.

Why can lens and aperture remain after changing shots in some workflows?

That behavior belongs to the separate “inherit from previous take” path. When the shot changes, focus distance is cleared while lens and aperture can remain. It is not the same mechanism as adding a camera.

Can all cameras be deleted from the current set?

No. The delete action is available only when more than one camera remains, so at least one camera is retained.


Axiom One LLC — SlateX. Figures current as of 24 September 2026.