Specifying a TTS voice

[shearn]

With the base install of GVP, it comes with the US English Jill voice. We bought a license for US English Tom and I'm trying to figure out how to tell MRCP to use that voice.

I found a snippet of info online saying I need to declare a global property: <-- property name="com.genesyslab.ttsengine" value="default" />
in my vxml file and get the value from my sys admin. However, my sys admin installed the language pack and he said there was nothing else to configure other than the install. Is that correct?

"default" of course would play Jill's voice without problem. The question is, how do I tell it to play Tom's voice?

Any insight will be much appreciated.

Shearn

[cavagnaro]

MCP is just a translator, your VXML app is the one that choices the voice...imagine a scenario with an app with 3 languages...how on earth will MCP would know that.
Read composer guides

[Kubig]

MRCP is a protocol for communication between clients and TTS/ASR server. Do you have TTS/ASR server?

[genesysguru]

Might be wrong but I think last time when using Nuance TTS we needed to configure it on the MRCP server end e.g. in Nuance.

[cavagnaro]

Upss...hoho
MRCP not MCP...
Well still has to be done on the VXML application only.

[Kubig]

Yes, if he does not have TTS/ASR server with MRCP (v1 or v2) protocol support, has to be done via separate audio files for each language in vxml app.

[shearn]

Hi all,

for some reason, I wasn't getting notified that there were responses to my question! I apologize about the silence.

So, we got it figured out finally. We had to create a Resource Access Point object for the new voice in Configuration Server. After that, the .vxml file just needs to specify the TTS engine by name. Our missing link has been the RAP object all along.

Here's a followup question: Do you have any best practice recommendations for specifying the TTS engine? What I have to do today is generate the .vxml code in Composer, then manually edit the .vxml to add the <-- property name="com.genesyslab.ttsengine" value="REALSPEAK_TOM" />, save it, then export the code out to the web server. Is this pretty much the only way to do it currently?

Shearn

[cavagnaro]

Weird...you have multiple TTS engines and Language Packs?
As for the option just declare it on the start on Global Properties...but I never had to using only 1 TTS engine and Language Pack

[shearn]

We just have English language throughout, but over the years, we've had both male and female VTO recordings. As we're moving over to GVP, we decide to keep using the existing recordings for now. So we want at least some continuity for the apps that uses both audio recordings and TTS. I believe we also have limited TTS ports so we can't just replace everything with TTS.

That declaration you mentioned is in the vxml file right? You're referring to the section:
<!-- Global Properties declarations -->
<property name="com.genesyslab.logtoasr" value="false" /> 
<property name="com.genesyslab.loglevel" value="5" />

[shearn]

Ooops. I hit post a bit too early.

(Continue from previous post) I guess I was wondering if there might be a way to not have to manually edit the vxml file, in other words, setting that property somewhere inside the Composer IDE's Callflow diagram editor. But if not that's OK, our developers can learn new tricks!

[Kubig]

For configuring property file for vxml application, you can use default property file, which is located under install folder of MCP for vxml or you can create your own file and configure it in IVR profile. These configuration will be used for each vxml app in Genesys solution.

[cavagnaro]

As said, click the Entry object and modify the Global Properties parameter. You declare there. No need to modify XML files...
So you have 1 app that uses both male and female voices??

[shearn]

Ah, I apologize, cavagnaro. I didn't follow you earlier. I got what you're referring to now! Thanks! And no, we do not have 1 app that uses both male and female. It's either one voice or the other.

Kubig, good point. I didn't even think about setting it at the IVR profile object. I'll check that out too.

Thanks everyone! You guys are helpful!