feat(smallestai): update TTS plugin for Lightning v3.1 Pro and unified endpoint#5799
Open
harshitajain165 wants to merge 6 commits into
Open
feat(smallestai): update TTS plugin for Lightning v3.1 Pro and unified endpoint#5799harshitajain165 wants to merge 6 commits into
harshitajain165 wants to merge 6 commits into
Conversation
…ified endpoint
- Add lightning_v3.1_pro model (premium 44.1 kHz pool, curated voice catalog)
- Rename lightning-v3.1 → lightning_v3.1 to match updated API model ID notation
- Remove lightning-v2 (deprecated) and its exclusive params (consistency, similarity, enhancement)
- Switch TTS endpoint from /{model}/get_speech to unified /tts; model now sent as body param
- Update TTSEncoding: mulaw → ulaw to match new API spec
…ophia for standard
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Comment on lines
+74
to
+76
| model: The TTS model to use. Use "lightning_v3.1" (default) for the standard | ||
| model with 217 voices across 12 languages, or "lightning_v3.1_pro" for the | ||
| premium pool with curated American, British, and Indian voices at 44.1 kHz. |
Contributor
There was a problem hiding this comment.
🟡 Docstring incorrectly claims "lightning_v3.1" is the default model
The docstring at tts.py:74 states Use "lightning_v3.1" (default) but the actual parameter default at tts.py:61 is "lightning_v3.1_pro". This will mislead users reading the documentation into thinking the standard model is the default, when it's actually the pro model.
Suggested change
| model: The TTS model to use. Use "lightning_v3.1" (default) for the standard | |
| model with 217 voices across 12 languages, or "lightning_v3.1_pro" for the | |
| premium pool with curated American, British, and Indian voices at 44.1 kHz. | |
| model: The TTS model to use. Use "lightning_v3.1_pro" (default) for the | |
| premium pool with curated American, British, and Indian voices at 44.1 kHz, | |
| or "lightning_v3.1" for the standard model with 217 voices across 12 languages. |
Was this helpful? React with 👍 or 👎 to provide feedback.
This was referenced May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
lightning_v3.1_proas a supported TTS model — Smallest AI's new premium 44.1 kHz pool with curated American, British, and Indian voiceslightning-v2and its exclusive parameters (consistency,similarity,enhancement)/{model}/get_speech) to the new unified/ttsendpoint wheremodelis a JSON body parameterlightning-v3.1→lightning_v3.1) to match the current API specTTSEncoding:mulaw→ulawto match new API specvoice_idfrom the model at construction time:meherforlightning_v3.1_pro,sophiaforlightning_v3.1— prevents silent bad output from mismatched voice/model pairingsTest plan
lightning_v3.1_proendpoint verified live againstapi.smallest.ai/waves/v1/tts(HTTP 200, audio returned)consolemode with Pulse STT + Lightning v3.1 Pro TTS