Documentation

​
​

Development

User Acquisition

Monetization

Industry

Vivox Core SDK

Vivox Core SDK

Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
    • Client SDK basics
    • Channels
    • Presence management
    • Messaging
    • Manage audio
    • Couch co-op
    • Android app development
    • iOS app development
    • macOS app development
    • Windows app development
    • Real-time recording
    • Speech-to-text audio transcription
    • Text-to-speech
      • Initialize text-to-speech
      • Text-to-speech voice options
      • Text-to-speech destinations
      • Inject a text-to-speech message
      • Queue a text-to-speech message
      • Cancel a text-to-speech message
      • Text-to-speech events
      • Get raw audio of synthesized speech
      • Use text-to-speech for incoming messages
      • Shut down text-to-speech
    • Troubleshooting
  • Reference
  • Privacy overview
  1. Vivox Core SDK documentation
  2. Text-to-speech

Queue a text-to-speech message

Queue a text-to-speech message for audio output.
Read time 1 minute
Last updated 8 months ago

Some destinations offer a built-in queuing system. When a new message is injected and there is an ongoing message playing, then the new message is put into a queue. After the ongoing message finishes playing, the next message in the queue automatically starts to play.
Note
The following code example uses the Queued Local Playback destination, but you can inject all text-to-speech (TTS) messages into any of the TTS destinations.
vx_tts_utterance_id firstUtteranceId;vx_tts_speak(managerId, voiceId, "Example message, this is great!", tts_dest_queued_local_playback, &firstUtteranceId);// Immediately injected and returns tts_status_successvx_tts_utterance_id secondUtteranceId;vx_tts_speak(managerId, voiceId, "Really amazing.", tts_dest_queued_local_playback, &secondUtteranceId);// Put in a queue and returns tts_status_input_text_was_enqueued. After the first message finishes playback, this message will start.
A queue is shared between
tts_dest_queued_remote_transmission
and
tts_dest_queued_remote_transmission_with_local_playback
.
tts_dest_queued_local_playback
has its own queue.
A destination queue can hold up to 10 messages. If a message is added when a destination queue is full, the Vivox SDK discards the message and returns the error
tts_error_destination_queue_is_full
.

Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.


    Report a problem with this page