The realtime API works well in English, Vapi VAD parameters work as expected. But if you change the language the middle of the conversation, Vapi VAD (that probably relies on deepgram ASR) seems to fail and the AI interrupts a lot and can even hang up in the middle of the conversation. I know there is probably no easy fix, but just reporting this as a limitation. One of the strength of the Realtime API is that it can change language live but with the current VAPI implementation, it's not really usable.

@AdeB Thank you for bringing this to our attention. It's great to hear that the Realtime API is performing well in English and that the Voice Activity Detection (VAD) parameters are meeting your expectations. However, I understand the challenges you're facing when switching languages mid-conversation. Language switching is indeed a complex feature, and it's important for the VAD to adapt to the phonetic and linguistic characteristics of the new language to maintain performance. Your feedback is valuable, and I'll make sure to pass it on to our development team for review. In the meantime, if you're frequently switching languages in a conversation, a potential workaround could be to explicitly inform the API about the language change. This could help the system recalibrate and adjust the VAD parameters accordingly. If you need further assistance or have more details to share, please don't hesitate to reach out. We're here to help ensure you have the best experience with our Realtime API.

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp)