docs(tts): document per-provider max_text_length caps from #13743 - #13825
Closed
r266-tech wants to merge 1 commit into
Closed
docs(tts): document per-provider max_text_length caps from #13743#13825r266-tech wants to merge 1 commit into
r266-tech wants to merge 1 commit into
Conversation
PR NousResearch#13743 replaced the global MAX_TEXT_LENGTH=4000 with a per-provider table and a user-override 'max_text_length:' key, but the user-guide TTS page documented no length behaviour at all. Users hitting truncation had no way to discover the new caps or the override. Add an 'Input length limits' subsection after the existing Configuration YAML block: provider default caps (Edge 5000 / OpenAI 4096 / xAI 15000 / MiniMax 10000 / Mistral 4000 / Gemini 5000 / ElevenLabs model-aware / NeuTTS,KittenTTS 2000), ElevenLabs model_id -> cap table (5k-40k), an override example, and the validation rules (non-positive / non-integer / boolean values fall through to the provider default).
alt-glitch
added
type/docs
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
2 participants
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
PR #13743 replaced the global
MAX_TEXT_LENGTH = 4000with a per-provider table and a user-overridemax_text_length:key, butwebsite/docs/user-guide/features/tts.mddocumented no length behaviour at all. Users hitting truncation (or wondering why xAI can take 15k chars while Mistral can't) have no way to discover the new caps or the override from the docs.This PR adds an Input length limits subsection to the Voice & TTS page, right after the existing
### ConfigurationYAML block. It documents:tools/tts_tool.pyPROVIDER_MAX_TEXT_LENGTH(Edge 5000, OpenAI 4096, xAI 15000, MiniMax 10000, Mistral 4000, Gemini 5000, NeuTTS/KittenTTS 2000)ELEVENLABS_MODEL_MAX_TEXT_LENGTH(flash_v2_5 40k, flash_v2 30k, multilingual_v2 10k default, v3 5k)tts.<provider>.max_text_length: <int>with a YAML example_resolve_max_text_length()(non-positive, non-integer, or boolean values fall through to the provider default so a broken config can't accidentally disable truncation)All values verified against
tools/tts_tool.pyonmain(commit 7b79e0f).Test plan
PROVIDER_MAX_TEXT_LENGTHandELEVENLABS_MODEL_MAX_TEXT_LENGTHdicts intools/tts_tool.py_resolve_max_text_length()andtests/tools/test_tts_max_text_length.pywebsite/docs/user-guide/features/tts.md+37 / -0