Add MiniMax text-to-speech processor - #319
Open
octo-patch wants to merge 1 commit into
Open
octo-patch wants to merge 1 commit into
octo-patch wants to merge 1 commit into
Conversation
|
@octo-patch is attempting to deploy a commit to the LLMStack Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
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.
Reason: Add MiniMax text-to-speech processing so workflows can synthesize audio with a regional MiniMax account.
Add provider credentials and speech endpoint selection, an auto-discovered speech processor, and typed voice/audio controls. Support the configured speech models, optional pronunciation rules, voice effects and subtitles. Decode completed audio into an asset and reject API errors, incomplete responses, and invalid audio before creating an asset.
Validation:
The minimal provider configuration and registration allow this PR to run on main. Those shared registration files also appear in the existing chat PR #315 and will need reconciliation when both changes land.