@kovid,
Quote:
|
E-book viewer: Read aloud: On Windows switch to using the new Microsoft speech subsystem with access to more voices
|
Unfortunately this v6.12 update to Viewer Read aloud means I now have access to fewer voices, not more. I can no longer access any of my 3rd-party purchased IVONA voices. This is very disappointing. Is there anything I can do? I'm using Windows 11 Home in case that's relevant.
In v6.11 all installed 64bit voices, from both MS (incl. Cortana) and IVONA, could be made to work OK in both Viewer Read aloud and in my user plugin
TTS to MP3. In fact the list of available voices was identical in both.
In v6.12 only the MS voices appear in Read aloud. Thankfully IVONA and MS Cortana voices *are* still available to my
TTS to MP3 plugin.
Looking at
viewer-webengine.json
Code:
"tts_sapi": {
"voice": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\IVONA OEM NextUp OpenSAPI amy22"
},
"tts_winspeech": {
"voice": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Voices\\Tokens\\MSTTS_V110_enGB_GeorgeM"
},
it appears that a different Win registry key is now used for Read aloud. Is there any possibility of making installed voices from both old and new keys available to Read aloud?