4 ms·
We can translate spoken words to text strings pretty reliably. AFAIK, we can do this locally without much processing power, but I may be mistaken. From the poin
by stephengillie 8y ago
We can translate spoken words to text strings pretty reliably. AFAIK, we can do this locally without much processing power, but I may be mistaken. From the point that spoken words become strings, chatbots and voicebots are effectively the same.
Those strings are piped through a Switch statement of static responses, or fall out into the Default response. This was the situation in 2013 when I created a speech bot in Powershell, and it sounds like the state of the art here hasn't progressed far.
What's needed is logic to dynamically build the Switch statements, or otherwise better parse human entry and build responses. There has been much work on a few different fronts, but I'm not aware of any which were wildly successful.
- ghaff 8y ago>We can translate spoken words to text strings pretty reliably. AFAIK, we can do this locally without much processing power, but I may be mistaken. Cloud services backed by big data sets tend to be better although I admit I haven't tried a local copy of Dragon Naturally Speaking for a long time. In any case, at least assuming fairly mainstream American/English accents, the voice recognition isn't really the problem any longer. Sophisticated NLP and responses are. We're a long way from virtual assistants that can do anything sophisticated.