Skip to content

Main content

Cue Pre Wait Post Wait Split Tool

Lay out a cue's explicit pre-wait, action and post-wait durations relative to cue trigger zero.

Loading tool…

Description

Return action start after pre-wait, action end after action duration, and the total including post-wait.

Performance timing can use clock labels, durations, cues, or frame counts. These are different coordinate systems, and a local time label alone does not determine a timezone-aware instant.

Return action start after pre-wait, action end after action duration, and the total including post-wait.

When to use this tool

Use Cue Pre Wait Post Wait Split when you need one cue, duration, or frame-based component under the stated time convention.

How to use the tool and how it works

  1. Enter preWaitSeconds, actionSeconds, postWaitSeconds. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read actionStartSeconds, actionEndSeconds, totalSeconds. Use the output convention below.

Require nonnegative preWaitSeconds, actionSeconds, and postWaitSeconds. Return action start after pre-wait, action end after action duration, and the total including post-wait.1

Input fieldMeaning and unitsAccepted input
preWaitSecondsPre Wait SecondsRequired. Finite number; minimum 0.
actionSecondsAction SecondsRequired. Finite number; minimum 0.
postWaitSecondsPost Wait SecondsRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
actionStartSecondsAction Start SecondsRequired. Finite number.
actionEndSecondsAction End SecondsRequired. Finite number.
totalSecondsTotal SecondsRequired. Finite number.
json
{
  "input": {
    "preWaitSeconds": 2,
    "actionSeconds": 5,
    "postWaitSeconds": 3
  },
  "output": {
    "actionStartSeconds": 2,
    "actionEndSeconds": 7,
    "totalSeconds": 10
  }
}

Limitations and assumptions

  • This models sequential intervals from time zero without overlapping actions, controller latency, or actual cue execution.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check the complete running order and the actual playback or clock system before coordinating an event.

References

  1. Calculation and input contract: performing-arts/cue-pre-wait-post-wait-split — tool.io

Similar or alternative tools