http://qs321.pair.com?node_id=11149689


in reply to text2speech and speech recognition for perl in 2023

I found that the hardest part for voice recognition is not implementing it in your program. At least for me and my own speech patterns, most systems go as far as "i recognize that this is a voice you are using" before giving up and selecting some random action in the vague hope that this is what i asked for.

The best solution so far (at least for me) is using one of those Echo dot thingies and creating a module/app/whateveritsname on their site that RPCs my own home automation system. Google also has good voice recognition.

The problem ATM is that any locally installed version will almost always be inferior to what Amazon and Google can do, simply by throwing Petabytes of training data into their data centers to train some neural network. And then run that neural network on their custom-made neural network processor hardware.

If you don't mind Google listening in, you can try their speech-to-text models for free if i'm not mistaken. After that, it costs 2-3 cents per minute. The sad thing about this is, with current energy prices, it's probably more expensive to run an (inferior) speech recognition locally. There are client libs for a few different programming languages, shouldn't be impossible to re-implement one of those in Perl (or just control an external program)

There is also the possibility to use your browsers speech recognition (also uses the Google cloud in most cases) and sending the recocognized text to the perl webserver of your choice. BTW, browsers also have a build-in text-to-speech API.

Putting it in a website could make your application a bit more flexible, since you probably have a matching client in your pocket (=smartphone), so you can control your stuff by speech from everywhere. Basically, you outsource all the speech stuff to your browser, and do all the cool and interesting stuff in your perl backend.

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP