Yeah, I recently added the UI installer. But that makes sense because it starts with an empty file before appending the parameters in the installer. The configure command pretty much skips all the install aspect, apart from running the config commands.
Huge thank you to you (and to randomuser123) for the work on this. Iāve got it running on a couple devices so far and itāa fantastic in so many ways.
Was trying to tweak it to stop getting as many false positive wakeword detections though and am having trouble finding how to modify the vad_threshold, any thoughts?
It needs to be set in the service file, open up $PREFIX/var/service/wyoming/run and you can set it pretty much at the bottom of the file as an extra parameter (wyoming-satellite-termux/services/wyoming-satellite-android at c2f10985011ecd1b86fdbd8c9921e5ab05b64512 Ā· pantherale0/wyoming-satellite-termux Ā· GitHub)
New line and --vad-threshold value \ after this line above will do the trick.
Forgive my ignorance, but Iām not seeing those directories in the termux home directory. I did find a threshold value in the setting.py file in the ~/wyoming-satellite/wyoming_satellite/ directory, I tried modifying it to see if that has the same effect.
Edit: I didnāt realize you could go above the home directory in termux, went one level higher and found the usr directory with the folders & files you mentioned, thanks for your help!
1 Like
No problem, $PREFIX is kind of the equivalent of / within a termux session. Although you can cd to / this is the root of the android system itself and not the termux data directories.
Even after adjusting the vad threshold to 1.0 Iām still getting way too many false activations and itās hurting the WAF, going to try swapping in a more complicated wakeword to see if I can reduce them. Is changing it as simple as dropping a new tflite file in the ~/wyoming-openwakeword/wyoming_openwakeword/models directory and modifying the wyoming.conf file to show "SELECTED_WAKE_WORD=āname-of-tflite-fileā?
what wake word are you using at the moment? Alexa has been pretty bad in my view. Improved slightly by changing the threshold to 0.7 but it still goes off if you breathe the wrong way or a dog barks.
Iāve been using āhey jarvisā, Iād assume that some others like āokay nabuā are probably better trained, but figured if Iām going to change it up I will try something with more syllables, since that feels like an obvious way to get less false activations.
Iāve loaded in some of the longer options from the unofficial wakeword repository here:
Iām away from home at the moment though, so hard to test it over a VPN lol.
FWIW, changing the vad threshold did not seem to have any noticable effect on the false positive activations, which makes me wonder if the change actually carried through.
Edit: tried running it with a new tflite model and got an error in handler.py line 244, presumably when it tries to validate/process the model filename. I kinda expected it wouldnāt be that easy, haha.
Thanks heaps for this amazing project! I was able to get it up and running on my FireHD 10" Tablet, after I did the modification above.
I was trying to run /script/run (expecting it to start the satellite after the modification) but it threw an error. I did then reboot the Tablet and thanks to Termux-boot, it started without probs.
(How could I start it from the console without a reboot?)
My question: I noticed the pick-up range of the microphone of this Amazon Tablet is quite low, @randomuser123 is it possible to select a microphone via Termux? I am thinking to add an USB-C microphone to the tablet to increase the pick-up range. But Iām not sure if Termux can handle different microphonesā¦
I havenāt tried that, but if the OS just picks it up automatically like a Bluetooth headset, then maybe it will just automatically default to that mic.