Where Reel Names Like A001 Come From—and Why the Prefix Follows the Camera
A reel name such as A001 is not stored as one free-form string. Its current display shape is built from a camera-letter prefix plus a three-digit zero-padded number: the prefix follows the camera identifier and the numeric part comes from the reel number. Because the displayed name is derived, the user cannot turn this field into an arbitrary complete card-name string; the editable part is the number, not the entire naming format.
The displayed reel name is derived as “camera prefix + three-digit number,” rather than being a free-entry field for an arbitrary full card name.
The prefix follows the camera and the number is padded to three digits
The shared display rule places the camera identifier first and formats the reel number to three digits. If the camera prefix is A and the value is 1, the result is A001. A different camera changes the prefix while the numeric value is still formatted through the same three-digit rule.
That is why the reel value described in What the App Fills In Before You Type keeps the same shape across views: those views follow this one formatting rule instead of maintaining separate free-text reel names.
The two input paths treat 0 differently
The camera-parameter form on the create and edit take views allows the numeric part to be cleared. Clearing the field displays an empty string but stores the numeric value as 0, so once the take does have a camera, the exported value is a shape such as A000 (with no camera attached, the export falls back to a different value). The minimum reel number is therefore not always 1: this form path explicitly permits 0.
The camera-parameter toolbar applies a different constraint: both increment/decrement controls and manual entry clamp the number to the range from 1 through 999. The two paths address the same reel number but do not share the same input boundary: the same cell can be 0 on the form side and cannot be 0 on the toolbar side.
Input keeps digits only and stops at three digits
Both paths filter out non-digit characters and keep only the first three digits. Letters, spaces, and underscores therefore cannot enter the numeric part through either field. The camera letter is supplied by the camera identifier rather than typed together with the reel number.
An older free-text reel-name column is cleared when the value is changed on the toolbar side and when a camera is created, and it has no dependable read/write path in the current flow. It should not be treated as an alternative custom naming method; the column still existing does not by itself make it usable.
Hard boundary: the full card-name format is not customizable
The current display rule only combines a camera prefix with a zero-padded number. It does not support replacing the complete reel name with an unprefixed free-form string, nor does it support shapes such as B002_R1 with an additional suffix. The checkable statement is the derivation rule itself; arbitrary card naming is outside this capability.
Where Each ALE Column Comes From also describes the handoff side as reading this derived reel value. If a receiver needs to compare it against a media card or an import template, the actual exported value should be checked field by field instead of assuming that any on-set card name can be carried through unchanged.
The current reel name is limited to a camera prefix plus a three-digit number; free-form card names and additional suffix formats are outside this path.
FAQ
Is the A in A001 typed as part of the reel number?
Not as part of the numeric input. The prefix comes from the camera identifier, and the number is then zero-padded to three digits after it.
Can the reel number be 0?
The camera-parameter form can be cleared, which stores 0, so an exported row for a take that has a camera shows A000; the toolbar path instead clamps entry from 1 through 999.
Can I enter a complete card name such as B002_R1?
The current reel input keeps digits only and limits them to three positions before the camera prefix is added, so an extra-suffix free-form shape is outside this path.
Can the older free-text reel-name column be used as a backup input?
It should not be treated as a current input capability. That column is cleared on toolbar-side changes and when a camera is created, and it has no dependable read/write path in the current flow.
Axiom One LLC — SlateX. Figures current as of 24 September 2026.