Repository navigation
feat(api): add OpenAI Realtime compatible TTS on /v1/realtime, Speech endpoint fields on all websockets - #584
Merged
Merged
Conversation
…on websockets via shared SpeechOptions
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.
OpenAI Realtime compatible TTS on
/v1/realtime, for Realtime TTS clients (wyoming_openai etc). TTS only:response.createtext input, 24 kHz PCM output. OpenAI's Speech models shut down Jan 2027 and point users to Realtime.{"id": ...}voice_aliases,lang_code,volume_multiplier,normalization_optionswork on all three websocket routes (sharedSpeechOptions), no voice tagsresponse.cancelstops a response. Audio input and conversation events get anerrorbackENABLE_WEBSOCKET_TTSswitch andAPI_KEYSauth as the ElevenLabs/Cartesia routesopenaiSDK (3.44.0, test-only dependency)ElevenLabs route now checks the voice on the first context message instead of at connect, since aliases arrive with it. Bad voices still close with 1008.
Testing
uv run pytestpasses locally (API changes)npm run test:webpasses locally (web player changes)npm run cpu:up/gpu:up), for inference or docker changesCHANGELOG.mdentry, if users will notice the change