VoiceGuide IVR Software Main Page
Jump to content

TTS not generating fast enough / playing old wav

Recommended Posts

Can you please advise which of these TTS generations or calls you would like us to look at.

There are 75 TTS plays and 12 calls in attached vgEngine trace.

Just browsing through them they all look fine, so not sure which one to look at in detail.


Share this post

Link to post

Yeah.  I was trying it a bunch of times to make it do that.  It would be the higher number wav files.  I'll try to figure it out or write down which one when it does it again.

Share this post

Link to post

By " when I make a module fail and get it to repeat, " do you mean when the module times out awaiting input and asks for input again? or something else?

If a module that uses TTS times out awaiting input it does not make the TTS engine do the TTS generation again, it uses the sound that was generated just a few seconds beforehand which also got placed in a .WAV file. On replays VoiceGuide plays straight from that .WAV file with no TTS engine involved. It's the same sound that was played before.

On SAPI TTS systems (which this is) the TTS engine creates a .WAV sound file (which takes a small fraction of a second) and VoiceGuide then plays that .WAV sound file. And when module times out awaiting input it just plays the same .WAV sound file again.

Share this post

Link to post

So for this test, it seems clear.  I deleted the wav files in temp, starting from scratch.  Made a new call, did all the correct things to get tts to wav generated in the correct order.

Next, I did a call and pressed less than the min number of digits.  It played the wav file for the next module instead of regenerating the tts to wav like it should (tts_2_2.wav).

I have it set to a 6 for min digits and 8 for max.

I have only a path for {success}.

Should I have a {fail} to restart the same module even though pressing less than min digits should have the module repeat?



Share this post

Link to post

Here is a quick patch + build that should revolve this:


Please post traces if any issues still encountered.

(bug was present if both the "Message that entered number was not correct or failed validation" was set to a .TXT file and the "Ask Caller to enter number:" mesage was set to .TXT file as well - so if TTS was used for both of those).


Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now