Breaks

Your total is <break time="400ms"/> forty-two euros.

​

Syntax

​

Durations are snapped

​

Example

audio = client.tts.generate(
    text='Welcome to KugelAudio. <break time="400ms"/> How can I help you today?',
    model_id="kugel-3",
    voice_id=1071,
    language="en",
)

const audio = await client.tts.generate({
  text: 'Welcome to KugelAudio. <break time="400ms"/> How can I help you today?',
  modelId: 'kugel-3',
  voiceId: 1071,
  language: 'en',
});

curl -X POST https://api.kugelaudio.com/v1/tts/generate \
  -H "Authorization: Bearer $KUGELAUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Welcome to KugelAudio. <break time=\"400ms\"/> How can I help you today?",
    "model_id": "kugel-3",
    "voice_id": 1071,
    "language": "en"
  }' \
  --output output.pcm

​

Notes & limits

• Breaks survive normalization. The text around a break is normalized independently and the pause is re-inserted afterwards, so normalize: true and break tags compose.
• Model support: kugel-3 supports 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’s group attribute for paced codes instead.