Tts Generation

[metra]

Hi,

 

We are using VG version 5.02.5012 and Acapela Telecom as TTS engine.

 

Sometimes, when the script asks for a TTS wave file generation, we have first the ErrorPlayingFile.wav played 1 or two seconds and after the generated wave file begin to play. See also section "Log Dual play" in traces file.

 

We also have sometine wave files locked by VG. In this case, no further wave file with the same name (..._6_4.wav) could be generated and we have to stop VG, to delete the locked Wave file and to restart VG. See also section "Log Locked File" in traces File

 

What are the possible reason for this facts ?

Is it possible to set up a wait time for TTS generation ?

 

I enclose the logs (vgm, sw, tw) of this events.

 

Thank you in advance.

 

Medical Link Services

Log_VG.txt

[SupportTeam]

The "Dual Play" which results in ErrorPlayingFile.wav being played first and then the TTS'd data being played appears to be cased by your script trying to do two TTS plays one after another... and not waiting for first TTS playing to start before doing another TTS play.

 

Please post the traces capturing the entire call, not just the play attempt, as well as the script itself.

 

 

The "Locked File" traces show that VoiceGuide asked the TTS system to do the TTS conversion and after TTS Engine reported that TTS is complete VG tried to open the created file but found that it was not created properly. It then tried to open the file a few more times over the next second (just in case TTS was a bit slow in finishing up it's TTS writing) but it found that each time the file header was not fully written.

After one second VG stopped waiting and played the ErrorPlayingFile.wav file.

 

Are you saying that you had to delete the file tts_6_2.wav before TTS would be able to do the second TTS during the call on all future calls?

 

Sounds like the TTS process crashing here, and blocking access to the TTS file it should be generating...

 

We should be able to come up with a workaround for system to recover from this - so there is no need for you to manually delete the .wav file (tts_6_2.wav in this case).

 

There should be no need stop VG - just deleting the .wav file which is 'locked' should resolve the problem. Do you find that you need to stop VG as well?

 

I take it that TTS conversions that create files other the 'locked' filename continue to work fine, and just every time the system tries to use the 'locked' file then there is a problem, yes?

[SupportTeam]

Attached .exe should resolve the 'locked' file problem you encountered.

 

To use this .exe you will need the TAPIWRAP.OCX which ships with current release of VG.

 

So you can either uninstall your existing VG and install the current release and update with this .exe, or you can install the current release on another machine and the just copy over the ocx.

If copying over just the ocx then you will need to use "regsvr32 -u" to unregister the current ocx before replacing it with new version and after copying over the file then register the new ocx using regsvr32.

 

If you are not familiar with regsvr32 then it's probably best to uninstall current VG and install the newest release...

VgMulti_5.2.5050.zip

[fwh]

I have the same problem with the VG for Dialogic version. where can I get the .exe patch file?

[SupportTeam]

Here is the "VoiceGuide for Dialogic" version with the same changes applied.

VgMulti_6.0.3113.zip