Smallest.ai documents a capability change: “Lightning v3.1 / v3.1 Pro - control number pronunciation separately from the voice You can now control how numeric content - numbers, currency amounts,…”
Lightning v3.1 / v3.1 Pro - control number pronunciation separately from the voice
You can now control how numeric content - numbers, currency amounts, times, and the numeric parts of dates and years - is read out, independently of the synthesis voice. The new optional number_pronunciation_language parameter sets the text-normalization language and is accepted on Lightning v3.1 and v3.1 Pro , across the dedicated /waves/v1/lightning-v3.1/* endpoints and the unified /waves/v1/tts route - REST, SSE streaming, and WebSocket.
Read from the provider's text; the quote is the provider's exact lines.
Smallest.ai documents a capability change: “Lightning v3.1 - auto language removed from docs and spec enums Why: code-switching guidance lives on the voice, not the request.”
Lightning v3.1 - auto language removed from docs and spec enums
Why: code-switching guidance lives on the voice, not the request. Each voice in the catalog has a tags.language set returned by GET /waves/v1/lightning-v3.1/get_voices; pass a language the voice was trained on to get the pronunciation you expect. The auto value never actually drove language detection at the model level - it was a permissive enum value that resolved to the voice’s default behavior - so removing it from the contract is the honest move.
Read from the provider's text; the quote is the provider's exact lines.
Lightning v3.1 - per-word timestamps on WebSocket streaming
Lightning v3.1 now exposes per-word timing events to WebSocket clients. Opt in with one flag - useful for captioning UIs, karaoke-style word highlighting, avatar lip-sync, and word-level analytics.
What changed
Two changes to a WebSocket request: add word_timestamps: true and handle the new status: "word_timestamp" frame.
Read from the provider's text; the quote is the provider's exact lines.
