cue

A word or syllable cue within a cueLine.
{
  "start": 2747,
  "end": 3018,
  "value": "눈",
  "byteStart": 0,
  "byteEnd": 2
}
<cue start="2747" end="3018" byteStart="0" byteEnd="2"></cue>
Does not exist.
Example with byte offsets

When untimed text appears between timed cues, byteStart and byteEnd disambiguate repeated tokens by pointing at the exact substring within the parent cueLine.value. For example, within cueLine.value = "Oh love love me tonight", the timed second love uses byteStart = 8 and byteEnd = 11:

{
  "start": 900,
  "end": 1300,
  "value": "love",
  "byteStart": 8,
  "byteEnd": 11
}
<cue start="900" end="1300" byteStart="8" byteEnd="11">love</cue>
Does not exist.
FieldTypeReq.OpenS.Details
startintegerYesYesStart time in milliseconds
endintegerNoYesEnd time in milliseconds. Within a cueLine, end must be either present on all cues or none. When the source provides partial end times, servers must fill missing values (e.g., using the next cue’s start, or the cueLine’s end for the final cue). When no cues have end times (e.g., Enhanced LRC with start-only timing), end is omitted from all cues. This is a documented contract rule; the OpenAPI schema does not enforce the all-or-none shape structurally
byteStartintegerYesYesZero-based inclusive UTF-8 byte offset into the parent cueLine.value where this cue begins
byteEndintegerYesYesZero-based inclusive UTF-8 byte offset into the parent cueLine.value where this cue ends
valuestringYesYesThe text of this word or syllable