English isn't a phonetic language, but text-to-speech needs to use specific sounds for each letter/syllable (each sound is called a phoneme). So there is usually a dictionary or set of rules to determine how to pronounce a word. Laughter vs daughter for example, polish vs Polish. If a word was pronounced incorrectly, the word probably wasn't in the dictionary and it was trying to pronounce it using the rules. Some of the improvement is just the improvement in the phoneme sounds used for text-to-speech. Some early computers didn't have the ability to playback digital samples, they didn't have much storage or access to internet, so they couldn't have recordings for every word. They had to approximate the sound using the capabilities of the sound chip. (Commodore 64 SAM: https://www.youtube.com/watch?v=B4_fjy9b7WI , and the rules: https://github.com/DLehenbauer/c64-sam/blob/main/src/sam.s ) Newer text-to-speech uses digital samples for phonemes or even the entire words. More on reddit.com

So you need a speech synthesizer, OS's conveniently come with one built in, and Godot also has the means to make call's to it. https://docs.godotengine.org/en/stable/tutorials/audio/text_to_speech.html The downside is its not going to sound exactly the same on every system. Making a custom TTS engine would be a lot of work, and personally the best solution would be to pre-record the voices and implement them as audio files. More on reddit.com

betterSam works you just need to change the settings a bit oh and better than work well with FAITH: the unholy Trinity characters as well More on reddit.com

I built a fun little side project that recreates the classic Microsoft SAM voice from Windows XP—entirely in the browser · SAM TTS uses phoneme-based synthesis (no AI models), written in JavaScript with Web Audio API. You can type any text, adjust pitch/speed/mouth/throat settings, and instantly ... More on news.ycombinator.com