Voice control
-
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.
-
@Boxer @oldtommyboy There have been other instances where joysticks have sent a continuous button press in the past that I came across. In FoxVox you can completely ignore those buttons if you want in the library settings area of the app. Then they won’t be a nuisance any more, but keep in mind they will be completely ignored by the app unless removed from the ignore list.
-
I have the same “issue” with my Warthog. Whenever I want change the PTT combo I have to move all switches on the throttle (DX) into positions where they don’t register as continuous button presses. It’s no biggie but something to be aware of when assigning your PTT key combo of choice (in my case it’s pinky shift & COMMS up)
Cheers, Uwe
-
I have a feeling that the key will show in the program regardless of leaving it blank or sim do nothing or even leaving deselect in place.
I will check today, thx all
Funny because i have deselect assigned twice in my key file ,the second time in the shifted dx keys.
Guess the program doesn’t show the shifted key.
Of course im not holding the pinky shift in either.
So im thinking just delete the command in the program.
Thx -
@hoover if you go to setting, right under the PTT is a point Blocked Inputs. There active buttons can be filtered out
-
@foxster said in Voice control:
@Boxer @oldtommyboy …the ignore list.
That’s a neat solution to the problem. Once again, good software works around badly designed hardware
-
@foxster said in Voice control:
@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.
I guess I’d like to understand the theory of operation for both the global dictionary and the assisting phrases elements. Since there aren’t any examples that I can see it’s a bit hard to discern how one might use them, why and in what kind of forms – I think the “such as” mention above is the most detail I’ve seen so far. Have I missed a video on that topic also?? (very possible of course! )
Are assisting phrases considered at specific points, anchored or looked for in the group and command in particular placement?? Similar question for the global dictionary – how is the recognition code using those in practice??
I recognize I’m straying off the OP topic quite a bit…please tell me if starting a different thread would be better.
-
@Boxer Trying to keep the explanation simple, the assisting phrases are added to the grammar definitions just like the recognition keys which helps the voice recognition “understand” what is being said. The difference is that the software knows to ignore them as they are optional assisting phrases only so it’s ok if they are missing.
I really should do a video tutorial on why/how they work to improve recognition. I’ll try to add it to my todo list
-
@foxster said in Voice control:
@Boxer @oldtommyboy There have been other instances where joysticks have sent a continuous button press in the past that I came across. In FoxVox you can completely ignore those buttons if you want in the library settings area of the app. Then they won’t be a nuisance any more, but keep in mind they will be completely ignored by the app unless removed from the ignore list.
@hoover said in Voice control:
I have the same “issue” with my Warthog. Whenever I want change the PTT combo I have to move all switches on the throttle (DX) into positions where they don’t register as continuous button presses. It’s no biggie but something to be aware of when assigning your PTT key combo of choice (in my case it’s pinky shift & COMMS up)
Cheers, Uwe
@Boxer said in Voice control:
@foxster said in Voice control:
@Boxer @oldtommyboy …the ignore list.
That’s a neat solution to the problem. Once again, good software works around badly designed hardware
Wanted to add my 2 cents on this - some food for thought from a programming perspective - since I found some of these same challenges when I was creating a PTT system to initially “get” the key/button that users want to assign, and then monitor for a PTT key/button “pressed” states.
Dual stage triggers, multi-function buttons, and 2- or 3-way toggles were making things very difficult. These have one button always down and depending on the firmware, it could be recognized when trying to set a button/key inside some other software like BMS, or FoxVox, and of course my own AVCS4 BMS VoiceAttack profile. Telling my PTT scripts to ignore or not use these types of buttons for PTT was the first way I dealt with these, until I got more proactive.
I ended up creating a number of additional functions in my program, most importantly starting with building a ‘baseline state’ of all mouse, keyboard, & joystick controller buttons - looping through each key to build an “always down” list. Only after this has been done should the user be able to “set” a PTT button to be captured and saved by the program.
During capture of the key to save, I found using that “always down list” allows evaluation for an “opposite state” rather than just checking for which key/button is in a “pressed” state, and I built my functions like this:
BuildAlwaysDownList() ...(then when user is prompted/able to "set" a key/button)... GetReverseMouseButton() GetMouseButton() GetReverseKeyboardKey() GetKeyboardKey() GetReverseJoystickButton() GetJoystickButton() GetReverseJoystickPOV() GetJoystickPOV()
Of course, during normal operation of voice control, any saved PTT keys/buttons will have an additional boolean flag if they are a “reverse” style. This way, the “PTT check” function (looping in the background) can know to watch for this same sort of “opposite” state rather than simply a “pressed” state, and eliminating the issues with “always down” buttons like Dual Stage Triggers or toggles on sim-pit controls for a PTT system.
-
Wow,you guys are so over my head,i feel like a idiot ( of which i am ) but appreciate all the help.
Anyhoo,so i went in my key file and replaced the deselect key to sim do nothing and added the 1 instead of 0 in the config file .
Started foxvox , went in the library,cleared the ptt assigned then reassigned the ptt with the comm 1 down.
Sure enough,the same two keys showed up .
So i simply clicked on the key i dont want and deleted it .
Now when i started bms i went in my settings,loaded my file and now where it used to say deselect,its simply says bms full which is my profile
But flew a mission and it worked better than i expected, no problems,had to repeat words once in awhile but still learning .
Anyhoo, tinker time. -
@oldtommyboy what you observed makes sense. The key file content is not involved in the business of FoxVox seeing two buttons pressed from your DX devices – that comes from the device hardware and Windows DX device driver. If you can’t change the behavior of the device, via programming software for it, to make it not show use always on buttons for some physical switch throws then I think you are stuck with your workaround or using the ignore list that @foxster put into the FoxVox program for this kind of situation.
-
@Boxer thx, u know i always wondered why whenever i start bms and go to setup,select my key file,load and always noticed that dgft/msm deselect was shown .
Now it just loads and showing bms full, my file name.
So it has always shown as activated,never really thought about it till using foxvox.
So now its still activated i guess even though nothing to activate.
Confused on why that particular key , something still not quite right in my key file, no clue.
Anyhoo, thankyou
Till my next WTF !!!