WIS TTS URL v2 support #336
Merged
Conversation
This file contains 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
To have more flexibility with the new Coqui TTS backend, we're going to construct the TTS URL in WAS before sending it to Willow. We will support both the old and the new way for a while, both in Willow and WAS, so that old Willow versions will work with new WAS versions, and new Willow version will work with old WAS versions.
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.
To have more flexibility with the new Coqui TTS backend, we're going to
construct the TTS URL in WAS before sending it to Willow.
We will support both the old and the new way for a while, both in Willow
and WAS, so that old Willow versions will work with new WAS versions,
and new Willow version will work with old WAS versions.