What the App Fills In Before You Type

A digital take record is not typed from scratch. SlateX can prefill or derive take number, shot number, reel and clip identifiers, sound roll, an initial timecode value, and part of a new camera record. The important distinction is that a value generated by a rule is a starting point, not a verified on-set fact.

Prefill answers “what goes in first,” not “has this value been confirmed?”

Take and shot numbers come from the existing structure

A new take number is based on the highest take number already present under the current shot, plus one. It is not based on the current count of records. If a take in the middle is deleted, a later take does not go back and fill that gap. The take record UI does not provide a manual take-number field.

Shot numbers are also generated from the active naming mode. The current modes belong to two families: one continues with alphabetic suffixes after the scene number, while the other uses a scene number with a hyphenated numeric suffix. This is a naming rule, not a judgment about what the next setup should be called. Shot management remains the place where a shot name can be reviewed or changed.

Generated numbering should not be read as a guarantee that the resulting identity is correct. Scene, shot, and take identities still need to be checked against the script and the day’s record, especially after deletions, renaming, or different record-creation paths.

Reel, clip, and sound-roll fields begin from fixed patterns

A camera reel is formed from the camera letter plus a three-digit zero-padded number, such as A001. Clip and sound-roll values use the same letter-plus-three-digit shape, for example C001 and S001. These patterns provide a consistent starting shape, but they do not prove that the media itself uses the same identifier.

In the new-take panel, when a camera is added, SlateX picks a currently unused camera letter and carries over only part of the prior camera state. Reel number, clip number, frame rate, shutter, white balance, and sound roll are in the inherited set. Lens, aperture, ISO, focus distance, composition fields, and VFX state are not simply copied as the same “add camera” package.

Continuation within the same shot and moving to another shot also do not use one identical inheritance rule. Some fields are retained or cleared depending on the record path and whether the shot is considered the same. Treat inherited values as draft context rather than proof that each field has been checked.

A manually created take starts with device clock time

When the new-take form opens without an existing timecode supplied to it, the initial value uses the device’s current hour, minute, and second, with the frame position fixed at 00. That value does not come automatically from a camera or external timecode chain, and its complete timecode appearance does not mean the frame position was verified.

This is a useful example of why “filled by software” and “observed on set” must stay separate. A complete-looking timecode can simply be the form’s initial value. Before saving, compare it with the actual record source. On receiving, compare delivered time values with the media or on-set record as well.

A populated field proves that something was written there; it does not prove that the source was correct.

Clip advancement depends on the creation path

Clip numbering is not governed by one global rule that says every new take advances the clip. Some recording paths advance the clip number in the project-level camera definition. Saving through another new-take path does not update that definition in the same way. Reusing the same camera definition can therefore produce a repeated draft clip number.

Reel behavior has a similar boundary. Its display follows the camera-letter plus number pattern, but whether the underlying number advances depends on the path and current state. A formatting rule must not be presented as verified media identity.

Recheck inherited values by source

Inheritance is useful as an entry point because frame rate, shutter, white balance, reel, clip, and sound roll may already have context from the prior record. Lens, aperture, ISO, focus distance, and composition do not follow the same rule in every path.

With multiple cameras, keep each camera record separate. Some shot-level settings can be overwritten during take creation by the last camera processed, while delivered files read the camera-level values. The value visible at shot level and the value exported for each camera are therefore not interchangeable concepts.

The practical question is not merely which fields already contain text. Ask where each value came from: numbering logic, inherited state, the device clock, or explicit on-set entry. Different sources require different verification.

Shooting-day assignment is a separate boundary

One more boundary has to remain separate from these prefill rules: shooting-day assignment is not written in the same way through every take-creation path. The presence of generated take, shot, reel, and camera values therefore must not be expanded into a claim that records can automatically be exported or summarized by shooting day. Verify whether the take actually has the relevant day assignment first.

FAQ

Does deleting a take cause the next take to fill the missing number?

No. A new take uses the highest existing take number under the shot plus one, so deleting a record in the middle does not make a later take reuse that gap.

If a new take already shows timecode, did it come from the on-set timecode source?

Not necessarily. When no timecode is supplied to the manual new-take form, it starts from the device clock’s hour, minute, and second and writes 00 in the frame position. Verify the actual source before relying on it.

Does adding a camera copy every parameter from the previous camera?

No. Reel, clip, frame rate, shutter, white balance, and sound roll are part of the carried state, while lens, aperture, ISO, focus distance, composition, and VFX state do not belong to the same direct inheritance set.

Does the clip number advance every time a take is created?

No. Advancement depends on the creation path. Some recording paths update the project-level camera definition; another new-take path does not update it in the same way. Compare the clip identifier with the media and the actual on-set record.

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