AVCS4 Immersive Voice Control Radios for VoiceAttack
-
Hi Semler, here is an other post about PTT. Sorry for That
0.92b Core and v1.3.92b AVCS4BMS installed, PTT Buttons Assigned in AVCS4 BMS (UHF and VHF press and release). Initialization okW10, VAv1.8.7.12 x32 in administrator mode, Listening ON, PTT mode ON.
When I first try to say a command, recognition is green, and nothing write in the test text file. Nice, it works as expected.
UHF ON, Declare, q2 on text file, cool …
UHF OFF (release), declare again, and … q2 again… WTF… try with VHF ON ,Declare , q2 … Hummmm:?
I try with other commands and AVCS reacts as if PTT mode is OFF.I shut down VA, relauch it, try an other command, then same behaviour.
I think I do something wrong.
I read at least 3 times all the 14 pages and can’t find what is wrong.Maybe some idea, help ?
-
Another big thumbs-up from Austria (QWERTZ, German Language and “3,14”).
Your workaround works like a charm
Thank you for your awesome efforts - I’m happy to use 1.3.92b again.Thank you for the report - patch has been released, simple config update so everyone will get it next time they load AVCS4 BMS - no need to download or import a new profile version or anything. Will copy my reply here:
Okay - now I can see exactly what the issue is, and it makes sense, too. It seems that I did not add in the specific keypress variable for that command, where it was formerly (incorrect) “Check My Six”, and I added the correct phrasing to that for “Clear My Six” but not it’s keypress counterpart (7)
I’ve patched this up, and pushed it out for all users. Just follow the prompt next time you restart VoiceAttack and load AVCS, and it will apply.
I will get the next full profile update released before too long, including the fix for handling international decimal separators, and other fixes/improvements. As always, I really appreciate everyone’s patience and support through these beta test rounds… I know they are long, and I’m a bit of a perfectionist, but I’m just one guy and it’s a passion project.
-
Hi Semler, here is an other post about PTT. Sorry for That
0.92b Core and v1.3.92b AVCS4BMS installed, PTT Buttons Assigned in AVCS4 BMS (UHF and VHF press and release). Initialization okW10, VAv1.8.7.12 x32 in administrator mode, Listening ON, PTT mode ON.
When I first try to say a command, recognition is green, and nothing write in the test text file. Nice, it works as expected.
UHF ON, Declare, q2 on text file, cool …
UHF OFF (release), declare again, and … q2 again… WTF… try with VHF ON ,Declare , q2 … Hummmm:?
I try with other commands and AVCS reacts as if PTT mode is OFF.I shut down VA, relauch it, try an other command, then same behaviour.
I think I do something wrong.
I read at least 3 times all the 14 pages and can’t find what is wrong.Maybe some idea, help ?
Be sure you have set both a “PRESS” as well as a “RELEASE” for each of the buttons. That behavior would happen if you had not set the “RELEASE” commands to the same button(s) respectively. What they do is return a boolean variable to ‘false’ in this current version, so since they have not been set to a key to fire each time it is released, this bool never goes back to ‘false’, and PTT mode is basically overridden and essentially ‘off’. Get those set and you’re good to go!
I feel for ya, don’t worry, this is all on voice command in the next version, hopefully coming as early as next weekend (or sooner). You’ll all no longer have to ‘manually’ edit dummy commands just to assign your desired Push to Talk keys (or Release to Talk hehe) – this new voice controlled PTT key/button assignment system is great, just a little more testing and polish, and it’s ready for prime time. The next release may be the end of the beta rounds, with more improvements coming in time such as the teased themed GUI’s, and others.
-
Thanks for the answer Semler, but yes the log screen is very clear : both UHF and VHF are pressed, then released …
For sure I do something wrong but can’t find what … -
Thank you for the report - patch has been released, simple config update so everyone will get it next time they load AVCS4 BMS - no need to download or import a new profile version or anything. Will copy my reply here:
“Clear my six” is running fine now.
Your auto-update-thing ROCKS -
Are you talking about voice control here?
Works very well VoxCommando.
Here is an example of commands, though in Russian.
Do not look at piloting. This is an example of voice control. -
Thanks for the answer Semler, but yes the log screen is very clear : both UHF and VHF are pressed, then released …
For sure I do something wrong but can’t find what …At the end of the initialization of AVCS Core, I have this
BMS Data Load Complete - Voice Attack is now loading profile
Inline function execution exception: Exception has been thrown by the target of an invocation. Index was outside the bounds of the arrayCould it be in relation with my issue ?
-
Wingedsky, maybe I found out something (maybe not, but let’s try).
Press the key, say the command… but then WAIT until the command is recognized before releasing.
The “moment of recognition” must fall inbetween of “press” and “release”, I guess.
Just leave your thumb on the button for a second longer. -
At the end of the initialization of AVCS Core, I have this
BMS Data Load Complete - Voice Attack is now loading profile
Inline function execution exception: Exception has been thrown by the target of an invocation. Index was outside the bounds of the arrayCould it be in relation with my issue ?
This could be an issue in addition to the PTT issue you are having. Again, if you are from a region that expresses Pi as “3,14” as opposed to “3.14” then two decimal variables will be messed up. These are part of the timing of the PTT keypress loops, so would effect those and foul them up. A hotfix is located in a previous reply here (reply to Judy), and I will have it all fixed as soon as I get this next version released.
Just need a bit more time to work on it. Thanks for your patience!
-
thanks Amadeus75 and Semler
Semler your suggestion doesn’t change any thing after I edited the profile as shown.
But it appear that the way suggested by Amadeus change something. I have to find the good timing for release and this way let the recognition log between the press and release log. Nice
When it works, I noticed something strange :
when I say a VHF command without PTT, I have
“9:22:36.933 AVCS4 Command Recognized, but PTT Mode is on and PTT Key Down not detected…
9:19:47.042 Recognized : ‘two say fuel’ (derived command) (Confidence 97)”Which seems normal and nothing send to the file
But For a UHF command, even if recognition ok and nothing send to the text file, the warning about PTT does’nt appear
Is it the normal Behaviour?
Edit : When the release key seems not to have been detected, I noticed that i need to do a press, then wait 1 or 2s (i don’t know exactly how long) without saying anything, then release. and it seems that the PTT is re initialize with always the same behavior as describe in this post (Ptt warning not detected only for VHF):shock:
-
I now have to keep the PTT key pressed for a second or two after speaking for the command to be recognised. I found that if I keep the key held until it’s recognised, that is the most consistent way for commands to register.
I thought it was because of JanJan’s plugin, but not sure - are there too many commands and is it parsing the best profile to use?
(and there was a minor update)
-
I now have to keep the PTT key pressed for a second or two after speaking for the command to be recognised. I found that if I keep the key held until it’s recognised, that is the most consistent way for commands to register…
That’s how it works for me, too. I have sometimes wondered if this is normal, or if that 1-2 second delay is supposed to be shorter. I’d be curious to find out.
-
I’m trying to figure out how AVCS4 BMS for VA works. I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup. Core and AVCS4 BMS initialize ok. Alternative All-Humans Mode is OFF, Audio Feedback is On, Default keyboard QWERTY, UHF/VHF PTT mode is ON. I didn’t touch anything else in CORE/AVCS4 BMS profiles. Now I enter 3D and fly around Kunsan, I set UHF to 292.650 Kunsan’s ARR Approach frequency, push and hold my UHF button (UHF is highlighted) and request different approaches starting with: APPROACH Request (any) or APPROACH Declare Emergency…. Nothing happens. I check VAC recognizes commands Ok(green). What am I missing?
Do I need to add key strokes in the profile perhaps (not sure but I don’t think so)?Thanks.
-
What am I missing?
Give it a try, and keep your finger on the button just a little longer after you spoke the command.
I think it could be a timing issue with “UHF/VHF PTT mode”.Make sure you hear that audio recognition signal, BEFORE you release the PTT key.
Otherwise the command may be recognized, but not within the correct “PTT time”.
The correct log should read: “Press -> recognized -> release”
Otherwise it may read “Press -> release -> recognized”… in this case, the recognizing comes too late for PTT mode.I could be wrong, but just give it a try.
(PS: Oh, and be careful: “VAC” is not “VA” ;))
-
I assume you’ve assigned your hotas buttons for ptt? I made the error of assigning hotas buttons AND keyboard keys (the profile explicitly says don’t do that, in a round about way).
Sent from my Phone 2 using Tapatalk
-
Deleted.
-
Can I check if the profile sends any keystrokes at all without launching BMS? I’m still not sure how this profile works. I’ve tried others much more simple ones they work by sending series of tttt or 12345 etc to BMS. )) I know I’m missing here something very basic in understanding of how it works I think.
-
Yes you can without runing BMS
Just open a text file and make it active, ready to enter letters (the cursor must flash) . Say you command, and if recognize, you should see the letters and numbers write without anything else. -
I’m trying to figure out how AVCS4 BMS for VA works. I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup. Core and AVCS4 BMS initialize ok. Alternative All-Humans Mode is OFF, Audio Feedback is On, Default keyboard QWERTY, UHF/VHF PTT mode is ON. I didn’t touch anything else in CORE/AVCS4 BMS profiles. Now I enter 3D and fly around Kunsan, I set UHF to 292.650 Kunsan’s ARR Approach frequency, push and hold my UHF button (UHF is highlighted) and request different approaches starting with: APPROACH Request (any) or APPROACH Declare Emergency…. Nothing happens. I check VAC recognizes commands Ok(green). What am I missing?
Do I need to add key strokes in the profile perhaps (not sure but I don’t think so)?Thanks.
Try turning PTT mode off. See if it all works well. PTT Mode (optional) is merely a helper to prevent recognizing commands during normal speech, but in reality, I rarely find AVCS4 BMS firing off commands when I am just talking to someone and not issuing commands to VoiceAttack.
You don’t need to add anything to the profile to work, but please do understand these profiles are a public beta test, and while so many things function exactly as designed, there are a number of minor issues and quirks that are still being worked out, as well as major systems like PTT Mode which are getting replaced/improved for the next version (ETA is right out the window, lost a week due to a blizzard here in Portland; spotty internet and occasional blackouts make work not worth the effort until this passes).
I have many ideas and many working proof of concepts for so many of the issues you all have reported, and I really appreciate the feedback! There’s only so much I can test myself, I have a modern gaming PC and a 2015 laptop and that’s it - not to mention human factors I could never test for. All these post really help - I’ll keep you all posted and reply when I have made some progress.
Cheers!
Amazdeus75 is correct that when PTT mode is on and set up correctly for a Push and a Release command, releasing this button too fast on a slower computer can cause the command to assume the PTT button is not held. This is also something I am working on improving, possibly using a key listener instead of the current method which sets a boolean variable to ‘true’ when a PTT key/button is depressed, and back to ‘false’ when released.
-
Amazdeus75 is correct that when PTT mode is on and set up correctly for a Push and a Release command, releasing this button too fast on a slower computer can cause the command to assume the PTT button is not held. This is also something I am working on improving, possibly using a key listener instead of the current method which sets a boolean variable to ‘true’ when a PTT key/button is depressed, and back to ‘false’ when released.
Yes, they mentioned that in this thread, I held PTT UHV/VHF buttons much longer but to no avail.
I’ll try vanila CORE/AVCS4 BMS profiles with a notepad first and see if that works.
Thanks!