I installed mycroft (18.08, rel 3) on my ubuntu 16.04 machine. All works great using pocket-sphynx and “hey mycroft” for the wake word. I thought the default was precise. Anyway, I asked mycroft to switch to precise and it complied. I waited long time for it to complete since there is no response saying when it is done. But now using precise it will not respond to the wake word. I have tried many things including restart, reboot, and reinstall. Using debug cli I confirmed it was using precise and the log shows it was loaded (see botom). There are no errors on loading. And using cli I can return to pocket-sphynx and it works again. Do you know how I can get it to use precise? I want to train my own wakeword and using pocket-sphynx had less than desired results.

More info. When I restart mycroft after changing to precise I do not see any lines in log about loading precise wakeword. I just get this:
18:31:37.511 - mycroft.client.speech.listener:create_wakeup_recognizer:263 - INFO - creating stand up word engine
18:31:37.513 - mycroft.client.speech.hotword_factory:load_module:261 - INFO - Loading “wake up” wake word via pocketsphinx
Perhaps precise is not being started.

I tried to replicate this on my Ubuntu 18.04 LTS system, and also found some anomalies. Firstly, I tried to see which listener was being used, and for some reason, PocketSphinx was being used, event though my Wake Word was the default Hey Mycroft. Using the phrase set my listener to Precise, Mycroft then tried to switch to Precise.

However, Mycroft kept trying to download Precise for over two hours with the message:

Your issue specifically is that Precise appears to be your default, but it is not activating

Why wasn’t Precise installed correctly in the first place

Precise not triggering

At a guess, I think what is happening based on the log file is:

Precise is trying to activate but cannot

And Mycroft is falling back to PocketSphinx

This doesn’t explain though why the Wake Word is not triggering for you when set to Precise.

Conclusion: I don’t think Precise is installed properly. Can you please try a command line install as shown above?

Precise not being correctly installed

I looked at the /dev_setup.sh and requirements.txt in mycroft-core, and the only thing I can think of is if we need to add mycroft-precise into requirements.txt - as it is not installed directly in /dev_setup.sh. I’ll try a new build of mycroft-core and see if this works.

Thanks so much for helping. It is getting very frustrating. Most works but can not get precise to work. I did the manual install as you suggested and no difference. Precise is loading but it just goes to pocketsphinx and when I ask to go to precise it complies but then I get not response from hey mycroft.

I next tried this one and put “mycroft-precise==0.20” into requirements.txt as suggested. Got error when I ran dev_setup.sh. I noticed before that precise was ver 0.2.0 so I changed requirements.txt to that ver and the setup succeeded. However, the result did not change. I will not use precise and when forced it will not respond. Don’t give up on me.
Ron

Well, we at least know that Precise is installed, but I don’t know why precise-runner did not install it properly. The issue is not just on your machine, I had the same issue here on Ubuntu 18.04 LTS so it’s more widespread. My log analysis didn’t show anything obvious I’m afraid.

But let’s turn our attention to why Precise is not activating properly for you. You’ve confirmed that you’re using the Default Wake Word of Hey Mycroft, so it’s unlikely to be a custom Wake Word setting issue (more information on setting a custom Wake Word here).

We’re definitely not going to give up on you

Are you comfortable telling me;

Do you have a strong accent at all (I grew up in Northumbria so totally understand Pitmatic, Geordie, and Mackem, not so good with the West Country ones

It may be that we don’t have enough samples of your particular accent for Mycroft to “recognise” your utterance of Hey Mycroft as the Wake Word. Are you opted in to our open dataset?

@KathyReid “precise-runner” downloads the proper “precise-data” binary, but fails to properly extract the archive. Because of that, it fails to finish the “set to precise” process. Configuration wise it however says the listener is set to precise however, because the process is not properly finished Mycroft ends up in sort sort of “in the middle state”.

My guess, however not confirmed yet is that Debian based systems updated some of the tar / gzip packages and therefor the python bindings to it have changed and are bugged at the moment.

Yeah the trick is that precise-runner is failing to install precise-data, but this failure does not show up in voice.log. I think I need to closely watch a Linux install from scratch and see if I can see the failure, possibly pipe stdout to a file for later examination. Will report back.

I know you are further along in the problem but to answer your question, no I do not have an accent
and have no problem with other SR pkgs. Mycroft with pocketsphinx works just fine. Not so well on
a custom wake word which is why I would like to use precise.

So, the problem we’re trying to solve now that Precise is installed, is why it’s not recognising your voice when you say the Wake Word. Is it still falling back to PocketSphinx or is it trying to use Precise to hear the Wake Word and not recognising it?

Can you show me your current log output / screenshot of the CLI?

(Sorry to go over old ground, I just want to make sure we’re diagnosing from the right spot)

I thought the problem was determined to be that precise-runner is failing to install precise-data. In any case below is the log with my comments in '()'s. I have to be away from my office for a few days so I will not be able to provide more debug info directly but will be able to answer any questions and continue in the discussion.

At one point I did manually install precise but not sure if available to this vir env. I do not
work much with python or the vir env
stuff so not sure if it is using that one or other. Anyway, have you had luck with a fresh install
on a ubuntu 16 or 18 system yet? I am happy to uninstall things and do a fresh
install (not OS). But that will probably not happen till next Monday as I am away from my system this
week. But I am excited about using your stuff with my research work here at Bell Labs. And
I would like to work with you all to extend it possibly. Right now just skunk works. Thanks
again for your help, I am sure you are working a thousand issues at once.

I am back and still trying to get mycroft running on ubuntu 16.04 on x86_64. Just in case something changed (for the better) I reinstalled mycroft per instructions and ran it. Unfortunately now I can not even pair the device as it failed to connect to mycroft when I ran start-mycroft.sh debug . I am able to ping mycroft.ai so the computer can get to the host. I even tried on a different computer which I did not update and it could not get to mycroft.ai. I do not see anyone else having this problem. Any ideas? Thanks.