The transcriber to pt-br is not working well.
# support
m
In the call logs, many messages show up as having a null body from the user, but when I listen to the audio recordings, I can clearly hear the user speaking. It seems like the bot is not capturing or transcribing the user's voice properly, even though the audio is fine. the transcriber configurations is pt-br. call id: df219e88-3d43-42ff-9724-d0d2f17a3110
p
Theres issue atm, that doesnt allow saving transcriber language, maybe its related to that?
v
Thanks for reporting this issue with the pt-br transcriber. To help troubleshoot this problem, could you please share: 1. Which transcriber provider are you currently using (Deepgram, Azure, Talkscriber, etc.)? 2. Have you checked the endpointing settings in your configuration? The default Deepgram endpointing value of 10ms might be [too aggressive](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343636482874933340) for capturing complete utterances in Portuguese. 3. Is
smartEndpointingEnabled
set to false in your configuration? This [needs to be disabled](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1329414710583627796) when not using English. 4. Have you tried adjusting the
waitSeconds
parameter in your
startSpeakingPlan
? I'll look into the call ID you provided, but these details would help me better understand what might be causing the null bodies in your call logs. Sources: - [Transcriber Configuration Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343636482874933340) - [Disable smartEndpointingEnabled for non-English](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1329414710583627796)
m
1. Azure 2. I'm using Azure 3. Smart endpoint off 4. wait second = 0.4, i tried to change this, no result The same assistant with the exactly configuration work last week, I change nothing and this week is not working
s
I have a workaround its an UI/API bug if you change transcriber by UI. It sends wrong data structure: You can fix it with a PATCH trough Postman: mentioned it here: https://discord.com/channels/1211482211119796234/1357701801964736704
m
ohh thanks man
k
checking if this is resolved/solved for you?
m
Yes, it's already resolved. Thank you!
k
Marking this ticket as Solved ✅
2 Views