AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@SemlerPDX
I’ve tried adding a PTT button using your “set a push to talk button” command but then messed it up and I think it’s now set to a button I don’t want. Is there a way to check if this happened and how do I remove it? Thanks!I’ve added a PTT button but comparing the activation and deactivation time between the PTT added via your profile vs. the default PTT set in VA, there seems to be quite a bit of lag with the added PTT? Is this normal?
-
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX
I’ve tried adding a PTT button using your “set a push to talk button” command but then messed it up and I think it’s now set to a button I don’t want. Is there a way to check if this happened and how do I remove it? Thanks!I’ve added a PTT button but comparing the activation and deactivation time between the PTT added via your profile vs. the default PTT set in VA, there seems to be quite a bit of lag with the added PTT? Is this normal?
Yes, that is normal and should be inconsequential. My PTT system functions without issue regardless of the difference in timings between it and the native PTT mode in VA. Listening will begin as soon as the PTT button is pressed, yet mine will stop listening slightly slower when released, though this should not cause any issues. If it ever does, please report and I’ll look into it.
I assume you found the way to delete a PTT button, just say, “Edit a Push to Talk Button”, and follow the prompts to select any entry, and then in the next pop-up we can choose to edit or delete that entry.
-
@SemlerPDX said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@Atlas Thanks for the suggestion! I’ve gone ahead and added that content to the AVCS Wiki page here:
https://veterans-gaming.com/wiki/vg-labs-projects/avcs-wiki/avcs4-bms-manual/The command recognition phrases for wingman are inclusive of the word “to” as shown here:
I’m not sure what could be interfering with these, but you can enable the VoiceAttack event log to show the confidence level of all recognized (and rejected) command phrases. The default confidence level is 50.
If you can take a screenshot of the VoiceAttack event log showing “to rejoin” as unrecognized with proper confidence above your minimum confidence level, we could consider that a problem worth troubleshooting. I cannot reproduce that:
(I culled the “two” from the prefix command for this test, and “to rejoin” worked just fine for me…)A bit of a post necro but I’m setting up VA again with your profile and got the issue here:
As you can see, “to” was recognised before but no confidence level so I turned it on and managed to do it again. Funny that the confidence level is higher at 68 with the wrong one vs. only 66 with the correct one.
-
@SemlerPDX said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Yes, that is normal and should be inconsequential. My PTT system functions without issue regardless of the difference in timings between it and the native PTT mode in VA. Listening will begin as soon as the PTT button is pressed, yet mine will stop listening slightly slower when released, though this should not cause any issues. If it ever does, please report and I’ll look into it.
I am basing the delay on the “on” and “off” sound that VA makes when I press the button. I believe this does not make the same sound when in-cockpit. Comparing when the sounds come for the “on” and “off”, it is near-instant with the VA-PTT whereas there is definitely some lag with using the PTT set through your profile.
Are you saying voice/command recognition starts as soon as the PTT is pressed even though there is a lag in the “on” sound?
I assume you found the way to delete a PTT button, just say, “Edit a Push to Talk Button”, and follow the prompts to select any entry, and then in the next pop-up we can choose to edit or delete that entry.
Yes sir, just did it again and found the option to remove it.
-
@Atlas So long as the voice command executes, the confidence level (which is hidden by default, unless turned on) isn’t really an issue. If it becomes an issue, you can attempt to lower the default Confidence level which is a threshold for recognition accuracy, train your speech engine for the specific pronunciation of a word, or perform speech training session completely through additional times (at least 3 is recommended, though thick accents may benefit from more).
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Yes, that is normal and should be inconsequential. My PTT system functions without issue regardless of the difference in timings between it and the native PTT mode in VA. Listening will begin as soon as the PTT button is pressed, yet mine will stop listening slightly slower when released, though this should not cause any issues. If it ever does, please report and I’ll look into it.
I am basing the delay on the “on” and “off” sound that VA makes when I press the button. I believe this does not make the same sound when in-cockpit. Comparing when the sounds come for the “on” and “off”, it is near-instant with the VA-PTT whereas there is definitely some lag with using the PTT set through your profile.
Are you saying voice/command recognition starts as soon as the PTT is pressed even though there is a lag in the “on” sound?
Yes, that is exactly what I am saying. Please report back if that is not the case when you use my custom PTT mode. I would absolutely recommend disabling notification sounds including this one for Start/Stop Listening in VA - they can be both distracting and immersion breaking.
-
@SemlerPDX
Thanks! Will test.So… a slight issue – the two Global options seems to be the “correct” option and they both work when using the set PTT button, which is to listen as long as the button is held and to stop listening once the button is released. This is the default behaviour of my VA-assigned PTT button as well, but when I set a PTT button via your profile, the VA-assigned PTT stops listening after 2-3 seconds even if the VA-assigned button is still held down.
-
@Atlas You should not be using my PTT system alongside the native PTT system in VA. They will conflict with each other, naturally this is undesirable behavior.
(also, to be clear, there are two entries only because one is a state identifier showing the current setting … if you had selected the ‘DEFAULT’ mode, you’d see two entries for this instead. The fact that there are two of any item in this drop down list is merely a product of the dynamics that display this list - it’s a non-issue, is what I’m trying to say)
-
@SemlerPDX
Hmmm… so I guess I should un-map the VA PTT and just use your program to map it?
If I do, which of the above options is the most appropriate to select? -
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX
Hmmm… so I guess I should un-map the VA PTT and just use your program to map it?
If I do, which of the above options is the most appropriate to select?You can use either system just fine, you just can’t use them both at the same time, if that makes sense.
If you are using my custom “Global Mode”, this is essentially the same is the native PTT Mode in VA anyway, simply without the benefit of my own voice command based set/edit/delete system with its ability to set up to 6 total push-to-talk keys, joystick buttons, and/or mouse buttons.
The reason I designed my own system was two-fold: to allow multiple PTT keys/buttons with a simple and easy voice command & user choice input UI, and an alternate mode that allows only restricting the BMS radio (menu) keypress commands and not ALL commands throughout VoiceAttack. That latter function is an option for those who also use VA for various things, even setting/resetting TrackIR or controlling recording software, etc. during multiplayer flight.
It makes sense in BMS to transmit our actual voice radio request to multiplayers on the same radio channel that we’d be using to send a keypress based macro to issue that corresponding radio command in our radio menu so they don’t merely hear that radio AI just talking out of nowhere, and hear proper and appropriate radio traffic. But we don’t need them to hear us tell TrackIR to Pause or hear us ask our VoiceAttack “What time is it?”, so my “DEFAULT” mode fills this niche.
The native PTT system in VoiceAttack can’t exactly do all this stuff, and that’s why mine exists.
The following video demonstrates my PTT system as I talk about it in greater detail, if it helps:
-
@SemlerPDX
That helps a lot and makes sense, thanks! I will give this a try! -
@SemlerPDX
So I finally figure out how to make the mic on my Quest 3 work… note that I had no issues with the Reverb G2 mic or the Pimax Crystal mic. Trying out some of my common commands, I am getting 95% or more misses on the voice commands.Do I need to re-train voice recognition using the Quest 3 mic? Or is it just a shitty mic to begin with and might as well use my headset (Arctis Pro) mic?
-
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX
Do I need to re-train voice recognition using the Quest 3 mic? Or is it just a shitty mic to begin with and might as well use my headset (Arctis Pro) mic?I am uncertain about the quality of the Quest 3 mic, however, voice recognition speech training is specific to both the voice of the person who trained it, and the microphone they used to train it (hopefully at least three times, completely through the entire session).
If either of these things change significantly, you need to create a new speech profile, and then go through the training session again (at least three times). Since you are using a new microphone, you’d want to create a new speech profile. If you flip-flop between this microphone and another when using VoiceAttack for different games (perhaps some not in VR), then you’d need to switch between your original speech profile and this new speech profiles created for the Quest 3 VR Mic.
As you can see in the linked post below, we can delete existing speech profiles, and create new ones, or set which speech profile is active - follow these steps to create your new speech profile for Quest 3 and train it up:
https://forum.voiceattack.com/smf/index.php?topic=64.0