Most PlayHT voices not working with custom Web Sni...
# support
d
When it comes to generating a custom assistant I have not been able to use most of the voices that are available through the Vapi dashboard assistant setup. The only voices that work are the basic ones listed in https://api.vapi.ai/api#/ (see playhtvoice in the schemas section at the bottom). For example, I setup an assistant in the dashboard using PlayHT's "Autumn" voice (which works), but this doesn't work if I generate the assistant with a web snippet — in that case I have had to use "donna" instead. If I use "autumn" or "Autumn" it allows me to call but there is no voice and it hangs up a few seconds later.
v
message has been deleted
@Doggo I'm sorry to hear that you're experiencing issues with using certain voices for your custom assistant. It sounds like there might be a discrepancy between the voices available through the Vapi dashboard and the ones that can be accessed via the web snippet. To ensure that all voices are properly accessible, it's important to check a few things: 1. **Voice Name Casing**: Voice names are often case-sensitive. Make sure that you are using the correct case as listed in the documentation or the dashboard. If "Autumn" works in the dashboard, it should be spelled exactly the same way in the web snippet. 2. **API Documentation**: Double-check the API documentation to ensure that the voice "Autumn" is indeed available for use through the API and that there are no additional parameters or settings required for its use. 3. **Web Snippet Configuration**: Review the web snippet configuration to ensure that it is set up correctly. There might be additional settings or initialization steps required for certain voices. 4. **Error Logs**: Check if there are any error logs or messages when you attempt to use the "Autumn" voice through the web snippet. This can provide clues as to what might be going wrong. 5. **Compatibility**: Ensure that the web snippet is up-to-date and compatible with the latest version of the Vapi API. There might have been updates or changes that affect how voices are implemented. If you've gone through these steps and the issue persists, it may be best to reach out to Vapi support directly for further assistance. They would be able to provide more detailed support and potentially identify any bugs or issues with the system. Please let me know if there's anything else I can assist you with!
You can continue this conversation by mentioning me in the message.
d
So why are there only a limited number of voices available through the API, versus the Vapi dashboard setup?
v
@Doggo The difference in the number of voices available through the API versus the Vapi dashboard setup could be due to a few reasons: 1. **API Integration**: The API might have a limited set of voices that have been integrated and tested for compatibility and performance. The dashboard, being a more controlled environment, could allow for a broader range of voices that are still under testing or are not yet fully supported through the API. 2. **Licensing and Permissions**: Some voices may have licensing restrictions that limit their use to the dashboard environment only. These restrictions could be based on the agreements with voice providers or due to the commercial terms associated with certain voices. 3. **Technical Limitations**: There could be technical constraints that prevent all voices from being available through the API. This could include issues with voice rendering, encoding, or delivery that are more easily managed within the dashboard environment. 4. **Feature Rollout**: The Vapi team might be in the process of rolling out additional voices to the API. The dashboard could be serving as a testing ground for new voices before they become available through the API. 5. **Documentation Updates**: It's also possible that the documentation has not been updated to reflect the latest set of voices available through the API. This can sometimes happen if the API is updated more frequently than the documentation. If you need access to a specific voice through the API that is currently only available through the dashboard, I would recommend reaching out to the Vapi support team. They can provide more detailed information on the availability of specific voices and any plans to expand the API offerings. Is there anything else I can help you with regarding Vapi or voice integration?
d
OK, thanks. I hope this is resolved in the future, but I understand that Rome wasn't built in a day!
@User Just wondering if there are plans to roll out additional voices for generating assistants with the web snippet / API in future? I'd love to be able to use PlayHT's Autumn voice.
s
Currently, we don't have any plans for it.
4 Views