Description
Sum nonnegative integer segmentFrames with exact integers and subtract excludedFrames from positive programFrames for eligibleFrames.
Frame intervals distinguish inclusive frame labels from counts between boundaries. Transition sharing and rounding a duration can differ from rounding each endpoint independently.
Sum nonnegative integer segmentFrames with exact integers and subtract excludedFrames from positive programFrames for eligibleFrames.
When to use this tool
Use Broadcast Segment Frame Share when you need an explicit frame-boundary or duration-accounting step.
How to use the tool and how it works
- Enter segmentFrames, programFrames, excludedFrames. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read segmentSumDecimal, eligibleFrames, share. Use the output convention below.
Sum nonnegative integer segmentFrames with exact integers and subtract excludedFrames from positive programFrames for eligibleFrames. Require the sum within eligible frames and divide for share.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| segmentFrames | Segment Frames | Required. Array of safe integer; minimum 0; maximum items 256. |
| programFrames | Program Frames | Required. Safe integer; minimum 1. |
| excludedFrames | Excluded Frames | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| segmentSumDecimal | Segment Sum Decimal | Required. Text; maximum UTF-16 length 8192. |
| eligibleFrames | Eligible Frames | Required. Safe integer. |
| share | Dimensionless fraction under the stated denominator policy. | Required. Finite number. |
{
"input": {
"segmentFrames": [
10,
20
],
"programFrames": 100,
"excludedFrames": 25
},
"output": {
"segmentSumDecimal": "30",
"eligibleFrames": 75,
"share": 0.4
}
}Limitations and assumptions
- Segments must already be nonoverlapping under the chosen count convention; the tool does not detect duplicate frame coverage.
- 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
Similar or alternative tools
- Shot Duration Proportion
Use sequenceDuration or sequenceDuration - excludedDuration as denominator according to excludeMarked, then divide shotDuration by it.
- Shot Transition Frame Boundary
Subtract lastFirstShot and one from firstSecondShot, then subtract transitionFrames and add sharedFrames for unassignedGap.