Caption Cue Gap Table

Report signed adjacent caption timing gaps in sorted start order; negative gaps retain overlap evidence.

Description

Report signed adjacent caption timing gaps in sorted start order; negative gaps retain overlap evidence.

A signed gap between neighboring cues can be negative when their intervals overlap.

When to use this tool

Report signed adjacent caption timing gaps in sorted start order; negative gaps retain overlap evidence.

  • Prepare the supplied cuesJson fields for this operation.
  • Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

  1. Enter cuesJson. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.gaps. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require nondecreasing starts and return each next start minus the preceding cue's end, with fromId and toId.1

Input fieldMeaning and representationAccepted input
cuesJsonJSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file.Text

For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.

json
[
  {
    "field": "cuesJson",
    "decoded": [
      {
        "id": "a",
        "start": 0,
        "end": 4,
        "text": "hi"
      },
      {
        "id": "b",
        "start": 3,
        "end": 6,
        "text": "hi"
      }
    ]
  }
]
Output fieldInterpretation
resultObject containing the named outputs below.
result.gapsThe gaps list in the ordering and representation described above.
json
{
  "input": {
    "cuesJson": "[{\"id\":\"a\",\"start\":0,\"end\":4,\"text\":\"hi\"},{\"id\":\"b\",\"start\":3,\"end\":6,\"text\":\"hi\"}]"
  },
  "output": {
    "result": {
      "gaps": [
        {
          "fromId": "a",
          "toId": "b",
          "gap": -1
        }
      ]
    }
  }
}

Limitations and assumptions

  • This compares immediate neighbors only, not a cumulative occupied-time union. A long earlier cue can overlap farther cues without being their direct predecessor.
  • Input cue records contain string id/text and integer millisecond start/end from zero to one trillion, with end at least start. At most 128 cue records are accepted; IDs need not be unique.
  • Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
  • Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
  • Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Use a subtitle-format parser or media review for markup, file syntax and synchronization. Preserve the integer-millisecond timeline and the stated overlap or clipping convention when composing these operations.

References

  1. Tool behavior and example: Caption Cue Gap Table — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies