DeeJay's Voice Activaded Commands (VAC) Profiles
-
Like I said, it was not working for a “WHILE”, it’s fine now.;)
Thanks,
RAM22
-
DeeJay,
Thank you for sharing this. Do you use custom key strokes for these commands?
I’ve downloaded both files and installed (what a pain in Windows 7 as you have to disable UAC and reboot before it will install correctly) but in the VAC Builder the Character Key(s) are different from what I’d expect.
For example the key stroke assiged to ‘Tower Inbound’ I would expect to be ‘t1’ but it shows ‘t&’. All the other commands are different also. Is this by design, or did my download get corrupted?
I can’t actually try it out yet, which is why I’m asking, as when I click on VAC On I get a pop up telling me my 30 day evaluation period is over, even though I’ve only just installed it {sigh}. It sure isn’t as slick a process as BMS was to get working
-
Thank you for sharing this. Do you use custom key strokes for these commands?
Oh shit ! Maybe french keyboard issue!
Maybe you will have to change that!? … did not expected that! … sorry
As soon as I have the time, I will check … maybe correct it if I can…!(?)
If you want to do it yourself, (if you don’t want to wait…) … here is corresponding keys:
French keyboard is AZERTY
& = 1
é = 2
" = 3
’ = 4
( = 5- = 6
è = 7
_ = 8
ç = 9
à = 0
- = 6
-
Thanx but what is the advantage of this compared to shoot? As I see it both use ms speech recognition. Also this tool has to be installed (shoot doesn’t).
Can I put a guide for this to bmswiki please? -
Thanx but what is the advantage of this compared to shoot? As I see it both use ms speech recognition. Also this tool has to be installed (shoot doesn’t).
Can I put a guide for this to bmswiki please?Can’t tell you … never used Shoot! I’ve heard that VAC is better working… (?)
-
Oh shit ! Maybe french keyboard issue!
Maybe you will have to change that!? … did not expected that! … sorry
As soon as I have the time, I will check … maybe correct it if I can…!(?)
If you want to do it yourself, (if you don’t want to wait…) … here is corresponding keys:
French keyboard is AZERTY
& = 1
é = 2
" = 3
’ = 4
( = 5- = 6
è = 7
_ = 8
ç = 9
à = 0
Merde!
That’s it. Oh well, it’s not a problem I can’t fix. I just need to change the characters to numbers.
Thanks for the quick response.
- = 6
-
This post is deleted! -
-
He DJ,
Good initiative mate!! Missed it completely however Certainly will give it a try!
But ehh…. regarding ‘instructions’:
1 - I talk to my wife (ok I admit, she’s the one giving the orders)
2 - then I could talk to my car (which doesn’t listen very well either)
3 - now I can talk to BMS (finally!! Now I’m the one giving orders )keep it up, good work here!
Regards,
Fan -
Can’t tell you … never used Shoot! I’ve heard that VAC is better working… (?)
I gave it a try and noticed that VAC requires the PTT button to be held for the keyboard command to be issued. It’s not necessary to hold PTT while issuing the voice command (VAC listens continuously). Shoot! requires the PTT to be held while issuing the voice command, but will issue the keyboard command whether the PTT is still held or not. The latter is a bit more suitable for BMS IMHO. It’s unnatural having to hold the PTT after you gave a voice command. On the other hand, I just recently installed Shoot! on Windows 7 (I’ve used it intensively on Win XP in the past), and I noticed that it sometimes takes a long time for Shoot! to react to a command. On Win XP that was never a problem. Not sure yet what’s causing it.
-
I gave it a try and noticed that VAC requires the PTT button to be held for the keyboard command to be issued. It’s not necessary to hold PTT while issuing the voice command (VAC listens continuously)
It is customisable … you chose what you prefer.
I’ve chosen to use PTT for two reasons…
1st - IRL, when I talk to my wingmen, I have to use my radio PTT … Why not doing the same in BMS?
2nd - I’m using ICV (or TS3) during PM (using also another PTT) … I don’t want to activate an unexpected commands when talking to other humans.
-
Sorry, I didn’t make myself clear:
In VAC, with PTT defined, you can issue the voice command without activating the PTT, as long as you activate the PTT when VAC wants to issue the keyboard command. That means it’s listening without PTT held, and you need to hold PTT a bit longer for the keyboard command to be issued reliably.
In Shoot!, again with PTT defined, Shoot! only listens when you hold the PTT. When it wants to issue a keyboard command, it will do so, whether PTT is held at that moment or not. No need to hold PTT a bit longer.
I find Shoot!'s method more natural for use in BMS. VAC on the other hand is more powerful, as you can switch profiles and run programs by issuing voice commands.
-
English version for those sans ordinateurs:
-
Sorry, I didn’t make myself clear:
In VAC, with PTT defined, you can issue the voice command without activating the PTT, as long as you activate the PTT when VAC wants to issue the keyboard command. That means it’s listening without PTT held, and you need to hold PTT a bit longer for the keyboard command to be issued reliably.
Have you tried using Arm mode? Quote from help file > Getting Started > Profile Activation Keys:
Arm mode - pressing the assigned keys will arm the switch for the recognized commands to be sent, after recognition the switch will auto-disarm.
If I understand your post correctly that should give the same result as you get in Shoot!
-
and you need to hold PTT a bit longer for the keyboard command to be issued reliably.
Okay … yep you’re right!
-
Now I haven’t tried it yet in Falcon as I still can’t get the damned program to work when I reenable UAC (it tells me my 30 day trial period has ended and I sure as hell am not shelling out $18 until I’ve seen it working) but in Notepad, Wordpad and any other program I’ve tried it in using Arm mode you do not need to hold the PTT key down.
Just press the PTT key once briefly, say your command, see the result. If you want it to recognise another command just rinse and repeat.
-
On the other hand, I just recently installed Shoot! on Windows 7 (I’ve used it intensively on Win XP in the past), and I noticed that it sometimes takes a long time for Shoot! to react to a command. On Win XP that was never a problem. Not sure yet what’s causing it.
You need more speech training.
Also in general have in mind IVC - TS3 and Shoot or VAC and ptt on Cougar. Combining all together will be a mess. For me shoot always on (I don’t fly MP) normal use IVC shifted use TS3. So the dilemma is obvious.
One solution is:
short ppt = VAC or shoot
hold ptt = IVC
shift hold ptt = TS3Optimal would be another shift mode.
-
short ppt = VAC or shoot
hold ptt = IVCThat’s a good idea!
…
Me using:
HOTAS UHF = IVC UHF & TS3 “Whisper to Chanel family” simulating the strike freq (AWACS + other package members or to be used as a broadcast freq)
HOTAS VHF = ICV VHF & TS3 PTT & VAC PTTNote that when using IVC & TS3 at the same time (TS3 as backup) … I have a key (SHF + BACKSPACE) to toggle “microphone muted” under TS3
Also a key (CTL + END) to enable/disable VAC -
One solution is:
short ppt = VAC or shoot
hold ptt = IVC
shift hold ptt = TS3My stickfile issues bith IVC and Shoot! PTT commands simultaneously, but I built in a function to enable/disable Shoot! functionality. The idea is to have my flight members hear my Shoot! commands via IVC. Of course, you run the risk of Shoot! misinterpreting non-Shoot! commands issued to the human players. Therefore the switch, so I can disable Shoot! in-game.
If you use a short button command to issue Shoot! commands, you’re speaking to Shoot! while the COMM switch is in neutral (or have I misunderstood your solution?). You could then also just have Shoot! always listening while COMM is in neutral. That would only run the risk of Shoot! misinterpreting your coffee order to your wife
-
Since IFF is not implemented yet, why not use a shifted PTT on either T5(IFF out) or T4(IFF in) on the cougar for VAC or Shoot, that way T2(VHF) & T3(UHF) can be used for IVC and teamspeak.
The reason I say shifted is because you may need the comms left(T5) and right(T4) to get your package to show correctly on the Data link