Description
Label a supplied utterance interval and calculate its duration.
Communication measurements depend on clock alignment, content units and interval boundaries. Pause time divided by word time differs from pause share of the whole interval, and touching time intervals have no positive overlap. Character budgets must state whether they count code points, code units or another measure.
Label a supplied utterance interval and calculate its duration.
When to use this tool
Use Utterance Onset Offset Timecode when you already have utteranceId, onsetSeconds, offsetSeconds and need to label a supplied utterance interval and calculate its duration.
How to use the tool and how it works
- Enter utteranceId, onsetSeconds, offsetSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read durationSeconds, timecodeToken. Use the output convention below.
Require utteranceId nonempty and offset>=onset; return offset-onset and JSON-array text [ID,onset,offset].1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| utteranceId | Utterance Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| onsetSeconds | Onset Seconds | Required. Finite number. |
| offsetSeconds | Offset Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| durationSeconds | Duration Seconds | Required. Finite number. |
| timecodeToken | Timecode Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"utteranceId": "U17",
"onsetSeconds": 12,
"offsetSeconds": 15
},
"output": {
"durationSeconds": 3,
"timecodeToken": "[\"U17\",12,15]"
}
}Limitations and assumptions
- Matching clocks and seconds are assumed. No speech, utterance boundary, transcript, speaker or actual timecode is detected or verified.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Inspect the original message, recording, transcript and timing or display specification. Use the complete analysis and audience context for communication outcomes; a local delay, overlap or length calculation does not measure comprehension, effectiveness or intent.
References
Similar or alternative tools
- Meeting Turn Queue Wait Duration
Measure a supplied queued turn's signed waiting interval.
- Conversation Repair Initiation Gap
Measure a supplied repair-initiation gap from a trouble marker.