3 ms·
I'm conditioned to do this trick in reverse, say to look for a recipe or song in French. Speaking the title in a horrible American English accent gives at least
by z2 7y ago
I'm conditioned to do this trick in reverse, say to look for a recipe or song in French. Speaking the title in a horrible American English accent gives at least a 20% chance that Alexa would understand the query, as opposed to 0%. I'm not familiar with the problem domain at all, but it seems speech recognition is just as bad as TTS or worse at recognizing what language is being processed. Or maybe the problem for both directions is that there is simply no effort to even classify the language first.
- visarga 7y agoI think the problem is that you have only used mass-grade TTS. Google can't deploy the latest and greatest for the billions because it would be 10x more expensive for them, while a small local TTS doesn't have the power to cover every situation. In demo situations it would be a whole different thing. I have followed the papers on TTS and listened to the demos. For example my MacOS system voice Alex often confuses 'live' (to live somewhere) with 'live' (as in live concert). That's because they have a simple model that can run on a laptop and not use too much space. This sample phrase tested on Google cloud TTS is perfect.
- noneeeed 7y agoI have the same problem with Alexa. I was trying to get it to play Keith Jarrrets "Köln Concert" album. I doesn't matter how I pronounce "Köln" I cannot get it to understand what I want. I ended up having to create a playlist for it with a different name.