Caption Cue Timing Fingerprint
Serialize ordered cue timing pairs as an exact noncryptographic fingerprint; excludes IDs/text and is not a collision-resistant hash.
Description
Serialize ordered cue timing pairs as an exact noncryptographic fingerprint; excludes IDs/text and is not a collision-resistant hash.
A timing fingerprint can compare ordered cue boundaries while intentionally ignoring text and IDs.
When to use this tool
Serialize ordered cue timing pairs as an exact noncryptographic fingerprint; excludes IDs/text and is not a collision-resistant hash.
- 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
- Enter cuesJson. 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.fingerprint. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Serialize the supplied ordered [start,end] pairs as compact JSON and return fingerprint.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 |
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.fingerprint | Compact JSON serialization of ordered timing pairs; not a cryptographic hash. |
{
"input": {
"cuesJson": "[{\"id\":\"a\",\"start\":0,\"end\":4,\"text\":\"hi\"},{\"id\":\"b\",\"start\":3,\"end\":6,\"text\":\"hi\"}]"
},
"output": {
"result": {
"fingerprint": "[[0,4],[3,6]]"
}
}
}Limitations and assumptions
- This is deterministic serialization, not a cryptographic hash. Cue order matters, while differing text and IDs can produce the same fingerprint.
- 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 Adjacent Identical Merger
Merge adjacent sorted cues with exact identical text only when touching or overlapping; retain all contributing IDs.
- Caption Cue Centered Gap Placement
Center an integer-duration caption inside a supplied gap; odd leftover milliseconds place the extra millisecond on the right.