Caption Cue Line Length Audit
Audit per-line UTF-16 cue lengths against an explicit limit, retaining cue/line indexes; does not count rendered glyph widths.
Description
Audit per-line UTF-16 cue lengths against an explicit limit, retaining cue/line indexes; does not count rendered glyph widths.
Caption line-length limits need a stated character-count unit. This audit uses UTF-16 code-unit length.
When to use this tool
Audit per-line UTF-16 cue lengths against an explicit limit, retaining cue/line indexes; does not count rendered glyph widths.
- Prepare the supplied cuesJson, limit 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
- Enter cuesJson, limit. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.violations. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Split each cue text on standard CR/LF line endings. Report cueIndex, lineIndex and length for lines strictly longer than the supplied integer limit.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| cuesJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| limit | limit. | Integer from 0 to 8192 inclusive |
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.
[
{
"field": "cuesJson",
"decoded": [
{
"id": "a",
"start": 0,
"end": 4,
"text": "hi"
},
{
"id": "b",
"start": 3,
"end": 6,
"text": "hi"
}
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.violations | Source positions or records that fail the specific screen above; an empty list means no such violation. |
{
"input": {
"cuesJson": "[{\"id\":\"a\",\"start\":0,\"end\":4,\"text\":\"hi\"},{\"id\":\"b\",\"start\":3,\"end\":6,\"text\":\"hi\"}]",
"limit": 1
},
"output": {
"result": {
"violations": [
{
"cueIndex": 0,
"lineIndex": 0,
"length": 2
},
{
"cueIndex": 1,
"lineIndex": 0,
"length": 2
}
]
}
}
}Limitations and assumptions
- Equal-to-limit lines pass. Markup and escape syntax are counted literally; glyph width, grapheme count and reading speed are not measured.
- 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
Similar or alternative tools
- Caption Cue Single Line Join
Join physical cue text lines with an explicit separator while preserving leading/trailing empty lines and timing evidence.
- Caption Adjacent Identical Merger
Merge adjacent sorted cues with exact identical text only when touching or overlapping; retain all contributing IDs.