Hume Octave production guidance

Use Hume Octave when the speech performance matters as much as the words: character narration, emotionally varied voiceover, interactive playback, branded voices, multilingual narration, voice cloning with consent, voice conversion, or audio that needs word/phoneme timestamps.

Do not treat Octave as a generic flat TTS engine. It is strongest when the request needs semantic context, emotional delivery, voice identity, or continuity across related utterances.

Do not use Octave for music, singing, non-speech sound effects, full audio mixing/mastering, source separation, or video generation. Use a separate audio post tool for loudness, noise cleanup, ducking, fades, file normalization, and final mix delivery.

Verification note: provider facts in this skill were checked against official Hume documentation, API reference, pricing, changelog, terms, privacy, and API data-usage pages on 2026-07-10. Re-check volatile facts before quoting exact pricing, plan limits, language lists, model status, or retention controls.

What Octave can and cannot do

Documented facts: