Caption Cue Timestamp Millisecond Formatter
Format nonnegative integer caption milliseconds with a caller-selected decimal separator; no frame-rate or cue-file serialization.
Description
Format nonnegative integer caption milliseconds with a caller-selected decimal separator; no frame-rate or cue-file serialization.
Caption timestamps separate hours, minutes, seconds and milliseconds, with either comma or period before the fractional part.
When to use this tool
Format nonnegative integer caption milliseconds with a caller-selected decimal separator; no frame-rate or cue-file serialization.
- Prepare the supplied milliseconds, comma 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 milliseconds, comma. 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.timestamp. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require milliseconds from zero to one trillion. Split into components, pad hours to at least two digits, minutes/seconds to two and milliseconds to three, using comma when requested.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| milliseconds | milliseconds. | Integer from 0 to 1e12 inclusive |
| comma | Explicit choice for comma; supply a boolean rather than a text label. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.timestamp | The timestamp value under the stated formula or text convention. |
{
"input": {
"milliseconds": 3723004,
"comma": true
},
"output": {
"result": {
"timestamp": "01:02:03,004"
}
}
}Limitations and assumptions
- This is elapsed caption time, not a time of day. No frame-rate or subtitle-file serialization is performed.
- 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 Timestamp Millisecond Parser
Parse a strict caption HH:MM:SS.mmm or comma timestamp into integer milliseconds; hours may exceed 23, no sign or frame notation.
- Caption Adjacent Identical Merger
Merge adjacent sorted cues with exact identical text only when touching or overlapping; retain all contributing IDs.