FoxVox Free voice control software for BMS
-
It looks like I need to go through the retraining process though as the recognition rate is really bad. Iāve got a bit of an english accent thanks to growing up opposite the local NAAFI in my home town.
Itās probably not possible to āconvertā the library somehow so it works with english / uk?
Cheers, Uwe
-
@hoover you shouldnāt have to switch to en-usā¦just change the library language to the uk? version from the settings cog wheel menu next to the library name. Let me know if that doesnāt work, but you should be able to use it like you did before.
-
So does someone have a ready-to-use script for this with the usual ATC/wing commands?
-
@Logic go to @foxster 's library page that he mentions above : https://foxster.itch.io/foxvox-libraries . My library has all the radio comms from 4.36 with 2-3 keywords each. I like it like that because it is easier to remember. Hope it helps!
-
loading the library worked fine after the english/US language pack had been installed.
Before that I would see the error mentioned above, but now all seems to work fine.
For AWACS I added some more words like ācenturyā and āchavezā which the system now picks up as āsentryā and āchaliceā
All the best, Uwe
-
@hoover
Nice those ones, dear Uwe.
Especially if they are fit, I mean.With best regards.
-
@foxster thank you for this awesome tool
-
@njenga5 You bet, and thanks - hope you like it!
-
Having an issue with PTT function.
Have set up the PTT in global settings and mapped the keys.
But itās not working for some reason, can see that voice is being heard but get the constant Push-To-Talk preventing message on every command.
Tried setting the PTT sounds up and they appear to not not work either.
Have tried different keys/buttons/controller etc but always the same issue.
Any ideas? -
@TxMtb you also have to set PTT in each group. It is one of the little buttons on top of the group.
-
@Le_Beau Just tried that, didnāt work either unfortunately. Probably something easy missing on my side.
Edit: My bad, was assigning 2 push to talk buttons and it wouldnāt work, assigning 1 only and it works.
-
This post is deleted! -
Hm, thatās weird. I have my PTT config set to pinky / comms forward and it works perfectly.
Cheers, Uwe
-
@hoover While trying to narrow it down tried just keyboard with the M key, it worked, set up M key and throttle, (Warthog), mic sw up, neither worked then.
Tried just mic sw up, and it worked, added M key with it and again neither worked.
Goal was to have mic sw up and down to activate ptt. But neither work when both are there. -
-
@hoover Usually run TARGET on throttle only but have also tried without it running.
Did figure out that when 2 PTTās are entered, if you press them both at same time, it works. But either or does not. Maybe itās just how the coding is. Really like the simplicity of the program and it works very well.Tried using 1 button on throttle and 1 on joystick as you said and still same thing happens. But if I press both at same time it works.
-
@TxMtb You are correct, the software is programmed to require all PTT keys - not either/or. I can easily add an option to allow any key defined on the PTT to work rather than requiring all of them if that would help you.
-
@foxster Ahhh, that makes perfect sense then! Thanks for the info, can quit scratching my head nowā¦
Pretty sure I can work this out with the individual command group PTT settings.Thanks again for your reply sir!
-
-
Hey foxster,
Iām just trying out the latest release, and Iām seeing a lot of invalid voice recognition attempts from foxvox when it shouldnāt even be listening (with āpush to talkā enabled).
would it be difficult to turn off Voice recognition completely when PPT is enabled and the button combo is not pressed? thatās the only time I want foxvox to listen for commands, it should be turned off / inactive / not attempting to make sense of all other sound inputs when the PTT button is not pressed / active.
All the best,
Uwe
-
@hoover That became a little tricky when I added ptt independently to individual voice groups because you can have some with ptt and others without. I needed to see when a command was rejected due to ptt vs not recognized. Iām thinking maybe the best thing would be to add a logging option to enable logging when a phrase is rejected due to ptt with the default being off. The truth is that phrases are constantly evaluated either way, itās just a visual cosmetic but I can see why youād want it off, although sometimes itās better on. Thanks for the suggestion.