Unable to swap between Acapela V8 and Acapela V6 in the same application
Last reviewed: 11/16/2010
PRB Article ID: P111008
The information in this article applies to:
- SpeechKit 6
Instantiating a new ChantTTS object and setting the Acapela V6 runtime fails after destroying a ChantTTS object that initialized with the Acapela V8 runtime.
Destroying the ChantTTS object causes the Acapela runtime to be unloaded. However, if SAPI4 or SAPI5 Acapela runtime libraries are present, SAPI will retain the Acapela API library in memory preventing a different version to be loaded.
To prevent SAPI from interfering with the swap, do not include the libraries in your deployment, or rename the libraries in your SDK.
Depending on the initialization sequence, the ChantTTS object could load the V8 runtime because it uses the default V8 SDK path.
Removed the default SDK path so CSPEnginePath must be used to set the runtime path. Fixed in SpeechKit build 18.104.22.168.
Component Formats Impacted
All component formats.