Scene, Shot, and Take Numbers Explained
Scene, shot, and take numbers identify three different layers. A scene number points the record back to a scene in the script. A shot number distinguishes a camera setup within that scene. A take number distinguishes repeated attempts under the same shot. SlateX follows the same hierarchy: scenes contain shots, and shots contain takes. These numbers should not be treated as one continuous counter because they answer different identity questions.
Scene asks “which scripted scene,” shot asks “which setup,” and take asks “which attempt under that setup.”
Scene number is script identity, but renaming it does not rewrite old shot numbers
The scene number belongs to the scene record and can be changed in scene management. One boundary matters immediately: changing the scene number does not automatically rename shot numbers that were already created.
If a scene was numbered 5 and existing shots were named in forms such as 5A or 5-1, changing the scene to another number leaves those existing shot strings intact. Later output that combines the new scene number with an old-prefixed shot can therefore expose the mismatch.
A scene-number change is not merely a cosmetic edit. After renaming a scene, review the shots already under it and decide whether their names still follow the intended convention.
Shot number identifies the setup and follows one of two built-in naming families
SlateX generates shot numbers from the current naming mode. The present modes belong to two families: a scene number followed by alphabetic suffixes, or a scene number followed by a hyphenated numeric suffix.
That naming mode belongs to the production, not to the device: the value is stored with the project’s own data, so opening the same production on another machine gives the same mode.
A shot number can be changed in shot management, but the take-record screen is not a direct shot-number entry field. The two available generation families should also not be described as an arbitrary custom naming system; they are the built-in modes currently provided.
Take number identifies repeated attempts; the app supplies the starting one
Take numbers default to app-generated and advance within each shot. The take-number field stays available on the create and edit screens, but they start from different values: create opens with an app-issued number, edit with the number that take already holds. Type a positive whole number and that value is recorded, and the next take continues from it; on the create path a blank or non-positive entry falls back to an app-issued number, while on the edit path it leaves the stored number untouched.
One consequence: deleting a take in the middle does not cause a later take to fill the missing number. The next number continues past the highest number already used, not from how many take records remain.
A take sequence therefore should not be promised to remain gap-free. The number is an identity within the shot, not a formatting exercise designed to keep every integer present.
A gap can remain. Preserving record identity matters more than making the numbers look continuous.
For why a deleted number is not reused, see “Why the Next Take Does Not Fill a Deleted Number”.
In multicamera records, take identity can match while camera identity stays separate
One take can contain several camera records. They can share the same scene, shot, and take identity because they belong to the same recorded attempt, while reel, clip, and camera identifiers remain separate for each camera.
During receiving, identical take numbers should not cause multiple camera rows to be collapsed into one media identity. Scene, shot, and take establish the record hierarchy; camera, reel, and clip continue the identification within that take.
Master and Coverage are derived from the shot-number shape
The current UI derives Master versus Coverage from whether the shot number contains a letter. A shot number with no letter follows one display path; a number containing a letter follows the other. The interface has no separate Master/Coverage selector.
Renaming a shot can therefore change the derived classification. Turning a non-letter form into a form that contains a letter can move it to the other grouping in the interface. It would be inaccurate to describe this as the user manually tagging a shot as Coverage.
One more boundary, with two sides: adding or editing a scene inside an episode does stop a repeated scene number — the form shows the error and the submit button stays disabled — while adding an episode runs no duplicate check on the episode number. When organising across entries or receiving a handoff, still look for repeated numbers and for historical names that no longer match a renamed scene.
FAQ
What do scene, shot, and take numbers each identify?
Scene identifies the scripted scene, shot identifies a setup within that scene, and take identifies a repeated attempt under the same shot. Together they form the record hierarchy.
Can a take number be edited manually?
Yes — the take-number field stays available on the create and edit screens: a positive whole number is recorded as typed and the next take continues from it. Create opens with an app-issued number, edit opens with the number that take already holds. On the create path a blank or non-positive entry falls back to an app-issued number; on the edit path it leaves the stored number untouched, so a gap left by a deleted take is not automatically reused.
Does the shot-naming mode travel to another device with the account?
It is not a device preference. The value lives in the production’s own data and travels with it, so opening the same production elsewhere gives the same mode — there is no second setting to verify on that machine.
Is Master or Coverage a type the user marks manually?
No. The interface has no such selector; it classifies from whether the shot number contains a letter, so changing the shot number itself can change the classification.
Axiom One LLC — SlateX