Issue with Multilingual TTS Output Using ElevenLab...
# support
r
Description: I’m encountering issues with multilingual TTS output when integrating ElevenLabs voices via the VAPI SDK. While English voices work flawlessly, Dutch, Portuguese, and Spanish voices sound unnatural with odd accents, as if trying to interpret the text in English. Steps to Reproduce: Use ElevenLabs voices configured for Dutch, Portuguese, or Spanish (language: nl, pt, es). Send text in the respective language to the TTS engine. Observe unnatural, accented pronunciation. Code Snippet: public readonly voices = { 'burt': { provider: '11labs', voiceId: 'e5WNhrdI30aXpS2RSGm1', language: 'en-US' }, 'elvira': { provider: 'azure', voiceId: 'es-ES-ElviraNeural', language: 'es' }, 'francisca': { provider: 'azure', voiceId: 'pt-BR-FranciscaNeural', language: 'pt' }, 'robert': { provider: '11labs', voiceId: 'cblS8WYNsiBLGnlV6jjx', language: 'nl' } } as const; return { transcriber: { provider: 'deepgram', model: 'nova-2', language: selectedVoice.language === 'es' ? 'es' : selectedVoice.language === 'pt' ? 'pt' : selectedVoice.language === 'nl' ? 'nl' : 'en-US' }, model: { provider: 'openai', model: 'gpt-3.5-turbo', messages }, voice: { provider: 'azure', voiceId: selectedVoice.voiceId }, name: this.config.value.assistantName }; // For ElevenLabs voices return { transcriber: { provider: 'deepgram', model: 'nova-2', language: selectedVoice.language }, model: { provider: 'openai', model: 'gpt-3.5-turbo', messages }, voice: { provider: '11labs', voiceId: selectedVoice.voiceId }, name: this.config.value.assistantName }; Troubleshooting Steps Taken: Verified language and voiceId settings. Tested voices and text directly on the ElevenLabs dashboard, which worked perfectly. Confirmed the text is properly formatted with language-specific diacritics.
v
@RayRay020 It seems like you've done a thorough job troubleshooting the issue with the multilingual TTS output. Since the voices work correctly on the ElevenLabs dashboard, the issue might be related to the integration process with the VAPI SDK. Here are a few additional steps you can take to resolve the issue: 1. **Check SDK Version**: Ensure that you are using the latest version of the VAPI SDK, as updates may contain fixes for language-specific issues. 2. **Review Language Codes**: Double-check that the language codes (
nl
,
pt
,
es
) are correctly implemented in the SDK and that they match the expected format for ElevenLabs. 3. **Inspect Integration Code**: Look for any discrepancies in how the SDK handles language parameters for ElevenLabs voices compared to other providers. 4. **Test with Simplified Text**: Try using very simple and common phrases in the target languages to see if the issue persists. This can help determine if the problem is with specific language features or the overall language support. 5. **Check for Encoding Issues**: Ensure that the text encoding is correct when sending requests to the TTS engine. Encoding problems could lead to incorrect pronunciation. 6. **Consult Documentation**: Review the VAPI and ElevenLabs documentation for any notes on language support or known issues. 7. **Contact Support**: If the issue persists, reach out to VAPI support with detailed information about the problem, including the steps you've taken and any error messages or logs. If you would like me to assist you further with any specific step or if you need to contact support, please let me know!
You can continue this conversation by mentioning me in the message.
r
where can i add and find the correct attribute format to finetune the model : Review Language Codes: Double-check that the language codes (nl, pt, es) are correctly implemented in the SDK and that they match the expected format for ElevenLabs.
s
Hey @RayRay020 To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!
I know you have already shared the most of info but these info around timestamp will help me to better convey the issues with the respective teams.
r
hi thanks for responding, fixed the issue but i cannot mark as resolved discord is throwing an error