CFD 16.6.53.0 does not support Olivia Polly neural voice, even after manually entering

[aie_it]

The doco here states "In case of Amazon releasing a new voice not included yet in this drop down list, you can just enter the value from the “Name/ID” column to use it". The Olivia neural voice does not appear in the voices dropdown - so I'm entering it manually.

When I input "Olivia" the resulting XML defaults to the "Standard" voice engine:

playPrompt.Prompts.Add(new TextToSpeechAudioPrompt(myCall, logHeader, onlineServices.TextToSpeechEngine, "Olivia", TextToSpeechAudioPrompt.TextToSpeechVoiceTypes.Standard...

I can workaround the problem by manually modifying the XML file to:

playPrompt.Prompts.Add(new TextToSpeechAudioPrompt(myCall, logHeader, onlineServices.TextToSpeechEngine, "Olivia", TextToSpeechAudioPrompt.TextToSpeechVoiceTypes.Neural...

This works, but thought I'd point it out.

P.S. We're new paying enterprise customers, I find it a little odd that I need to post bug reports to the forum. I get charging for support, but you should allow customers to submit bug reports/bug tickets directly.

 

[edossantos]

Hello @aie_it,

That voice is being added in the CFD for v18 that will be released shortly after the 3CX v18 final release.

We're continuously adding new voices released by the TTS engines we support, but they're available to you when we release a new version of the CFD.

Kind regards.

 

[aie_it]

Thanks Ernesto, but you missed my point.

3CX's documentation says you can use a new voice by "enter[ing] the value from the Name/ID”. However this is not true for new neural voices.

I think the documentation needs to be updated to say the following:

"In case of Amazon releasing a new standard voice not included yet in this drop down list, you can just enter the value from the “Name/ID” column to use it. Note that manually entering new neural voices is not supported".

I have personally found a workaround (by manually editing the XML), but others may not be as capable.

 

[edossantos]

Thanks Ernesto, but you missed my point.

3CX's documentation says you can use a new voice by "enter[ing] the value from the Name/ID”. However this is not true for new neural voices.

I think the documentation needs to be updated to say the following:

"In case of Amazon releasing a new standard voice not included yet in this drop down list, you can just enter the value from the “Name/ID” column to use it. Note that manually entering new neural voices is not supported".

I have personally found a workaround (by manually editing the XML), but others may not be as capable.

Yes, that's correct, because in Amazon Polly the same voice name can be standard or neural. However, when you specify a voice name that is not listed, it is assumed to be standard. This is a trade-off until the voice is added. We will adjust the documentation, thanks for the heads up!