<break> tags to insert an explicit silence at a specific point —
before a verification code, between list items, or wherever punctuation alone
doesn’t give you the pause you want.
Syntax
| Form | Meaning |
|---|---|
<break time="300ms"/> | Explicit duration in milliseconds |
<break time="1.5s"/> | Explicit duration in seconds (decimals allowed) |
<break strength="medium"/> | SSML strength preset (none, x-weak, weak, medium, strong, x-strong) |
<break/> | Default pause (200 ms) |
<break/>) and explicit-close forms are accepted;
attribute values may use single or double quotes.
Durations are snapped
The model is trained on three discrete pause lengths: 200 ms, 400 ms, and 500 ms. Whatever you request is snapped to the nearest trained value (ties resolve to the longer pause), so the effective pauses are:| You write | You get |
|---|---|
time="100ms" … time="300ms" | 200 ms (300 ms ties → 400 ms) |
time="350ms" … time="450ms" | 400 ms (450 ms ties → 500 ms) |
time="460ms" and up | 500 ms |
strength="x-weak" / "weak" / "medium" | 200 ms |
strength="strong" / "x-strong" | 500 ms |
strength="none" | no pause inserted (not snapped up) |
<break time="500ms"/><break time="500ms"/> ≈ 1 s.
Example
- Python
- JavaScript
- cURL
Notes & limits
- Breaks survive normalization. The text around a break is normalized
independently and the pause is re-inserted afterwards, so
normalize: trueand break tags compose. - Model support:
kugel-3supports break tags (see Models). On models without break support the tags are stripped and synthesis continues without the pause. - Punctuation first. For natural rhythm, commas/periods/ellipses are usually better — see Punctuation as pacing. Breaks are for deliberate silences of a specific length.
- Inside
<spell>blocks, don’t place break tags — use the spell tag’sgroupattribute for paced codes instead.