Cant switch transcription to "bg"/Bulgarian even ...
# support
v
As seen in the image I have selected "bg" for bulgarian transcription and I have chosen the voice of "Elena" which is an Elevenlabs voice in Bulgarian. For some reason. no matter which voice I choose it never seems to work for "bg" despite the voice preview literally being in Bulgarian. How can I fix this? ID of voice: fSxb5mPM1l5zTVVtM3Vb (Elena - Elevenlabs) https://cdn.discordapp.com/attachments/1357661052267135056/1357661052912926760/image.png?ex=67f103e3&is=67efb263&hm=ea664e284c7dac4c32a74278be62a2fc873a1f75e59cc6a12a22e7c8643cdbf1&
v
Is there anything specific from these suggestions you'd like me to elaborate on, or would you like to try a different approach? Sources: - [Troubleshooting Bulgarian transcription issues with Elevenlabs voices](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333785780447084554) - [Elevenlabs voice compatibility with Bulgarian transcription](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336377394050764821) - [Vapi transcription configuration for Bulgarian language](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1270786139355090995) - [Limitations of the Scribe transcription model in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343672800900022343) - [Known issues with Vapi Elevenlabs integration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335277468805758986)
Hi there! 👋 I see you're having trouble with Bulgarian transcription despite selecting the right language and a compatible voice. While I don't have a definitive solution for this specific issue with the Bulgarian language and ElevenLabs voice "Elena", I can definitely help with some troubleshooting steps based on similar issues others have encountered. Here are some potential solutions to try: 1. **API Key Configuration**: Try removing your ElevenLabs API key if you're using one. According to [troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341348892402384896), sometimes using Vapi's default key works better than a personal one. 2. **Try a Different Model**: Switch from the "Scribe" model to another model if available. Some users have had success switching to the "turbo" model when experiencing issues with ElevenLabs voices. 3. **Voice Model Configuration**: Make sure the language setting for the voice model used for outbound communication is specified. According to [configuration information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1270786139355090995), sometimes the transcriber language is set correctly, but the voice model language isn't specified. 4. **Check
chunkPlan.enabled
Setting**: For non-English languages like Bulgarian, keeping
chunkPlan.enabled: true
is important for proper sentence boundary detection and whitespace normalization. This can affect how well the transcription works. 5. **Sync Voice with VAPI**: Confirm if you've already synced your voice with VAPI by selecting 11labs as your voice provider and clicking on "Sync with 11labs" in the Voice Library. 6. **Voice ID Verification**: Double-check that the voice ID is correct and compatible with the provider. The ID you provided (fSxb5mPM1l5zTVVtM3Vb) should be verified.
s
Hi Valeri, there are multiple reported issues about updating the assistants in any way... lets all together #1293690685781839933 and make this an emergency for the dev team
v
Oh, so its something happening just today?
s
seems so
v
okay
triggered it
s
nice
a
@Valeri Sabev The Transcriber language is now fixed and deployed to PROD. It should save as expected now.
s
@Arvind @Sahil Still not fixed unfortunately... Are you on it? Any update? Thanks in advance
try change to google or openai ... save and then change back to deepgram... that worked for me ... kinda ... the agents responses are whacky still but the language remains changed
a
Yes, taking a deeper look into this. Some transcriber configs were updated.
s
@Arvind Agents working reliably again ... thanks for your effort
a
Marking this ticket as Solved ✅
2 Views