Why the Next Take Does Not Fill a Deleted Number
A take number is not a free-entry text field. When SlateX creates a take, it looks at the take numbers that already exist under the same shot, takes the maximum value, and adds 1; if that shot has no takes yet, numbering starts at 1. Because the rule uses the maximum number rather than the number of remaining records, deleting a take in the middle leaves a gap and the next take continues after the current maximum instead of going back to fill the hole.
Take numbers are generated as “maximum existing number + 1” within the same shot, so deletion leaves a gap instead of causing the next take to reuse the old number.
There is no user-entry field for the take number
The current interface displays “Take N,” but neither the create view nor the edit view provides a control for typing a take number. The number is written by the take-creation paths rather than by the user editing a numeric text field.
What the App Fills In Before You Type covers values the software provides before manual entry; the take number is one of the clearer examples. It therefore has only the generated path; there is no step where the user later corrects the number by hand.
A new number uses the maximum, not the remaining count
On normal creation, the app finds the highest existing take number for that shot and adds 1. Starting a recording uses the same rule. A separate Quick Shot path writes 1 only when that shot contains no take at all.
The important distinction is that “maximum + 1” is not “count + 1.” If a shot once had takes 1, 2, and 3, and take 2 is deleted, only two records remain but the maximum is still 3; the next take becomes 4 rather than becoming 3 again or filling 2.
The tradeoff is to leave a gap rather than reuse a lower number
This numbering rule can make the sequence look discontinuous, but it means a take created after deletion will not receive the same number as a take that may already have been handed off. The choice is to leave a missing number rather than fill the hole by reusing a lower number. This holds when a take in the middle is deleted: the rule reads the maximum among the takes that still exist, so deleting the current highest take means the next take takes that number again.
That does not mean take numbers stay continuous in actual shooting order. Deleting a take in the middle is what leaves a gap, so the receiver should treat the take number as an identity within one shot rather than treating “no missing numbers” as a correctness condition.
A deleted number remains a gap because later creation continues from the current maximum; the remaining record count does not trigger renumbering.
Hard boundary: take-number scope is one shot
The numbering scope is the shot. Different shots can each have take 1 and take 2, so the take number is not a project-wide or scene-wide independent identifier.
That distinction is also why Why the Same Takes Do Not Line Up Row-for-Row Across Handoff Files separates take numbers from file row numbers and ordering. A changed row order in a handoff file should not be read as evidence that take numbers have been renumbered; those are different mechanisms.
FAQ
Can the take number be edited manually?
There is no current take-number input control. The interface displays the number, but create and edit views do not provide a path for directly typing or changing it.
If take 2 is deleted, will the next take become take 2?
No. The next number is the current maximum within the shot plus 1, so the middle gap remains.
Why not use the number of remaining takes plus 1?
The remaining count shrinks after deletion, while the maximum number still shows how far numbering has progressed. The current rule continues after that maximum.
Can two different shots both have take 1?
Yes. The numbering scope is one shot, so the take number should not be treated as a project-wide identifier.
Axiom One LLC — SlateX. Figures current as of 24 September 2026.