#What do provoke this error ?Error sending audio: sent 1000 (OK); then received 1000 (OK)

1 messages · Page 1 of 1 (latest)

high zephyrBOT
#
AI-generated Answer for epoxyra

Short answer: you’re trying to send after the WebSocket has already been closed.

In ElevenLabs’ WebSocket APIs, the socket closes automatically:

  • after inactivity (default 20 seconds, configurable), or
  • when you signal end-of-sequence (e.g., sending an empty string), or explicitly close the connection. (elevenlabs.io)

What to do:

  • Keep the socket alive by sending a single space " " periodically, or increase the inactivity_timeout (up to 180s) in the WebSocket URL. (elevenlabs.io)
  • Don’t send more data after you send the empty string (EOS) or a close message; reopen a new WebSocket if you need to continue. (elevenlabs.io)

Sources:
Generate audio in real-time | ElevenLabs Documentation
Generate audio in real-time | ElevenLabs Documentation
Generate audio in real-time | ElevenLabs Documentation

warm sonnet
#

How does that happen ? I am sending an audio to scribe v2 realtime and none of the audio_base_64 are empty. hy does it close then ?