Skip to content

Main content

Shot Transition Frame Boundary Tool

Inclusive endpoint frame accounting with an explicit shared-transition-frame correction.

Loading tool…

Description

Subtract lastFirstShot and one from firstSecondShot, then subtract transitionFrames and add sharedFrames for unassignedGap.

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

Subtract lastFirstShot and one from firstSecondShot, then subtract transitionFrames and add sharedFrames for unassignedGap.

When to use this tool

Use Shot Transition Frame Boundary when you need an explicit frame-boundary or duration-accounting step.

How to use the tool and how it works

  1. Enter lastFirstShot, firstSecondShot, transitionFrames, sharedFrames. 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 unassignedGap. Use the output convention below.

Subtract lastFirstShot and one from firstSecondShot, then subtract transitionFrames and add sharedFrames for unassignedGap.1

Input fieldMeaning and unitsAccepted input
lastFirstShotLast First ShotRequired. Safe integer; minimum 0.
firstSecondShotFirst Second ShotRequired. Safe integer.
transitionFramesTransition FramesRequired. Safe integer; minimum 0.
sharedFramesShared FramesRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
unassignedGapUnassigned GapRequired. Safe integer.
json
{
  "input": {
    "lastFirstShot": 100,
    "firstSecondShot": 106,
    "transitionFrames": 5,
    "sharedFrames": 0
  },
  "output": {
    "unassignedGap": 0
  }
}

Limitations and assumptions

  • The supplied boundary convention permits negative gaps; transitions and shared frames are not detected from media.
  • 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: media-studies/shot-transition-frame-boundary — tool.io

Similar or alternative tools

  • Shot Change Frame Gap

    Return nextFirstFrame - previousLastFrame as frameGap and max(0, frameGap - 1) as omittedFrames.

  • Broadcast Boundary Frame Rounding Gap

    Multiply endSeconds - startSeconds by framesPerSecond, round its frame count using floor, ceil, or nearest, and divide back to seconds.