Re: Why "COMify" the SAPI support in C Sharp?
@Camlorn, it is not a game. I use SAPI for a very specific reason. This is my TTS wrapper for Android and so I need a granular control on when the uytterance is ended, ETC.
URL: https://forum.audiogames.net/post/62182
Re: Why "COMify" the SAPI support in C Sharp?
You can talk to One Core etc. by talking to the UWP APIs I believe. Those are available to non-UWP apps as well as a good variety of other UWP APIs.I'd just use Tolk. But if you're not going to use Tolk you have to cover several
Re: Why "COMify" the SAPI support in C Sharp?
@3My main problem with OneCore is that they don't let developers make voices custom for it, as well as not exposing the API, very easily and much of it, anyways, but that could change. The way NVDA has to talk to it is probably, i
Re: Why "COMify" the SAPI support in C Sharp?
Yeah, it does. If you want something that doesn't use com, try the c# wrapper for eSpeak, or the tts engine present in uwp, that uses the one core voices instead of sapi, a totally different platform actually. And you're right, the us
Re: Why "COMify" the SAPI support in C Sharp?
Erm, doesn't System.Speech.Synthesis.SpeechSynthesizer() use COM as a backend? I'm not positive, but pretty sure that's what I heard. So if that's true, the only thing you would gain are more source code lines. Oh and a headache from
Why "COMify" the SAPI support in C Sharp?
Hello!I heard some opinions on this forum stating that using iSPVoice interface is better than builtin System.Speech.Synthesis.Is it just a matter of personal preference or I can gain something from using COM? I am nearing finishin
