I don't see (or hear?) the advance here...
Edit: Yes, that example was unfair, because it's from the 90s (and actually, DECtalk was largely unchanged since the 80s, until it was ruined in the late 90s). Here's a somewhat more recent one: With the ETI-Eloquence engine, which was last updated in 2002, the string "2 Marketing" (which one might find, say, in a Wikipedia table of contents) is expanded to "March twond keting".
Someone linked another example here:
https://soundcloud.com/zack-bloom/amazons-new-text-to-speech...
And it pronounces 1970s (the decade) as one-thousand-nine-hundred-seven-ths.
I don't know if this is crossing into uncanny valley territory. I think some of this is not being used to it.
Google Map's driving voice sounds subtly better than that voice sample. I'm looking forward to seeing if a similar service is coming for GCP.
This would drive me nuts, as there's no easy way to predict what sort of transformations it would make. Basically, if it's not near perfect, it's arguably worse than no intelligence at all.
With our PBX stuff, I know it's dumb, so I'm already accustomed to giving it something I know it will read correctly, like "domain dot com".
I believe that's what the Lexicons are for within the service.
I read the post I was replying to as some sort of undefined, built-in, set of intelligent transformations.
For example, 75F-> 75 Fahrenheit would require that you make a Lexicon entry for every value...1F, 2F, 3F, etc. That's not really intelligent :)
Polly 1: https://d0.awsstatic.com/product-marketing/Polly/HelloEnglis...
Polly 2: https://d0.awsstatic.com/product-marketing/Polly/HelloEnglis...
WaveNet 1: https://storage.googleapis.com/deepmind-media/pixie/us-engli...
WaveNet 2: https://storage.googleapis.com/deepmind-media/pixie/us-engli...
There just isn't a comparison -- Polly sounds way more robotic.
WaveNet is Google's, and I'm saying that this is significantly worse.