Speech-to-text audio too large? Sume STT takes up to 10 MB, hosted
Sume's stt_create needs a public HTTPS audio URL on the Sume media host, 10 MB at most. What fits: 16 kHz mono wav versus mp3, and how to cut a long file.

Sume's stt_create tool takes a public HTTPS audio_url, preferably on the Sume media host, and the tool schema caps the file at 10 MB; a non-Sume host fails with unsupported_audio_source. A 16 kHz mono 16-bit wav is about 32 KB per second, so 10 MB holds a little over five minutes of wav, and roughly twice that as 128 kbps mp3. The words always come back in words[], and speech-to-text is listed at $0.01 per audio minute in the catalog.
Size by format
Sume's audio detach guide calls 16000 plus channels: "mono" the speech-to-text shape and says the default wav is pcm_s16le. That is 16,000 samples a second at 2 bytes each. Its mp3 option is 128 kbps, which is 16,000 bytes a second. These are calculated from those published figures, not measured.
| Format | Bytes per second | Approximate length in 10 MB |
|---|---|---|
| wav, 16 kHz mono, 16-bit | 32,000 | About 5 minutes |
| mp3, 128 kbps | 16,000 | About 10 minutes |
| wav, 48 kHz stereo, 16-bit | 192,000 | About 52 seconds |
Cutting a long recording
Detach the audio of a long video once, then split it into ranges with timeline audio, which returns up to 20 ranges per job at $0.01 per job and keeps each as its own durable file. Transcribe each range separately and add the range's start time to its word times when you stitch the results back together.
Audio detach itself returns at most 900 seconds per job, so a recording longer than 15 minutes needs a range anyway.
Sources
Related posts
More in Developers
- SSML in text to speech: Sume takes a plain transcript, no ssml field
Does Sume's text to speech accept SSML? The tts_create body has a plain transcript and rejects unknown keys. What to use for speed, volume, emotion and pauses.
- Sume API rate limits by plan: requests per minute for writes and reads
Sume gives every API key a per-minute budget set by plan: 120 writes on Free up to 1200 on Scale, with reads at forty times the write number. Table and headers.
- Client timeouts for Sume jobs: SDK defaults and the 30-second cap
Sume's sync wait caps at 30 seconds, waitForRun defaults to 10 minutes, subscribeFormatRun and waitForJob to 20. Pick a deadline per job type, keep the job id.
- Choosing a Sume Idempotency-Key: business key plus a payload version
A good Idempotency-Key is stable across retries and changes with the request. Build it from your order id and a payload hash, or hit 409 idempotency_conflict.
Written by Sume