docs(qwen3-tts): add real-time streaming tuning guide#646
Draft
akaiHuang wants to merge 2 commits intoBlaizzy:mainfrom
Draft
docs(qwen3-tts): add real-time streaming tuning guide#646akaiHuang wants to merge 2 commits intoBlaizzy:mainfrom
akaiHuang wants to merge 2 commits intoBlaizzy:mainfrom
Conversation
Author
|
Hi @Prince_Canuma @Blaizzy, I've added a practical real-time streaming tuning guide for Qwen3-TTS in the documentation. This is based on extensive benchmarking on M1 Max (4-bit). It shows:
The guide turns the previous ~4.31s first-chunk into a tunable 0.317s–0.546s range. Would love your feedback on whether this is useful and if any adjustments are needed before marking it ready for review. Thanks! |
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
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
Add a practical real-time tuning section for Qwen3-TTS streaming in the model docs.
What this adds
streaming_interval = chunk_tokens / 12.5relation for Qwen3-TTS codec rate.chunk_tokens2/4/6/8) with trade-offs for latency vs smoothness.stream=True, streaming_interval=0.32as a pragmatic default for real-time usage, with guidance to move to0.48when smoother chunks are needed.Why
Users deploying live translation / assistant pipelines often need concrete first-pass values rather than only API descriptions. This doc update shortens trial-and-error and aligns expectations around chunk boundaries vs latency.
Scope
Docs-only change. No runtime behavior changes.