Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Voice2json: Offline speech and intent recognition on Linux

voice2json.org

Post reply on HN
Print view View original

111–114 of 114 posts

Re: Voice2json: Offline speech and intent recognition on Linux

#111

Post by dokem »

tootie wrote: post #82
dokem wrote: post #81

I can finally build the Jarvis home assistant I dreamt of when first learning coding in high school. To bad now I know voice assistant widgets generally are useless.

Speech recognition is actually orthogonal to AI. In my day the AI prototypes (like ELIZA) were basically chat bots. Speech recognition is now very sophisticated and accurate. Determining meaning from human language (spoken or written) is far more advanced than it used to be but still kinda sucks.

Yes, text to speech has become impressively good and can basically be relied upon. But siri/alexa still really disappoint me and dont seem to be much better than a list of basic rules one could program up.

Re: Voice2json: Offline speech and intent recognition on Linux

#112

Post by nwalker85 »

Edman274 wrote: post #58
nwalker85 wrote: post #38

Really interesting use of intents and entities. I feel like some of this is reinventing the wheel, since there is already a grammar specification, but novel use of intents/entities. https://www.w3.org/TR/speech-grammar/

Yeah, in my experience no one uses or supports that specification, which is a shame because if you're using something like AWS Connect with AWS Lex for telephony IVR, you can't just create a grammar and then have AWS Lex figure out how to turn its recognized speech-to-text into something that matches a grammar rule. Thus, Lex will return speech-to-text results that are according to general English grammar rules, rath…

Some do, some don't, sure. Google STT for example supports class tokens natively. There are also services like uniMRCP that allow for certain SRGS grammar features to be used with Google STT, but they are limited in what constructs they support. I've worked pretty extensively with a platform called Verbio, and they fully support the SRGS grammar specification. I work in conversational AI, and when I do implementations, I have to evaluate the complexity of the use case and whether or not a full grammar will be needed and choose a STT provider based on that.
Post reply on HN