Skip to content

Main content

Broadcast Slate Timing Segment Tool

Measure a broadcast slate segment from half-open absolute frame boundaries; no timecode drop-frame convention is inferred.

Loading tool…

Description

Subtract indices for durationFrames and divide by frame rate for durationSeconds.

Frame intervals distinguish inclusive frame labels from counts between boundaries. Transition sharing and rounding a duration can differ from rounding each endpoint independently.

Subtract indices for durationFrames and divide by frame rate for durationSeconds.

When to use this tool

Use Broadcast Slate Timing Segment when you need an explicit frame-boundary or duration-accounting step.

How to use the tool and how it works

  1. Enter slateStartFrames, slateEndFrames, framesPerSecond. 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 durationFrames, durationSeconds. Use the output convention below.

Require ordered nonnegative slate frame indices and positive framesPerSecond. Subtract indices for durationFrames and divide by frame rate for durationSeconds.1

Input fieldMeaning and unitsAccepted input
slateStartFramesSlate Start FramesRequired. Safe integer; minimum 0.
slateEndFramesSlate End FramesRequired. Safe integer.
framesPerSecondFrames Per SecondRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
durationFramesDuration FramesRequired. Safe integer.
durationSecondsDuration SecondsRequired. Finite number.
json
{
  "input": {
    "slateStartFrames": 100,
    "slateEndFrames": 175,
    "framesPerSecond": 25
  },
  "output": {
    "durationFrames": 75,
    "durationSeconds": 3
  }
}

Limitations and assumptions

  • Frames use an exclusive-end duration convention; no timecode parsing, drop-frame label handling, synchronization, or broadcast delivery requirement is validated.
  • 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

Use a consistent frame rate and timecode convention and inspect actual edit boundaries when frame accuracy matters.

References

  1. Calculation and input contract: communication/broadcast-slate-timing-segment — tool.io

Similar or alternative tools