Alex Krier

@AlexSpectrum93@dragonscave.space

I love text-to-speech (TTS) synthesizers, and do music production/audio exparimentation.

I can't believe its been 10 years since NOAA Weather Radio transitioned from the Console Replacement System (CRS) which used NWS DECtalk, AT&T Mike (later replaced with Speechify Tom), and AT&T Crystal (later replaced with Speechify Mara) for English, and Speechify Javiar for Spanish, to the Broadcast Message Handler (BMH) which uses NeoSpeech Paul for English and NeoSpeech Violeta for Spanish. Personally, I would've chose James instead of Paul, since I think James has that more formal professional intonation perfect for weather related events, Paul sometimes sounds a little bit high pitched.

One thing I have to let everyone know about the Google TTS NVDA addon is, don't switch to another synth while you are using the "Google" natural/neural voices. If you restart NVDA, initially use another synth like Tiflotecnia/ Cerence, Flite, OneCore, RHVoice, and you attempt to switch back to Google TTS, it won't speak. The reason why is, Google TTS expects the Chrome OS (HMM-based) voices to be loaded first before you choose any of the natural (neural) ones, and this happens per language, so if you were using US English HMM voices, and than attempt to switch to natural Nigerian English, it won't speak until you select one of the Chrome OS voices. I prefer the Chrome OS ones anyway, so I don't have to deal with it not speaking.