Hi.
I am trying to write an app that is entirely handsfree - using the TTS and VR libraries.
It seems that you have to wait for the TTS Ready event to fire each time the Speak method is called before the the TTS can be used again. Originally I thought this event only fired during initilialisation.. ..is it self re-initilaising after every call to Speak I wonder?
As the Ready event is 'asyncronously' happening it means a lot of code has to go in the (TTS) Ready event and it can be any number of seconds before it becomes Ready again after each Speak() call.
In order to try and control the firing of this event somewhat I have been using Release and Initilialize before each Speak call and then wait for Ready to fire and handle the Speech there -(which is probably not good on resources?)
My question then is:
Has anyone figured a way to test for the 'Ready' state instead of waiting for it to occur?
Thanks,
I am trying to write an app that is entirely handsfree - using the TTS and VR libraries.
It seems that you have to wait for the TTS Ready event to fire each time the Speak method is called before the the TTS can be used again. Originally I thought this event only fired during initilialisation.. ..is it self re-initilaising after every call to Speak I wonder?
As the Ready event is 'asyncronously' happening it means a lot of code has to go in the (TTS) Ready event and it can be any number of seconds before it becomes Ready again after each Speak() call.
In order to try and control the firing of this event somewhat I have been using Release and Initilialize before each Speak call and then wait for Ready to fire and handle the Speech there -(which is probably not good on resources?)
My question then is:
Has anyone figured a way to test for the 'Ready' state instead of waiting for it to occur?
Thanks,