I love your app so much.
I found that when I say "Tower", the engine recognizes it as "," for some reason.
So I added "," to voice keys and the engine then recognizes "Tower" perfectly but on saving the profile or toggling voice recognition, the app shows "phrase cant be an empty string" error.
The app is still usable since I just need to add the voice key manually every time but I will be very grateful if you can fix it.
Thanks for your report. That is really strange...I have seen the voice recognition come back with garbly-goop before, but only when using my laptop built-in mic which was picking up fan noise while I was speaking (and I think it also may have happened while running multiple instances of FoxVox at the same time). Odd that you say the "," is consistent, though, as I've only ever seen it on rare un-repeatable occasions. I will keep an eye out for any information on what might be happening. Please look into your microphone's recording clarity as well, just in case there is any issue there - perhaps go through the windows speech training one or two times as well.
Apparently, to train the "English" recognition model, windows UI lang has to be English too and I don't really want to change UI lang... but it might be worth trying to see if training can solve the problem later.
I turned off everything that was making noise but the issue still persists and confidence level is always around 0.93.
My microphone is blue Yeti nano so its not very bad.
As a programmer, I understand that handling "," for a special case like this is very annoying and not worth the effort :(
