Text-to-Speech (Streamed File)
Text-to-Speech (Streamed File)
Authentication
Request
A list of Utterances to be converted to speech output.
An Utterance is a unit of input for Octave, and includes input text, an optional description to serve as the prompt for how the speech should be delivered, an optional voice specification, and additional controls to guide delivery for speed and trailing_silence.
Enables ultra-low latency streaming, significantly reducing the time until the first audio chunk is received. Recommended for real-time applications requiring immediate audio playback. For further details, see our documentation on instant mode.
- A voice must be specified when instant mode is enabled. Dynamic voice generation is not supported with this mode.
- Instant mode is only supported for streaming endpoints (e.g., /v0/tts/stream/json, /v0/tts/stream/file).
- Ensure only a single generation is requested (num_generations must be
1or omitted).
Number of audio generations to produce from the input utterances.
Using num_generations enables faster processing than issuing multiple sequential requests. Additionally, specifying num_generations allows prosody continuation across all generations without repeating context, ensuring each generation sounds slightly different while maintaining contextual consistency.
Controls how audio output is segmented in the response.
-
When enabled (
true), input utterances are automatically split into natural-sounding speech segments. -
When disabled (
false), the response maintains a strict one-to-one mapping between input utterances and output snippets.
This setting affects how the snippets array is structured in the response, which may be important for applications that need to track the relationship between input text and generated audio segments. When setting to false, avoid including utterances with long text, as this can result in distorted output.
If enabled, the audio for all the chunks of a generation, once concatenated together, will constitute a single audio file. Otherwise, if disabled, each chunk’s audio will be its own audio file, each with its own headers (if applicable).
Selects the Octave model version used to synthesize speech for this request. If you omit this field, Hume automatically routes the request to the most appropriate model. Setting a specific version ensures stable and repeatable behavior across requests.
Use 2 to opt into the latest Octave capabilities. When you specify version 2, you must also provide a voice. Requests that set version: 2 without a voice will be rejected.
For a comparison of Octave versions, see the Octave versions section in the TTS overview.

