Caption Cue Single Line Join
Join physical cue text lines with an explicit separator while preserving leading/trailing empty lines and timing evidence.
Description
Join physical cue text lines with an explicit separator while preserving leading/trailing empty lines and timing evidence.
Caption line endings can be joined with a chosen separator while retaining cue timing and identity.
When to use this tool
Join physical cue text lines with an explicit separator while preserving leading/trailing empty lines and timing evidence.
- Prepare the supplied cuesJson, separator 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, separator. 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.cues. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Split each cue text on CRLF, CR or LF and join its lines with separator. Preserve ID, start and end.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 |
| separator | separator. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
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": "x",
"start": 0,
"end": 1,
"text": "a\nb"
}
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.cues | The cues list in the ordering and representation described above. |
{
"input": {
"cuesJson": "[{\"id\":\"x\",\"start\":0,\"end\":1,\"text\":\"a\\nb\"}]",
"separator": " "
},
"output": {
"result": {
"cues": [
{
"id": "x",
"start": 0,
"end": 1,
"text": "a b"
}
]
}
}
}Limitations and assumptions
- A separator containing a newline can still produce multiple lines. No markup removal, whitespace trimming or line-width optimization occurs.
- 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 Line Length Audit
Audit per-line UTF-16 cue lengths against an explicit limit, retaining cue/line indexes; does not count rendered glyph widths.
- Caption Adjacent Identical Merger
Merge adjacent sorted cues with exact identical text only when touching or overlapping; retain all contributing IDs.