Fix: Error receiving message & Error sending user audio chunk sent 1009 (message too big) #482
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
|
nice catch, i found this same bug in an external user of elevenlabs ws two weeks ago, and now its in our own sdk. annoying. thank you! |
AngeloGiacco
approved these changes
Feb 13, 2025
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.
Sometimes using the ConversationalAI demo throwing exceptions like:
Error receiving message: sent 1009 (message too big) frame with 1254313 bytes exceeds limit of 1048576 bytes; no close frame receivedError sending user audio chunk: sent 1009 (message too big) frame with 1254313 bytes exceeds limit of 1048576 bytes; no close frame receivedSeems current ws message limit is too low for some provided sound answers. This fix should fits long response requirements.