Missing confirmation beep

[AtomicMysteryWeasel]

I recently got a new PC and had to reinstall VoiceAttack and Vaicom Pro from scratch.  Now that I've finally gotten everything reinstalled and reconfigured (geez what a chore!) the beep I normally got after addressing my intended outbound recipient is not occurring.  For instance if I call up "Chief: remove the wheel chocks." Or "Tower request startup", etc.  I get no beep after the slight pause in Chief or Tower.

 

That is to say in the past what I should hear sounds like this:

 

"Chief..." (brief pause) beep   "Remove the wheel chocks"

"Tower..."  (brief pause) beep "Request start up"

 

I'm no longer getting that beep , but I do get a beep at the end of my transmission. Which is really weird.  

I've tried this using Easy and Normal Comms, also with and without VSPX processing. Nothing changes.

 

Everything else seems to work OK, but man I really like that first (hey my intended recipient heard and is listening to my transmission) beep. 

 

Has anyone else seen this behavior?  What am I doing wrong? I've been over my settings a dozen times and all through the manual and this is driving me nuts.

[MAXsenna]

@AtomicMysteryWeasel
Hi!
1. Make sure "confirmation beeps" or whatever it is called its turned on in the control panel.
2. Have you turned on "REDIR" or something on the audio tab as well? Try setting "default" and "init".

The only times I had issues with this, was when Windows messed with output after my headset bugged out due to driver updates etc. (It shows two audio sources), and I had selected the non default output.
The VoiceAttack slider in the Windows volume control, also controls this.
I can post screen grabs later if needed.

Hope you solve it!
Cheers!

Sent from my MAR-LX1A using Tapatalk

[AtomicMysteryWeasel]

Hi Max,

Thanks for the suggestions.  I did try them.  I'm pretty sure the setting identified in the first picture attached is the setting you mean.  It's on.  Still no beep.  Still the same behavior.  Tower, Overlord, Marshall, Chief, JTAC, etc...doesn't matter who I address I get nothing.  Just dead silence until my transmission ends.  THEN I get a beep.  

It's so weird. I don't understand this.

[sthompson]

Sounds like you might have the "Hold AI Transmission" box checked on the MP page.

[AtomicMysteryWeasel]

Hi sthompson,

I appreciate the thought.  Unfortunately that is a negative, Ghost rider. 

[AtomicMysteryWeasel]

Here's some of my attempts over the past few minutes.  What's weird is it says it doesn't recognize these words it actually recognizes.  I mean...how do you understand you don't recognize the words "Washington" or "Tower" if you don't recognize the words Washington or Tower?

 

[MAXsenna]

Actually, it is "Use Audio Hints", but you have it checked already.
This is a tricky one.
I would try to turn "OPER" to "OFF" on the audio tab.
Then I would open the Windows volume control, turn DCS waaaaay down, and turn VoiceAttack all the way up. The sound level of the sounds are actually quite low.
I remember now that I have actually made DCS make them "un-hearable" (if that's a word ).
Oh! You can actually try without starting DCS, press the TXs and while you watch the VoiceAttack slider. If the sounds are playing, the volume meter should rise.

Sent from my MAR-LX1A using Tapatalk

[AtomicMysteryWeasel]

Hi Max,

OK so I tried the OPER switch.  No joy.

It's not that VA/Vaicom Pro aren't hearing me.  It seems as though they're not picking up on who I want to talk to.  Both Windows Speech and VA understand "Washington", "Tower", "Chief" et al all with a high 90% success rate. And both VA/Vaicom Pro know that I want to speak to "the nearest tower", or "nearest AWACs" etc.   But it seems as though specific destinations are not being recognized.

So it doesn't know "Marshall" or "Washington" or "Tower" I think it's just picking the nearest tower etc.  Which would explain also why it doesn't know what do with "Chief" or "Sarge".

Do you suppose this is a lua issue?

[AtomicMysteryWeasel]

I just Master Zeroed the following settings.

Still no joy.

 

[MAXsenna]

@AtomicMysteryWeasel

Ahhhhhh! I missed your post, just above my last. But now I get it. "Unrecognised" is misleading in this context. 

"Washington", "Chief", "Tower" or "or flight" are not commands. That's why you don't get any confirmation beeps, and VA doesn't known what to do with a single word. Even though Microsoft Speech Recognition has interpreted the speech input perfectly, and translated it correctly to the appropriate text output. Though VAICOM (or VA) should tell you "missing input" or something. 

Try "Batumi inbound" or any other complete command. 

[AtomicMysteryWeasel]

 OK well...maybe I'm losing my mind? Setting all of this stuff up from scratch has been a real job.  Maybe I'm mistaken.  I'll try what you mentioned and let you know how I make out.

Thanks.

[RedeyeStorm]

10 hours ago, MAXsenna said:

@AtomicMysteryWeasel

Ahhhhhh! I missed your post, just above my last. But now I get it. "Unrecognised" is misleading in this context. 

"Washington", "Chief", "Tower" or "or flight" are not commands. That's why you don't get any confirmation beeps, and VA doesn't known what to do with a single word. Even though Microsoft Speech Recognition has interpreted the speech input perfectly, and translated it correctly to the appropriate text output. Though VAICOM (or VA) should tell you "missing input" or something. 

Try "Batumi inbound" or any other complete command. 

Not quit @MAXsenna. When I say ‘Chief’ and then pauze, I here a beep from vaicom that it recognized the intended recipient. Same with Overlord, Magic etc. @AtomicMysteryWeasel doesn’t hear that beep and he should. If I read it right then because vaicom doesn’t recognize the intended recipient it doesn’t carry out the command. If this correct then unfortunately I have no solution.

11 hours ago, AtomicMysteryWeasel said:

So it doesn't know "Marshall" or "Washington" or "Tower" I think it's just picking the nearest tower etc.  Which would explain also why it doesn't know what do with "Chief" or "Sarge".

This may be another problem all together. This sounds more like easy comms is on. In MP I have the issue I can only talk to the tower I took off from. I dial in the frequentie of another airfield but as soon as I talk the frequency jumpes back to the frequency of my take off airfield. No idea about that one either.

[MAXsenna]

3 hours ago, RedeyeStorm said:

Not quit @MAXsenna. When I say ‘Chief’ and then pauze, I here a beep from vaicom that it recognized the intended recipient. Same with Overlord, Magic etc. @AtomicMysteryWeasel doesn’t hear that beep and he should. If I read it right then because vaicom doesn’t recognize the intended recipient it doesn’t carry out the command. If this correct then unfortunately I have no solution.

Really? That's interesting, because mine doesn't, and beeps works for me. Can you post your VoiceAttack log when you say these commands?
Anyway. If you look at his log, you can see the words are recognized fine actually, but "chief" is not a complete command, and it is VoiceAttack that doesn't know what to do with it.
OP can make a standard VA command with "chief", and then it VA will know ehat to do with it.

BTW. For complete pendantism, neither VAICOM nor VoiceAttack does any recognition. VoiceAttack passes the text it gets from MS to VAICOM only IF it matches any of the VAICOM commands. If it doesn't, it is rejected. That's what you see in his log. Have a look at mine. I have not started DCS while doing this. Do not worry about the red lines. It's because I'm not in DCS and in a  the correct module for my hardware.

Pay special attention to the line "go for". I actually say "gopher" like in the line after. When I say "Gopher, close group formation" I get the correct beeps. Orange line.

 

3 hours ago, RedeyeStorm said:

This may be another problem all together. This sounds more like easy comms is on. In MP I have the issue I can only talk to the tower I took off from. I dial in the frequentie of another airfield but as soon as I talk the frequency jumpes back to the frequency of my take off airfield. No idea about that one either.

VAICOM won't know unless you're in a mission. That's why I recommend testing with DCS not started.

Cheers!

Edited May 1, 2022 by MAXsenna
Grammar

[AtomicMysteryWeasel]

6 hours ago, RedeyeStorm said:

Not quit @MAXsenna. When I say ‘Chief’ and then pauze, I here a beep from vaicom that it recognized the intended recipient. Same with Overlord, Magic etc. @AtomicMysteryWeasel doesn’t hear that beep and he should. If I read it right then because vaicom doesn’t recognize the intended recipient it doesn’t carry out the command. If this correct then unfortunately I have no solution.

This may be another problem all together. This sounds more like easy comms is on. In MP I have the issue I can only talk to the tower I took off from. I dial in the frequentie of another airfield but as soon as I talk the frequency jumpes back to the frequency of my take off airfield. No idea about that one either.

"Not quit @MAXsenna. When I say ‘Chief’ and then pauze, I here a beep from vaicom that it recognized the intended recipient. Same with Overlord, Magic etc. @AtomicMysteryWeasel doesn’t hear that beep and he should. If I read it right then because vaicom doesn’t recognize the intended recipient it doesn’t carry out the command. If this correct then unfortunately I have no solution."

Yes, this is indeed what is going on.  

"So it doesn't know "Marshall" or "Washington" or "Tower" I think it's just picking the nearest tower etc.  Which would explain also why it doesn't know what do with "Chief" or "Sarge"."

This is my own supposition, and I could very easily be wrong - but this seems to be why it's doing what it's doing.

Yes, I am using  Easy Communications.  I never play multiplayer.  I'm just not that good yet, and it's just less hassle.

2 hours ago, MAXsenna said:

Really? That's interesting, because mine doesn't, and beeps works for me. Can you post your VoiceAttack log when you say these commands?
Anyway. If you look at his log, you can see the words are recognized fine actually, but "chief" is not a complete command, and it is VoiceAttack that doesn't know what to do with it.
OP can make a standard VA command with "chief", and then it VA will know ehat to do with it.

BTW. For complete pendantism, neither VAICOM nor VoiceAttack does any recognition. VoiceAttack passes the text it gets from MS to VAICOM only IF it matches any of the VAICOM commands. If it doesn't, it is rejected. That's what you see in his log. Have a look at mine. I have not started DCS while doing this. Do not worry about the red lines. It's because I'm not in DCS and in a  the correct module for my hardware.

Pay special attention to the line "go for". I actually say "gopher" like in the line after. When I say "Gopher, close group formation" I get the correct beeps. Orange line.

 

VAICOM won't know unless you're in a mission. That's why I recommend testing with DCS not started.

Cheers!

 

OK Max,

So are you saying maybe I need to keyword train VA/VP? 

[MAXsenna]

53 minutes ago, AtomicMysteryWeasel said:

OK Max,
So are you saying maybe I need to keyword train VA/VP? 

To the contrary, your recognition is fine. That's what I wrote.
It understands "Washington" to the letter. And by "it" I mean MS Speech.

VAICOM uses VA as a gateway to MS Speech. That's how this works. VA gets the speech-to-text from the MS Speech Recognition Engine.
And I repeat "Washington" is not a command by itself. That's why VA or VAICOM doesn't understand what to do with it. "Washington select" is a command.

 
@RedeyeStorm Has a point, so before I forget TURN OFF easy comms. It's bad, and is negative learning. ED should remove it, but I guess FC3 sort of needs it.
Re-read from the top. Are you expecting to say "Washington" - beep - "Inbound" - beep -?
I'm not saying you're wrong, but I've never heard that. But I seem to remember you got a confirmation beep and a reminder of the command was missing more input.
I repeat again. Do not start DCS, and try "Batumi, inbound", or Washington for that matter.
Try "Chief, remove the wheel chocks".
I'll admit that I use VSPX, so I can talk really fast and don't really need any micro pauses. But again. Recognition is not the issue. In the VA log you posted you can see it

EDIT: I just noticed something. You are using TX4. Do you know why? 
 

I post this again. As you can see the words are perfectly recognized, but they can't be used to anything, because the lack context. The command is not recognized, because it doesn't exit. Except "Gopher". By itself, MS Speech thinks the chances are better that I say "go for", but put in context with the whole command "Gopher close group formation" makes more sense, because it actually exists as a command and "go for close group formation" does not. Understand what I'm trying to say here?
So please try some full commands with DCS off.

Edited May 1, 2022 by MAXsenna

[AtomicMysteryWeasel]

10 minutes ago, MAXsenna said:

To the contrary, your recognition is fine. That's what I wrote. It understands "Washington" to the letter. And by "it" I mean MS Speech.
VAICOM uses VA as a gateway to MS Speech. That's how this works. VA gets the speech-to-text from the MS Speech Recognition Engine.
And I repeat "Washington" is not a command by itself. That's why VA or VAICOM doesn't understand what to do with it. "Washington select" is a command.
And before I forget TURN OFF easy comms. It's bad, and is negative learning. ED should remove it, but I guess FC3 sort of needs it.
Re-read from the top. Are you expecting to say "Washington" - beep - "Inbound" - beep -?
I'm not saying you're wrong, but I've never heard that. But I seem to remember you got a confirmation beep and a reminder of the command was missing more input.
I repeat again. Do not start DCS, and try "Batumi, inbound", or Washington for that matter.
Try "Chief, remove the wheel chucks".
I'll admit that I use VSPX, so i can talk really fast and don't really need any micro pauses. But again. Recognition is not the issue. In the VA log you posted you can see it

Sent from my MAR-LX1A using Tapatalk
 

OK well it is possible I'm remember how this worked incorrectly.  There was quite a bit of time between the death of the old PC and my new box getting here. 

I'll try what you're suggesting as far as not starting DCS and see what happens.

I'll also try going without Easy Comms - that sounds kind of daunting, but I'll try it.

--Thank you.

[MAXsenna]

OK well it is possible I'm remember how this worked incorrectly.  There was quite a bit of time between the death of the old PC and my new box getting here. 
I'll try what you're suggesting as far as not starting DCS and see what happens.
I'll also try going without Easy Comms - that sounds kind of daunting, but I'll try it.
--Thank you.

Haha! Yeah, but that's the fantastic part of VAICOM! It will teach you radios, and can even tune most of them for you!
That's, why I want you to try some commands offline, because then the setting in DCS won't matter
BTW, TX4 with Easy Comms makes totally sense!

Sent from my MAR-LX1A using Tapatalk

[AtomicMysteryWeasel]

Ok so if I just breeze through the command quickly without any pausing:  "ChiefRemoveTheWheelChocks." "JTAC,Playtime15Minutes." etc.  It looks like everything is working fine - outside of DCS.  Maybe it's just me and I'm an idiot.  I know that VPSX commands are supposed to be given in an expeditated manner, but I could have sworn I used to get a beep after addressing my recipient ("Chief," beep "...remove the wheel chocks."beep.  ; "JTAC", beep "...playtime 15 minutes. beep. ") but maybe I'm wrong.

I'll fire up the hornet after Sunday lunch and try this out again.  I'll let you know how I make out.

The hard part is going to to be unEasy Comms and  trying to figure out where to map three additional TX buttons.

 

[RedeyeStorm]

@MAXsenna I do not get everything you said but the misunderstanding might lay in the VSPX. I do not use it so I need to pauze and wait for the beep. That would also explain @AtomicMysteryWeaselconfusion. If he has VSPX activated there would be no beep now but VSPX is relatively new and it may not have been there last time he used VAICOM.

[MAXsenna]

@MAXsenna I do not get everything you said but the misunderstanding might lay in the VSPX. I do not use it so I need to pauze and wait for the beep. That would also explain @AtomicMysteryWeaselconfusion. If he has VSPX activated there would be no beep now but VSPX is relatively new and it may not have been there last time he used VAICOM.

Aha! That's a fair point. I have been using VSPX for about two years I think. So, if it works that way without it, I totally forgot. I will never switch back though. For me it works so much better.
Only downside is that you can't say "recipient 1-1 colt 1-1 command" etc. for some of it. Works for tankers though. Very cool.

Hmmm... I was so sure it was because the command was not complete.
@AtomicMysteryWeasel Have you done the "Finish" step? Because I stand by that the recognition works perfectly, but VoiceAttack have noe clue what to do with it. But if you haven't done the "Finish" step in the Keywords Editor in the Control Panel, it actually makes perfect sense. Because then the command is actually missing from VoiceAttack.
Could you please check if the commands are missing from VA? Or just do the step anyway, just to make sure?


Sent from my MAR-LX1A using Tapatalk

[AtomicMysteryWeasel]

5 hours ago, MAXsenna said:

 

 

Aha! That's a fair point. I have been using VSPX for about two years I think. So, if it works that way without it, I totally forgot. I will never switch back though. For me it works so much better.
Only downside is that you can't say "recipient 1-1 colt 1-1 command" etc. for some of it. Works for tankers though. Very cool.

Hmmm... I was so sure it was because the command was not complete.
@AtomicMysteryWeasel Have you done the "Finish" step? Because I stand by that the recognition works perfectly, but VoiceAttack have noe clue what to do with it. But if you haven't done the "Finish" step in the Keywords Editor in the Control Panel, it actually makes perfect sense. Because then the command is actually missing from VoiceAttack.
Could you please check if the commands are missing from VA? Or just do the step anyway, just to make sure?


Sent from my MAR-LX1A using Tapatalk
 

 

Yes I have done the finish step.

OK so...with the Easy Comms and VPSX on...as long as I speak quickly it seems to work as normal. No beeps when I initially address my recipient, but it works pretty darned well.  I over flew several air fields and called out to Washington or Marshall and had no issues contacting them.  Also my VA seems to load up with a lot more dialogs when it first starts up. Unless I've hit some verbose switch I was previously unaware of a ton of F10 selections are loading on startup and that never happened before.  Before on the old PC that is. 

I'm beginning to think my old setup was bent, just bent in a way I liked and got used to, but may be this is how VA is supposed to work?  I'm not sure.  I need to go through the Vaicom Pro manual and learn some of the more nuanced commands.  I always had issues on the new machine giving wingman more than just the most basic commands.  All this F10 load out at start business makes me wonder if maybe the old machine wasn't loading up the way it should?  That would explain beeps where they shouldn't be. 

I really appreciate you guys trying to help me.  I need to poke around on this some more, but I feel like I'm headed in the right direction with it.  I don't get the chance to play DCS much through the week.  I've normally had enough of computers by the time I get off work, but I'll keep you guys posted how I make out as I work through this.

Thank you all again.

[sthompson]

38 minutes ago, AtomicMysteryWeasel said:

Also my VA seems to load up with a lot more dialogs when it first starts up. Unless I've hit some verbose switch I was previously unaware of a ton of F10 selections are loading on startup and that never happened before.  Before on the old PC that is.  ... 

All this F10 load out at start business makes me wonder if maybe the old machine wasn't loading up the way it should?

Most likely you did not have "Import F10 Menu" checked on the old machine. You do have it checked as seen in your screen shots. And if you have that checked then every F10 menu item in every mission you fly is going to get saved by VAICOM in its database. It's not smart to leave it turned on in my view. I'm not aware of any way to delete them from the database except by resetting it.

[MAXsenna]

Most likely you did not have "Import F10 Menu" checked on the old machine. You do have it checked as seen in your screen shots. And if you have that checked then every F10 menu item in every mission you fly is going to get saved by VAICOM in its database. It's not smart to leave it turned on in my view. I'm not aware of any way to delete them from the database except by resetting it.

I agree with this @AtomicMysteryWeasel
Turn it off or your DB will be full.
Du delete the commands, you can simply do it one by one with the preceding "action" in the Keywords Editor.
I turn it on for missions I know I will be using more than once, especially in MP.
I then make an alias so I don't have to say "action" and easily can find it again, because it retains the "action".

I'm really happy we sort of got s working solution for you.
Thanks to all that have chimed in!

Cheers!


Sent from my MAR-LX1A using Tapatalk

[melchionda]

On 4/30/2022 at 10:28 AM, AtomicMysteryWeasel said:

I recently got a new PC and had to reinstall VoiceAttack and Vaicom Pro from scratch.  Now that I've finally gotten everything reinstalled and reconfigured (geez what a chore!) the beep I normally got after addressing my intended outbound recipient is not occurring.  For instance if I call up "Chief: remove the wheel chocks." Or "Tower request startup", etc.  I get no beep after the slight pause in Chief or Tower.

 

That is to say in the past what I should hear sounds like this:

 

"Chief..." (brief pause) beep   "Remove the wheel chocks"

"Tower..."  (brief pause) beep "Request start up"

 

I'm no longer getting that beep , but I do get a beep at the end of my transmission. Which is really weird.  

I've tried this using Easy and Normal Comms, also with and without VSPX processing. Nothing changes.

 

Everything else seems to work OK, but man I really like that first (hey my intended recipient heard and is listening to my transmission) beep. 

 

Has anyone else seen this behavior?  What am I doing wrong? I've been over my settings a dozen times and all through the manual and this is driving me nuts.

I had the same issue and the way that I fixed it was that I needed to go to the Audio Tab in Viacom Pro and click the Init button.  It actually doesnt really look like a button and I dont know what it does but it does fix the problem.  The only problem with the solution is that I need to click the Init button every time I start up Viacom Pro.  (That didnt used to happen).

 

[AtomicMysteryWeasel]

I haven't tried that yet, Mel.  But I will and I'll let you know. 

Thanks!