On-set Recording / W4.1 · One Scene, Two Days

Why One Scene Cannot Sit on Two Shooting Days at Once

SlateX currently constrains a scene-to-shooting-day relationship so that a scene can belong to only one shooting day at a time. Moving a scene from the first day to the second is therefore not “adding another day”; the existing schedule relationship has to be removed before the scene is assigned to the new day. That rule keeps one scene’s schedule on a single day. Take records are not under that limit: every take carries its own shooting day — the day in use when the take is created, changeable on the take’s Shooting Day row — so a scene shot across two days keeps its takes on their respective days. What does not exist is a schedule state joining one scene to two days at once, not those two days of records, and this view is not where one scene totals across days.

In the schedule layer a scene belongs to only one shooting day at a time; changing days means removing the old relationship and assigning a new one, not stacking another date onto the same scene. Each take carries its own day, so shooting one scene on two days is not a contradiction.

A scene that is already scheduled does not appear in this picker

In the step where this app assigns scenes to a shooting day, the list first filters out every scene that already has a shooting day. An already scheduled scene is therefore not shown disabled or greyed out; it is absent from the selectable list. To move it to another day, the existing relationship must first be removed so that the scene can return to the available set.

“Scene picker” here refers only to this scheduling step inside the app, not to a fixed industry term. The app has other interfaces with similar picker naming but different meanings, so the behavior of this one should not be generalized to every place where a scene is selected.

Search uses scene number and scene name only

In this scheduling picker, search matches the scene number and scene name. It does not search the summary. If the only phrase you remember appears in a scene summary, this step will not surface the scene because of that summary text.

The grouping key and the displayed group name also come from two different places: grouping follows the scene’s episode number, where an unset episode is treated as episode 1 and therefore lands in the first group, while the label uses that episode’s name and falls back to a generated “Episode N” when no name is set, the label being set by the first scene that enters the group. Because they come from separate places, the grouping and the label should not be assumed to show the same latest value in every case.

Confirmation assigns each scene and then saves once

On confirmation, the selected scenes are assigned to the target shooting day and then saved together. The picker closes only after the save succeeds; if the save does not succeed, the picker stays open.

What can be stated here is only the relationship between saving and dismissal: either the save succeeds and the picker closes, or it does not and the picker stays open. No claim about partial success can be made. To determine the actual saved result, the receiver should check the scene’s current shooting-day assignment in the interface.

Hard boundary: a two-day shoot is not one cross-day scene record here

Because one scene can belong to only one shooting day at a time, the same scene record cannot sit under day one and day two simultaneously. When a real shoot splits one scene across two days, the schedule is still one day at a time and this view offers no cross-day total; seeing the scene on another day should not be read as the app maintaining one unified schedule across both days. Keep the two layers apart: takes keep their own day, and what is missing is the relationship that would merge two days into one.

What a Take Record Needs for Handoff covers what belongs in an individual take record, while Which Camera Parameters Carry Forward When You Add a Camera covers camera inheritance. Neither changes the one-scene-at-one-time scheduling limit described here.

The schedule relationship has no state for “one scene attached to two days at once”; takes carry their own days, and merging two days into one total is not something this view provides.

FAQ

If a scene is already scheduled on day one, can it be selected again on day two immediately?

Not in this step. A scheduled scene is absent from the selectable list until its existing shooting-day relationship is removed.

Does the search box search the scene summary?

No. Search here matches only scene number and scene name, not the summary.

What happens if saving does not succeed?

The picker closes only after a successful save; if saving does not succeed, it stays open. A more specific claim about alert behavior has no checkable basis.

Does this view aggregate one scene across two shooting days?

Not as a cross-day aggregation tool. One scene’s schedule holds a single shooting day at a time, while the takes shot on both days each carry their own day — check them day by day, because nothing here merges the two into one total.


Axiom One LLC — SlateX