I'm currently working to add voice recognition to some of my embedded projects. The requirements are:

  1. Must be able to listen continuously
  2. Run on embedded ARM processors (particuarly Raspberry Pi and BeagleBone Black)
  3. Good accuracy on a limited set of words (English only)
  4. Decent performance, particularly on low-power CPUs

My first thought was to use Google Speech API. The accuracy is great, and it's reasonably fast. But it is also limited to only 50 calls per day, so it wouldn't satisfy my requirement #1. And I don't like the idea of streaming all of my personal conversations to Google. It's already enough to have NSA listening to my phone calls...

(maybe it's an option for the future, when implementing something with a physical push-button, like a Star Trek communicator device)

SiriProxy is another neat hack, but it doesn't work with iOS7/8 anymore. Apple will soon offer an official interface to Siri via its HomeKit program, but it'll only work with licensed hardware. Likely not an option for hackers and personal projects.

After some research, I found CMUSphinx project, which seems to be the best project in the area of voice recognition. PocketSphinx toolkit is the version you want for embedded CPUs, as it's pure C, and rather portable.

The documentation is not very friendly, but once you get it going, it works well.

The first step is to download and install SphinxBase, followed by PocketSphinx. The README has instructions to compile and install, but it's the basic

make install

By default it'll install binaries to /usr/local/bin, and language models to /usr/local/share. Make sure you have swig and alsa drivers installed before starting (apt-get install swig alsa-base alsa-utils).

Once installed, you need to figure out which dictionary model you want to use. Just for testing, I created a dictionary with 106 words, based on the old Logo language (remember the Logo turtle?), like forward, backward, turn right, turn left, etc.

Before you can start training PocketSphinx, you'll need an acoustic model. Sadly, the speech corpus (i.e., audio files with spoken words) used to train the models are usually closed source. So either you spend a couple of hours recording the voices (or using an4/Voxforge) to train your own model, or you'll skip this entirely and just use some of the built-in models, accepting lower accuracy. Given my limited number of words in the dictionary, I decided to go with built in acoustic models.

Next, you need to describe your Language Model - the words, grammar, and frequency of words that you want to recognize. This tutorial has more details. If you're in a hurry and just want to get PocketSphinx going with a dictionary for your pre-defined words, save yourself some trouble and use the online lmtool. This webservice will allow you to upload your dictionary file (a simple ASCII file, with one sentence or word per line), and it'll generate all the language models you need to run PocketSphinx.

Here's a sample of my dictionary file:

    square root
    wait until

If you want to play with this dictionary, download these files here, and run:

pocketsphinx_continuous -lm lm/logo.lm -dict lm/logo.dic

(note: if pocketsphinx is stuck at READY, it's probably listening to the wrong hw device. Check where is the microphone attached via cat /proc/asound/cards, and add -adcdev plughw:X,0 to the line above, replacing X by the hardware id of your microphone).

pocketsphinx_continuous -lm lm/logo.lm -dict lm/logo.dic -adcdev plughw:2,0

Smartphones use all sorts of tricks to cancel the background noise, but that requires special hardware, so you'll need a reasonable quiet environment. Otherwise the accuracy will suffer, depending on how large your dictionary is.

As you would expect, smaller dictionaries have much better accuracy. With a 100-word, I got 60-70% correct. After I reduced to a simple 15-words dictionary, I got virtually 100% match rate, even with some background noise and a non-American accent. Certainly enough for my projects.

Next up: running this on a Raspberry Pi, installing a decent openair microphone, and testing overall performance when connected to a home automation system. Stay tuned!

Blog Logo

Gui Ambros

Maker, engineer, ad:tech veteran. Incurable optimist. I was there when the web was born. Opinions here are my own. @GuiAmbros



/dev/random rants about technology, electronics, startups.

Back to Overview