docs(qwen3_tts): clarify voice cloning vs speaker synthesis usage rules#582
Closed
mm65x wants to merge 2 commits intoBlaizzy:mainfrom
Closed
docs(qwen3_tts): clarify voice cloning vs speaker synthesis usage rules#582mm65x wants to merge 2 commits intoBlaizzy:mainfrom
mm65x wants to merge 2 commits intoBlaizzy:mainfrom
Conversation
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.
Description
this updates the
qwen3_ttsREADME to explicitly clarify the API contract for voice cloning vs speaker synthesis to prevent user confusion, based on the discussion in #557.closes #557
specifically, it clarifies that:
voiceargument alongsideref_audioandref_textto avoid routing/configuration conflicts.ref_textmust be a literal transcript string, unlikeref_audiowhich accepts a file path.Changes in the codebase
mlx_audio/tts/models/qwen3_tts/README.mdChecklist