So this is a recent update/issue with the Deepgram Voice. It has a click at the beginning of every output of speech which is generated. Completely ruins the UX. I've tried to find anything in the documentation which allows me remove the first 10ms of that output (to get rid of that click) but there's nothing. For context: we do ~10,000 calls per month on VAPI and this deepgram voice is the best one for our conversations. We need to stick with the voice. However, I need you guys to fix this bug asap or I'm going to have to migrate over to LiveKit.

Hi Caleb, It seems the issue you're experiencing with a clicking noise at the start of Deepgram voice outputs is not directly addressed in the current documentation or settings. However, here are a few steps you might consider to mitigate the issue: 1. **Check Voice Model and Options**: Ensure that you're using the correct voice model and settings. You can specify the voice model by setting the

model

property to either

"aura"

or

"aura-2"

as mentioned in the [April 16, 2025 changelog](https://docs.vapi.ai/changelog/2025/4/16). 2. **Custom Audio Processing**: Consider implementing a custom audio post-processing step that trims the initial few milliseconds to remove the click. This would require handling audio processing outside of the Deepgram setup but might solve the issue if it's viable for your infrastructure. 3. **Voice Replacement**: As a workaround, you may want to test other voice providers supported by Vapi, such as ElevenLabs or Inworld, which could offer similar or better quality without the clicking issue. See the [Inworld Voice Provider changelog](https://docs.vapi.ai/changelog/2025/6/24) for configuration details. Consultation with the Deepgram support team might also yield more specific solutions or updates on potential fixes. If the issue persists, monitoring updated changelogs for new features or patches may also be beneficial or please do let us know further so we can help.