-
Notifications
You must be signed in to change notification settings - Fork 513
How to do integration with Azure TTS
The overall architecture is important to ensure good end to end experience like latency, reliability, scale etc.
It could be from client or a service. For service, it could be an integrated service like direct line speech or a 3rd party application service.
It is usually recommended to call TTS service from an application service, which could be the middle layer to the customer's client application.
Is it from Azure DC or from 3rd party cloud?
In general, it is better to keep the region close to minimize latency.
Across DC call would usually take more time. so the close the DCs are, the smaller the latency would be.
We recommend to choose Azure DC to host the application caller service.
To minimize latency or bandwidth, a streaming and compressed format is recommended.
how-to-choose-different-audio-output-format
We recommend to add trace ID for each request. so it is good to debug an issue later.
How to get request ID for debugging purpose
In general, if you have higher demand for request per second than default, engage the Azure support or your Azure contacts, we will respond quickly.
How to increase TTS request limits?
For service to service call, it is better to use synthesis pool which can save connection time for each request.
- Azure TTS: Empower every person and every organization on the planet to have a delightful digital voice!
- Azure Custom Voice: Build your one-of-a-kind Custom Voice and close to human Neural TTS in cloud and edge!