Windows Registry Editor Version Stefan - German (Germany)" With the modifications it should look like this (take special notice to the key paths): Remove the entire line for the attributed called SayAsSupport, it is not needed by SAPI. All you have to do is change both references from Speech_OneCore to Speech. Both will make a reference to the key Speech_OneCore. Open the exported file with Notepad or similar.
The easiest thing is to right click the voice key (MSTTS_V110_deDE_StefanM) and from the context menu select Export to save the entire voice structure to a file (this will later allow you to easily replicate all these steps into a couple of clicks if you want to do this in another computer). The German male voice in my case is called MSTTS_V110_deDE_StefanM. There you will find each WinRT voice registered under its own key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens But after studying the Windows registry and a couple of files referenced in there, I noticed that both APIs use the same data files so I copied the registry keys from the German male voice registered in WinRT API into the corresponding SAPI section. In Windows 8+ there are two speech synthesis programming interfaces (like explained by Eric Brown).
Works for 32 and 64 bit programs (natively or WOW). So I did this "hack" and surprisingly worked right away (Windows 10 version 1803). I needed to make a desktop (not universal app) program in C# that utilized the male voice but it was not available through SAPI.
In my case, under Windows 10, I installed the German language with TTS package and it installed a female voice (WinRT and SAPI) plus a male voice (WinRT only).
PS: I don't really know if I chose the right topic for this question, feel free to redirect me to another if needed.I managed to fix this issue by modifying the Windows registry.
Please note that Ayumi is already set as my TTS voice in Settings app, but as I said above, Windows 10 doesn't seem to care about these settings. I'd like to set my TTS voice to Ayumi, yet Ayumi isn't a choice in Speech Properties (see the screenshot below).ġ - What is the difference between those two settings, and why don't they feature the same voice?Ģ - What can I do to set Ayumi Mobile as my actual TTS voice (in Speech Properties). Windows 10 (mine, at least) actually uses the voice set up in Speech Properties, and doesn't really use the Setting app setup. It seems that the TTS voices appearing in Windows 10 "Settings" app don't match the ones appearing in the "Speech Properties" windows (which is findable in Control panel). I've already downloaded Japanese language pack. Recently I've been trying to set my Windows 10 TTS in japanese. Use mobile TTS voices as desktop TTS voices I couldn't gain control of the entries, either.ĭoes anyone know a way of accomplishing this? Thank you! I created a restore point and I tried to modify or delete those voices using regedit as an administrator (and also in safe mode) but it gave me an error about permissions. For instance: keep Microsoft Zira but delete Microsoft David (both US English, ) and so on. Now I wonder if it would be possible to delete, or at least hide from other apps, some of the Microsoft voices I don't use. But, I was able to make the necessary changes for individual voices to be detected (in this case by Balabolka) using something along the lines of: Unlock all Windows 10 TTS voices system-wide to get more of them - gHacks Tech News Many of these voices remain hidden to other applications. I have installed the voice packages for several languages through: Settings/Time & Language/Speech/Add voices. Hello, I use a program called Balabolka that can detect the Microsoft voices installed in your system and read texts to you using those TTS voices. I'm using: Windows 10 Home, version 1909.