Open Source Voice Macro
-
in the Spirit of BMS Open Source (sort of) aspec, I stumbled on a free Voice Command software… i haven’t built a profile as of yet but maybe of interest to someone https://voicemacro.net/
-
That’s pretty interesting! I make profiles for the VoiceAttack program, though it is paid software, as opposed to donationware like this voicemacro thing. Also, BMS includes profiles for VAC (Voice Activated Commands), but again VAC is not free, either.
I’m gonna check this out when I have time. Thanks for the heads up! Looks cool -
I have been testing it and was pleasantly surprised, it has recognized 98% of calls in English (not my language), and 99% of calls in my language.
I give it a 9 out of 10
-
That software looks really good. Keep us posted on how your testing goes
-
I’m a newbie to BMS but decided to give it a go, since I once did this for a submarine sim and it worked great. I’d like to set it up for the ATC Menu but it doesn’t seem to accept mapping multiple keystrokes to a single voice command, eg. “unrestricted approach” -> “t t t t 4”. Anyone tried it successfully?
Thanks
-
yes with easy success …see pic
-
I can’t seem to access your attachment, it says invalid link if I open it (in Firefox) in this tab or another tab.
-
not sure server thing… but multiple keystroke can be done eg awacs vector to home plate … Keyboard Q then ok keyboard Q then ok keyboard 6 then ok …job done …also clone button is your friend …
-
Here’s my profile that I use.
Download: http://www.mediafire.com/file/0bgkzxa0l6nwxhe/BMS.xml/file
Make sure to change the PTT buttons. I had to use a slight workaround to implement push-to-talk. Assign your PTT button to the “Ignore commands stop” action. Then assign the same button to the “Ignore commands start” action, but make sure to choose “Execute on Button: up”. That way when you let go of the button, it starts ignoring your commands again. You can use a regular “always on” if that’s more to your liking.
For the actual voice commands: I tried to use callsigns where it made sense, but also keep it simple for better detection. They are enclosed in square brackets ([Chalice 1; Sentry 1]). Click on the actions to see under the Voice Command entry what you have to say to trigger it. I tried to stick to the text that’s displayed in the comms box.
AWACS listens to the usual AWACS callsigns. Example: Sentry 1 request picture, Chalice 1 request picture, etc.
Your wingman listens to “Callsign 2”. Example: Falcon 2 attack my target, Gamble 2 attack my target, etc.
Your element listens to “Callsign 3”. Example: Falcon 3 attack my target, Gamble 3 attack my target, etc.
Your whole flight just listens to the Callsign. Example Falcon attack my target, Gamble attack my target, etc.
ATC listens to the entity that the command is for. Example: Ground request taxi for departure, Tower ready for departure, Approach request vectors for visual approach, etc.. There are also the “global” commands like the one to request QNH. Those can be used with any entity: Tower request QNH, Approach request QNH, etc.
The tanker listens to Texaco and Copper. Example: Texaco 1 request air refueling.I have experimented with making more complex, but more immersive voice commands. For example adding your own callsign into it. It worked, but the longer the voice command the higher the chance that it doesn’t get recognized properly. That’s why I decided to stick to the “simple” ones as seen above. I find it still immersive enough and it’s a great thing compared to having to manually push it on the keyboard.
-
I’ve just tested that free software, after having read the thread, and it works surprisingly well : I get reliable results and the voice commands are pretty easy to create.
Thanks a lot for the tip, guys. -
That’s pretty interesting! I make profiles for the VoiceAttack program, though it is paid software, as opposed to donationware like this voicemacro thing. Also, BMS includes profiles for VAC (Voice Activated Commands), but again VAC is not free, either.
I’m gonna check this out when I have time. Thanks for the heads up! Looks coolNot only is it free, since it’s open source it could be forked and heavily modified to suit specific needs of Falcon environment.
-
Make sure to change the PTT buttons. I had to use a slight workaround to implement push-to-talk. Assign your PTT button to the “Ignore commands stop” action. Then assign the same button to the “Ignore commands start” action, but make sure to choose “Execute on Button: up”. That way when you let go of the button, it starts ignoring your commands again. You can use a regular “always on” if that’s more to your liking.
This is how most VA profiles do it, wouldn’t call it workaround but “industry standard” at this point
-
This is how most VA profiles do it, wouldn’t call it workaround but “industry standard” at this point
I could assign just a simple button in most other software without the need for the comparatively complicated way mentioned above. I don’t mind it and use it, but it’s silly to claim an “industry standard” for something as simple as assigning a hotkey.
Not only is it free, since it’s open source it could be forked and heavily modified to suit specific needs of Falcon environment.
I don’t think it counts as free software. On the “Download” page it mentions a license, but it doesn’t appear to be licensed under one of the common free software licenses. I also can’t find a link to the source.
-
I don’t think it counts as free software. On the “Download” page it mentions a license, but it doesn’t appear to be licensed under one of the common free software licenses. I also can’t find a link to the source.
lol - by that definition, my AVCS4 BMS Radios (for VoiceAttack) is not ‘free’… but then again, I do attach a CC by-nc-nd or by-nc-sa license to most all of my own work, still though - that’s a pretty liberal definition of terms. But this voice macro software is specifically donationware, and like my AVCS4 BMS Radios, free to use without limitations but encouraging support for the likely hundreds or thousands of hours of work put into it, not to mention continued user support.