EAS Cut-In Runtime
Budget an emergency-alert cut-in against a caller-supplied runtime.
Description
An emergency cut-in runtime budget sums four supplied components.
An emergency cut-in runtime budget sums four supplied components. Its margin is maximum runtime minus the total.1
Budget an emergency-alert cut-in against a caller-supplied runtime.
When to use EAS Cut-In Runtime
Use this tool to budget an emergency-alert cut-in against a caller-supplied runtime.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use EAS Cut-In Runtime and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter introSeconds, messageSeconds, translationSeconds, outroSeconds, maximumRuntimeSeconds using the field table and calculation rules, then run the tool.
- Read totalRuntimeSeconds, remainingSeconds, withinRuntime. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| introSeconds | Cut-in introduction (s) | number; minimum: 0 | Required |
| messageSeconds | Alert message (s) | number; minimum: 0 | Required |
| translationSeconds | Translation or accessibility audio (s) | number; minimum: 0 | Required |
| outroSeconds | Cut-in close (s) | number; minimum: 0 | Required |
| maximumRuntimeSeconds | Maximum runtime (s) | number; minimum: 0 | Required |
Enter nonnegative component/max seconds. Return total, signed remaining time and inclusive fit flag.
total=ΣfourDurations; remaining=maximum−total Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| totalRuntimeSeconds | Total cut-in runtime (s) | number; minimum: 0 |
| remainingSeconds | Runtime margin (s) | number |
| withinRuntime | Within supplied runtime | boolean |
{
"input": {
"introSeconds": 5,
"messageSeconds": 30,
"translationSeconds": 20,
"outroSeconds": 5,
"maximumRuntimeSeconds": 60
},
"output": {
"totalRuntimeSeconds": 60,
"remainingSeconds": 0,
"withinRuntime": true
}
}Limitations and assumptions
No broadcast file, alert validity, legal requirement or transmission behavior is checked.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Package Runtime: Total broadcast package elements against a runtime limit. For a complementary task, use Tease Length: Check tease copy against character and spoken-runtime limits.
References
-
EAS Cut-In Runtime — tool.io
Similar or alternative tools
- Package Runtime
Total broadcast package elements against a runtime limit.
- Tease Length
Check tease copy against character and spoken-runtime limits.