Sume TTS Router output formats: WAV on Sonic, MP3 on Eleven

Sume's Sonic rows return mp3 or wav up to 48 kHz. Eleven rows return mp3 only, and three of them only mp3_44100_128. Pick by the format you need.

5 min readSume
All posts

If you need WAV from the Sume TTS Router, use a Sonic row. The catalog on main lists eight formats for Sonic (mp3 at 44.1 kHz in 192, 128, 96 and 64 kbps, mp3 22.05 kHz at 32 kbps, and wav at 48000, 44100 and 24000), while Eleven rows return mp3 only: v4 and v4 Turbo list six mp3 options, and Eleven v3, Multilingual v2 and Turbo v2.5 list only mp3_44100_128.

Source: packages/api-contract/src/tts-router-models.ts on origin/main b28f3b0 (read 2026-10-13).

Output formats by TTS Router row (read 2026-10-13)
RowsFormats
Sonic 3.6, 3.5, 3, latest, preview, 2, turbomp3_44100_192, mp3_44100_128, mp3_44100_96, mp3_44100_64, mp3_22050_32, wav_48000, wav_44100, wav_24000
Eleven v4, Eleven v4 Turbomp3_44100_192, _128, _96, _64, _32 and mp3_22050_32
Eleven v3, Multilingual v2, Turbo v2.5mp3_44100_128 only

Why does the container matter for lip sync?

Sume's timeline audio docs say mp3 adds priming padding again at every edge when files are joined, and recommend wav if you will join the file again or if the file drives lip sync. A Sonic wav also avoids a lossy step before a lip sync job, whose audio limit is 10 MB.

How do I ask for wav?

Send the structured output_format that TTS 1.0 already accepts. The catalog helper maps container: "wav" and sample_rate to ids such as wav_48000; a combination not listed for the model is refused.

curl -X POST https://api.sume.com/v1/tts-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: wav-line-001" \
  -d '{
    "model": "sonic-3.6",
    "transcript": "Free shipping this weekend only.",
    "voice": { "id": "YOUR_SONIC_VOICE_ID" },
    "output_format": { "container": "wav", "sample_rate": 48000 }
  }'

Sources

Related posts

More in Developers

All Developers posts

Written by Sume