French Tts

[svitex]

In French there are some letters with "accents" like "é". (The letter "e" with a small line on top of it).

 

In Voiceguide in TTS Speak module, when i use this letters, voiceguide not send the good letter to TTS engine and the sound of word is wrong.

 

When i make a test directly with the TTS Application there is no problem.

 

What is the solution ??

[SupportTeam]

Which TTS engine are you using?

 

Which version of VoiceGuide are you suing?

 

Can you try saving the TTS text in the .TXT file and specifying that .TXT file as the file to be played?

 

[svitex]

QUOTE

Which TTS engine are you using?

Which version of VoiceGuide are you suing?

Can you try saving the TTS text in the .TXT file and specifying that .TXT file as the file to be played?

I Use Nuance Scansoft Telecom 4 TTS Engine.
I Use The last Version of Voiceguide 7.0.4.

The probleme is the same when i write the texte in .txt file.

When i write the text in Microsoft Sapisrv config panel and i click on "Test the voice" there is no problem.

[SupportTeam]

Please update to this version of v7: [old link removed]
You will need to uninstall existing version (backup your config files) and then install this new version.

The TTS input needs to be done as a .TXT file (specified where the .WAV file is usually specified).

Make sure the .TXT file is saved in Unicode format.

If you still have problems please post traces from VG's \log\ subdirectory which capture the system startup and the call, and also post your .TXT input file.

[svitex]

Thank you for your help.

 

The french TTS works fine in txt file + Voiceguide 7.0.4 unicodeTTS !

 

In "text to speak" module, the text isn't Unicode.

Perhaps in the future version ?

 

I work to translate the systems scripts for french.

- Date and time format

- Numbers to say (the decimal separator is "," in french, not ".")

 

Another Mistake : Impossible to make a gosub in a script or a module.

Voiceguide application close itself.

 

 

[SupportTeam]

Thanks for confirming the .TXT approach works fine on your system now.

 

VoiceGuide v7 will read Unicode .TXT files and forward them in Unicode format onto the TTS.

 

The v6 Script Designer's text boxes do not support Unicode at this stage. The future script designer will support Unicode.

 

We will look into the Gosub issue.

 

 

 

[svitex]

The French Tts is okey with Unicode.

 

There is a new problem in the GET NUMBER MODULE :

 

The text in the File .txt is reading by the Tts Engine.

At the end on the text, the engine keep the process and never stop reading.

The engine don't see the end of a file and stay in the file, there is no return to the module.

 

In the line status monitor, i see :

Playing (C:\Program Files\Voiceguide\Temp\tts_1_.wav)

 

If i wait, there is no text repeat . Just Silence...

 

If i physicaly hangup the line, the status line is already ON LINE.

 

(The timeout 30 is never fired)

 

When i play a .wav file directly, all is allright. The text is playing 2 times between 5 seconds of silence.

After 30 seconds, the Hangup module fired.

 

Same problem with the PLAY MODULE and .txt file.

 

Best Regards

 

[SupportTeam]

We have found and corrected this bug. Please update to this version: [old link removed]

 

To update you will need to uninstall the current version, make sure no .EXE files are left in VG's main directory and then install the new version.

[svitex]

Great, Congratulation for your reactivity !

 

The Tts file is read normally to the end, and the process continue, the timeout 0 is fired. It's okey !

This problem is corrected !

 

Other problem with Tts :

 

The tts File work's fine in "Play Sound Module", "Get Number Module" but in the "Speak Number Module", i hear a loud Noise during the reading.

The sound is very very bad.

 

 

 

 

[SupportTeam]

In the Say Number module does the TTS part sound fine, but then the actual numbers sound distorted? This would be caused by the TTS file and the numbers being created in different format. Have a look at the format of the TTS files created by your TTS (open them in Windows Sound Recorder or just view Properties) and then make sure the digit files used by the Say Number module are recorded in same format.

[svitex]

In The "Say Number Module" in the "Play before saying number" field, The .txt file is distorted.

In the "Number" Field, The sound is distorted too.

 

The generated .wav of TTS and the numbers .wav are in the same format :

128 kbps - 16 bits - 1 mono - 8khz PCM

 

It's Ok in the other modules (Tts and wav) but is distorted in the Say Number Module.

 

In The Say Number Module :

TTS File + Wav Number = Wrong and Wrong

Wav file+ Wav Number = Ok and Ok

 

Always the same format : 128 kbps - 16 bits - 1 mono - 8khz PCM

[SupportTeam]

Looks like the use of .TXT files is not supported in a Say Number module. Looks like it was regarded as not being required as if you are using a TTS engine then you can just use the TTS to say the numbers/dates as well - so you can use a normal Play module to get this done. If you must use the Say Number module then the .TXT file would need to be played from Play module beforehand. Use a on {timeout 0} goto path and set the number of replays to 0 to let the script move onto the Say Number module immediately after the prompt finishes playing.