Chip, I was not aware that the Speech Platform of the MS would in any way replace the SAPI. Just thought it to be yet another standard, with which I have not yet bothered. Sure, if MS would drop SAPI altogether, that would be bad news for many developers, and a buntch of users. Smile. Reality I guess, will be slightly different. Even if they drop the support of SAPI, your SAPI stuff may still work, I would think. At least on existing systems. So, I will continue my project, till someone can tell I am wrong. Smile.
Main reason for all my SAPI idea right now, is that I want to leave the users of some of my apps, the chance of deciding different voices, for different apps or activities. At least, I personally find it quite helpful, since you more easily will be able to distinguish app produced speech, from the general screen reader chattering. Of course, I will leave the users the chance of deciding, so if they want the apps to speak through the same synth as the screen reader itself, that is fine, and they can just set the app to do so. Well, again, if anyone has any feedback on the issues Chip brings out here, I am eager to know as well. ----- Original Message ----- From: Chip Orange To: [email protected] Sent: Wednesday, February 12, 2014 1:09 PM Subject: RE: Using a SAPI voice? Hi David and others, I see that MS has replace SAPI with the Microsoft Speech Platform, which evidently has a different way of interfacing with the voices. Does anyone have any info on the two systems: when will SAPI stop being supported; am I correct in thinking that the speech platform is not backwards compatible with SAPI commands? Etc. Was just wondering if a developer put a lot of effort into SAPI could he count on it continuing to run for a long time? Thanks. Chip From: David [mailto:[email protected]] Sent: Monday, February 10, 2014 4:33 PM To: [email protected] Subject: Using a SAPI voice? In my app, I am using a SAPI voice, to read out a certain amount of text. the very basics of the code, is: Dim SVoice: Set SVoice = CreateObject( "SAPI.SpVoice") SVoice.Speak "blah-blah-blah!" Allright, all of this works fine. Yet, since the text is somehow lengthy, and I want other processes not to wait for all that text to be spoken, I have this one question for you experienced developers. Is there any instruction I can use, to send the text to the Sapi voice, and immediately have the next line of code carried out? That is, some kind of an instruction for the Sapi Object, to know that it is not supposed to wait for the voice to finish speaking, before the code can move on. Thanks for any response, and hope the above somehow made sense.
