I'm happy that we're getting more and more lifelike text to speech voices using AI, but here's something you might not know. These AI based text to speech voices can be unpredictable. It's not that they say things wrong or mispronounce any more than other speech synths do, but what definitely does happen is that it does not say the same string of text the same way twice. It might change the intonation, or even sometimes the speed of certain syllables from utteration to utteration. I use my screen reader with the speed very, very fast. Often I don't pay conscious attention to exactly what words are spoken because I've gotten so used to the text to speech voices that I use that my brain does this subconsciously. They have certain patterns that I can recognize and this tells me what the synth just said without having to understand every single syllable or word. This is important for reading short texts like names of buttons, window titles, web addresses, messages, usernames, etc.
And let's not even talk about code. A natural voice reading code is just... it just doesn't work. It just feels totally wrong. I need to navigate through code very fast. Not only do AI voices have quite a bit of latency, but if I'm quickly scrolling through a file I'm listening to the actual words just as much as I'm listening for familiar sequences of sounds. AI based TTS don't have that because things are ever so slightly different.
This also means that cloud anything is absolutely out. If you're making web requests to get your screen reader to speak then stop right now. I won't use it, you wouldn't use it, nobody would use it. I guess Apple can do this on their new devices because of the M1 platform, but even there you can absolutely feel the delay between pressing the key and the voice reacting to what you've done. The simpler the tts, the faster the response time, the happier I am.
A fun, happy little Mastodon/Hometown instance. Join us by the fire and have awesome discussions about things, stuff and everything in between! Admins: @Talon and @Mayana.