Voice control
-
@Tomcattwo et al. – thanks for the steer to VA. I’m aware of that one too. I’m afraid my noggin exploded when I tried to look at the AVCS4 configuration – it’s very impressive but felt like massive overkill for my use case. I’ve got something now for VA that almost does what I want but at the expense of having a profile per ownship callsign which seems less than ideal.
[ I’d love a PM is someone has a VA profile that solves this for callsigns and airports but just focuses on the radio problem…don’t want to clutter up this thread with too much VA content ]
This thread though started with FoxVox questions and that was where I wanted to focus. There’s a lot of good info about it and getting it to handle command input seems quite well explained. What’s less clear is how or if it can adapt well to use for more realistic speech radio message translation to command input.
In other words, I have a fair idea of what VA can do in the context that I’m interested in. Asking questions here was more to probe what FoxVox can or can’t do
So: I’m still interested to hear more from FoxVox users and/or learn if libraries are out that oriented to the realistic phrasing translation…
-
@Boxer said in Voice control:
@Tomcattwo et al. – thanks for the steer to VA. I’m aware of that one too. I’m afraid my noggin exploded when I tried to look at the AVCS4 configuration – it’s very impressive but felt like massive overkill for my use case.
Foxvox is awesome, hope you have a great time with it and are able to get your stuff set up as needed.
First I’ve heard of any head explosions over AVCS4 configuration, though the feedback spurs me to further simplify and optimize first time setup and profile use for end users. My goal was to avoid creating a VoiceAttack plugin, so I went for the two profile approach with AVCS CORE as a base/background profile, and AVCS4 BMS to provide an “any way you say it” means to call any radio command in BMS.
There is a lot, but I can understand being overwhelmed just looking at my command reference for AVCS4 BMS (https://veterans-gaming.com/semlerpdx-avcs/profiles/commref/bms40.html/) and will take it to heart to keep working on simplification and ease of use.
Previous configuration hurdles such as setting a PTT button have already been streamlined to a simple voice command, “Set a Push to Talk Button”, with text-to-speech which prompts users to press the key/button they want to set (and ability to set up to 6 total PTT buttons on keyboard, mouse, or joysticks) in addition to an (optional) computer “name” to wake listening via voice command if desired, like, “Hey Computer…”
Best wishes whatever you use, voice commands are just perfect for BMS radios and crank up the immersion several degrees! Cheers!
-
@Boxer Not sure if you saw this one, but I think it addresses the issue of flexibility that you mentioned. The software is designed to allow flexible yet accurate recognition (insofar as possible - I could write a long and boring dissertation on the subject). Foxvox is designed to achieve good recognition quickly and easily for basic users, but has within it the ability to really hone in on tough and complex phrases with support words and the global library. You can also spend some time with the advanced logging to test and really perfect certain keys. I use long “realistic” (I’m no pilot so this is questionable) phrases all the time with near flawless results.
Anyway, I’d be happy to help in any way I can if you have a specific question or phrase you’d like to work on. Otherwise, it’s a free download so it’s easy to just give it a go and see what it can do.
-
thanks foxster, the new features look really impressive w/r to improving the recognition.
I’m just wondering would you have to set up key phrases for all the bases or would
“Approach”
not be sufficient if foxvox simply ignored the unknown / unrecognized airbase prefix?
Thanks & all the best,
Uwe
-
@oldtommyboy said in Voice control:
@oldtommyboy ok well i can get the program to regonize my comm 1 down switch on my hostas as the ptt and i can give commands,which it hears and shows in the program but cannot get it to work in bms.
When i push and hold comm1down,nothing happens.
But i do hear a click but thats it.
What am i missing?
When i close out of bms and check the program,it still shows my commands.
Do i need to change something in my config.
Like change my comm 1 in my config to ptt.
HmmWell any idea,s on this,works,just not in game,something simple im forgeting?
-
@hoover I use it with the wildcards set up and it works great imo. Just have some memorizing of keywords to do.
With the wildcards, I can transmit “Gunsan Tower, Goblin 1-1 Request Taxi for Departure”
It will key on Tower, Taxi, and Departure and execute that command.
For another example, “Gunsan Tower, Goblin 1-1 Request taxi Back to Ramp”
It will key on Tower, Taxi, and Back to execute that command. -
@oldtommyboy Bms must be the active window and make sure you have the correct outputs defined. You can test the output by opening a text editor like notepad and try the recognition (make sure the editor is the focused window). You will see the keys appear.
-
@hoover Keep in mind the new features in the vid were at v1.3 and we’re at 1.6 now. You can make Approach* work as a wildcard by adding the * (as shown) making it a wildcard meaning it doesn’t have to be the first word of the phrase.
In my video my hesitancy with wildcards is not that they don’t work but you need to be careful with them because you can start to get unwanted recognition using too many and creating too much flexibility. But having them available and using them correctly can make the software do some amazing things.
@TxMtb shows a perfect example of doing it correctly.
-
@foxster well i found the problem.
When i assign the comm 1 or comm 2 button on my hostas,your program assigns 2 keys,no idea why.
The second key it always assigned was my missile/ dogfight deselect button.
Anyhow after many changes back and forth to my config file,nothing made a difference, so i put everything back the way it was in my config file .
Then after messing around with your program, i find i could simply delete the second key, tried that and it now works.
Ugh!
Maybe i dont have something set right in my config but never had a problem.
O well,i got it working,now for tinkering. -
@oldtommyboy Something must be causing the second button to register. That can happen if you’re using another app like vjoy or joy2key. Good you noticed and deleted it. The ptt can bind to multiple keys on purpose but can be a problem if not intentional. Anyway glad it’s working!
-
@foxster no clue,i use the x52 and like everyone else,i use the 3 way rotary on the stick.
And i simply run bms,trackir and the x52.
Nothing else.
But yeah,not sure why others with the 52 havent noticed this,makes me think something wrong with my setup but been using it for years. -
When i assign the comm 1 or comm 2 button on my hostas,your program assigns 2 keys,no idea why.
The second key it always assigned was my missile/ dogfight deselect button.This happens because your DGFT switch is not on center when you record the UHF/VHF push to talk presses…FoxVox sees DGFT override or MRM override as pressed if that 3-way is not centered when you press another button like the radio switch. Ask me how I know
-
@Boxer uh, i’ll bite,how do u know, or should i say what to do.
there is no fine adjustment that i know of.
in the 52 control panel its just 3 position and looks right when i checked it.
my comm 1/2 4 way switch is on my throttle.
my 3 way is set as dogfight up, center is deselect and mrm is down, it was in the enter position and that position is the key that gets added.
not sure what im doing wrong but it seems like deselect key is a constant on.
did i miss something? -
@oldtommyboy – yeah, sorry, I was trying to be funny but the truth of it is that I made this error myself and discovered the double button recording thing. The “fix” is just to ensure your DGFT switch on the throttle is in the center position and then it should work as you expect when you subsequently record the radio switch button presses for the PTT.
-
Oh and I should add: you do NOT want to map a button to the center position of the DGFT switch. Instead use the HOTAS self-cancel setting in the config file and just map the DGFT and MRM switches to the up and down positions. The self-cancel option is exactly for this situation where people want to use all DX button mappings for HOTAS (which every sensible person does to avoid keyboard modifier key mess ups ).
set g_bHotasDgftSelfCancel 1
If you map a button to the center position of the physical switch then it will ALWAYS look like it’s pressed when it’s centered and in fact you will never be able to use the record function in programs like FoxVox without it seeing two buttons pressed at once.
sorry – should have added that above…it’s probably the important part…
-
@foxster – thanks for the pointer. I did see that one. And your version of “realistic” phrases definitely matches mine…wannabe rather than pro at this over here too.
I will as you suggest give it a go. I had a quick look at the basic starting library – I was curious about assisting phrases but I didn’t see any of those on a quick pass…am I just missing them??
-
@Boxer yep my 3way is on the stick but yeah its in the middle.
-
@Boxer yep my 3way is on the stick but yeah its in the middle.
AND … BINGO, thar she blows…
That is it i believe,i have the center position mapped to deselect dgft/mrn.
And it is not selected in the config YET.
Cant check now but im thinking thats it.
Fiqured it had to be active if selected
I did try putting sim do nothing in my key file in place of deselect but the key still showed up in the program.So i should put sim do nothing back in my key file and check the cancel in config to 1.
Think thats right.
I,ll check this tomorrow.
Thx -
@oldtommyboy so at the risk of laboring the point… I’m not sure what stick device you are using. However, what you want is to set it up so that it does NOT show windows a button press for the center position – i.e. when you look at the game controllers control panel applet for the stick, when the switch is in the middle position you don’t want it showing one of the buttons “on” (brighter red color)…if it does show that in the middle position and your controller programming will not let you stop it doing that…then I think you are just out of luck with the double recording thing…there’d be no way, regardless of what you map in the game key file to that switch position, to have FoxVox not see a button press there as well as whatever else you were actually trying to record.
Generally speaking controllers that always show a button pressed and held regardless are a no-no…I’d argue it’s bad design so I hope you can use a config program or something to not have it do that.
Good luck!
-
@Boxer I’ve left them off of the default library on purpose because I want the software to work fine in its most basic configuration. Start simple then add more complexity as needed.
The assisting phrases will help the speech recognition engine stay locked onto a particular phrase when it matches more words. Something to note is the command names are automatically used as assisting phrases by default so no need to duplicate those. For most scenarios I’ve not needed them by and large but they can make a night and day difference when used with a tricky phrase that needs to support more diversity. The more recognizable words found on a command, the more accurate the recognition. The global dictionary adds those words to all the keys as assisting phrases in the library and that can help as well. Words such as two ship, four ship, f16, and others defined in the dictionary can help.