FoxVox Free voice control software for BMS
-
<p>@rfxcasey friend if I counted correctly you were the 3rd person to suggest the other voice recognition program on this thread, so you had 2 posts and 5 upvotes to them (hardly a mob to lynch you), that informed you that this is the developers post and it was not cool to do that. After that you had 6 posts from @SemlerPDX , @foxster plus a funny post from @Aragorn (good one hahaha), that simply said "its ok man, you have parked on a no parking zone, you did not see the sign, its cool, just move your car please ", and your responses were more on the side of being offended by that. So as everyone else said<strong> it’s ok, no harm done you did not see the “No Parking” sign, just move your car please! </strong>I actually believe you are a good Samaritan that just tried to help, I also think that you misunderstood @SemlerPDX ‘s first message. I believe he was referring to that bad review of foxvox on another site, but on his quote he also had @foxster ‘s response about you, so maybe you thought he was referring to you also, but I don’t believe that is the case.<br /><br />Anyway let’s move on to debugging, shall we ;-)<br />@foxster I believe I found a bug. I have 2 similar phrases “Ground” --> “Request Taxi” and “Ground” --> “Request Taxi Back”, as you can see from the below pic, Foxvox hypothesizes both phrases from what I say and correctly chooses the “Ground” --> “Request Taxi Back” as the one to execute, which is the one I actually pronounce, but then executes the wrong one “Ground” --> “Request Taxi”, as you can see from the notepad on the right corner of the pic. Also please notice the time difference from last hypothesized phrase up until execution, it is 26’’, I don’t know why it is that long, but that happens an any command I give today. I will restart my pc and get back to you on that, maybe it is unrelated to FoxVox.<br />If you need any more info let me know. I am now in the process of recording all voice commands from the BMSVACInstallationGuide.pdf to your program, and I thoroughly test each one before proceeding.<br /><img class=“ql-image” src=“https://i.imgur.com/LRqklOW.jpg” /> <br /><br /><br /></p>
-
<p>@foxster Another one the spoken phrase is “Ground Recharge J F S”, it is not on any hypothesized phrase but it is correct on the recognized phrase, but then it tries to execute “Ground Recharge Taxi FS” that does not exist.<br /><img class=“ql-image” src=“https://i.imgur.com/dCjzc1E.jpg” /><br /><br /></p>
-
<p>@danaos75 First, I have found that a long delay would sometimes occur when my microphone was picking up white-noise from my computer fan which was just enough to keep the speech recognition engaged. I was able to combat this by setting the recognition timeout setting to 1 or 2 seconds (although I’m using it at zero again after lowering my mic sensitivity).<br /><br /><img class=“ql-image” src=“https://i.imgur.com/PrbvS3A.png” /><br /><br />As for the Request Taxi, it is possible that a phrase will match 2 commands because extra words in the phrase are allowed and ignored. Make sure you have a blocking key setup for the word ‘Back’ on the Taxi for Departure command. Here’s how I do it:<br /><br /><img class=“ql-image” src=“https://i.imgur.com/QTX9PfC.png” /><br /><br />This allows me to say ‘Request Taxi’, ‘Request Taxi for Departure’, ‘Request Taxi to Runway’, ‘Request Taxi Back’, ‘Request Taxi to Ramp’, or ‘Request Taxi Back to Ramp’ and all will work as I expect.<br /><br /><img class=“ql-image” src=“https://i.imgur.com/npCMeca.png” /><br /><br />Now for your question on Recharge JFS, could you show me the voice key setup on that? As you’ve noticed, there’s actually a lot more going on under the hood than what is just reported in the enhanced logs. It would actually be a mess if I tried to display it all to the user so I stuck with the primary recognition chain only to help troubleshoot - which helps a lot but obviously isn’t everything. In the case of the Recharge JFS, here’s how I set it up. Notice for myself I put ‘JFS’ on both keys so it would more easily recognize it, but I also included ‘Recharge’ as a key word and I included ‘Jet Fuel’ as an alternative as phonetically ‘JFS’ can be a little challenging to recognize.<br /></p>
-
<p>@foxster as per your instruction I now have 13 commands (only 200 more to go <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f627.png?v=1g16vn91q2r” alt=“” class=“not-responsive emoji emoji-android emoji–anguished” /> ) that work flawlessly (blocking keys did the work on “Taxi” and “Taxi Back”)! Thank you!</p>
-
<p>@danaos75 OK, I have found the underlying issue with the Recharge J F S. There is an issue with the spaces introduced by a fix I did to strip out non-alphanumeric characters. This would also affect multi-word commands which is why my library wasn’t having the issue. I’m including the fix with an update I will be posting soon - at most a couple of hours which will also include the confidence level integration and a toggle to enable/disable enhanced recognition. Don’t worry, it won’t undermine any of the work you’ve done so far and I think you’ll find it will fix your reported problem <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f600.png?v=1g16vn91q2r” alt=“” class=“not-responsive emoji emoji-android emoji–grinning” /> </p>
-
<p>@foxster thank you for the fast response, but as you can see from the below pic it works just great now. I have the JFS without spaces in between and very similar to what you have on your pic above<br />and it works! I say Ground JFS or Ground Recharge or Ground Recharge JFS and it works 10/10! But I am glad that I helped locate a bug <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f41b.png?v=1g16vn91q2r” alt=“” class=“not-responsive emoji emoji-android emoji–bug” /> . I am using 2 word commands so far just to see how it goes, and I can elaborate later. My goal is to use comms without touching the keyboard at this time, I am not trying to sound like a real human pilot.<br /><br /><img class=“ql-image” src=“https://i.imgur.com/nfrTMnp.jpg” /><br /> <br /></p>
-
<p>@danaos75 Glad to hear it’s working for you. I just posted the update for you here: <a href=“https://foxster.itch.io/foxvox/devlog/354532/foxvox-update-v152” target=“_blank”>https://foxster.itch.io/foxvox/devlog/354532/foxvox-update-v152</a>. It fixes a few underlying things I needed to get to in the recognition as well as introducing the features I mentioned and fixing the bug with spaces. If you want to sound more like a real pilot later, give this one a go and see how much you can deviate and still hit the correct keys. I’ve found that you need to keep phrases with spelling (QFE, QNH, JFS, etc.) short as they don’t work well with a bunch of extraneous words (due to the inherent nature of the voice recognition) but other phrases handle it pretty well. As always, just let me know if anything needs to be fixed - it’s getting there as it gets more runtime and user feedback. I’ll be around if you run into any breaking issues. Thanks!<br /></p>
-
<p>@foxster I now have a complete working 213 voice commands for FoxVox. I used your latest update 1.5.2. I can confirm that only one command is giving me trouble (that !@# GO VIC), so I might change that to GO VICTORY, but since it is a formation command for an obsolete formation I don’t think I will bother. I now get almost 100% recognition of my commands and the best part is that I don’t have any miscommands (executing a command other than the one I spoke). They are all very simple, mostly one word, commands. If anyone wants the file as a base for his\her setting up foxvox I will gladly give it to him. Thank you for a great app!<br /><br />P.S.1 I have one suggestion, if possible to export the commands on some file format (.xml?) to be easier to bulk change the structure and copy paste commands and then import it back. <br />P.S.2 The initial list of commands where extracted from the BMS_VAC_(QWERTY).xml that is located on Falcon bms docs folder. That helped a lot to have a ready, copy paste list, and to have every command possible available, so big thanks to whoever made that file <img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f44f.png?v=1g16vn91q2r” alt=“” class=“not-responsive emoji emoji-android emoji–clap” /> </p>
-
<p>@danaos75 I’m glad it’s all working. You make a good suggestion about the open file structure. Rather than xml I went with compressed Json though. I could easily add in the ability to save a library uncompressed so that it would be easy (well easier) to do any external editing. Also, if it would help anyone out I could create a repository alongside FoxVox to share user-made libraries.<br /><br />Now that you’ve got your base library some things to keep in mind:</p><ul><li>You can extend phrases and still have great recognition by adding assisting phrases and dictionary entries…you don’t need to be limited to 2 word phrases</li><li>You can change to a new library easily by voice command (I swap between libraries configured differently for multiplayer vs single player)</li><li>You can open PDF or other files during pre-flight or flight using voice commands (I have one to launch BMS, OpenTrack, & Joy2Key on startup so all I launch is FoxVox)</li><li>You can use alias creation during pre-flight (or on the fly) to add in callsigns onto commands (For example airport name instead of “Tower”. Names can be challenging so I add them to the global dictionary (i.e. “Kimpo”) for better recognition. Even if they are misspelled when added, as long as you say it the same way, they work).</li></ul><p><br />A lot of these features aren’t usually necessary but they’re great to have when needed and are there to enhance the experience. As always, let me know if you have any more suggestions and thanks for the feedback!</p>
-
-
-
Is there any way to map the POV of the Warthog Throttle up and down (index finger) as the PTT switch? Looks like it is not handled as a button.
-
@Le_Beau currently no…the POV isn’t tracked like a regular button but it is something I can add in with a future update. I was planning to anyway, just hadn’t gotten around to it. I’ll add it to the queue along with some other new enhancements I’m working on.
-
@foxster Thank you very much.
With 4.36 out i‘m currently rethinking all my settings. One change would be to move the comm-switch to the pov, which would be closer to the original. Currently it is on my thumb button.
-
@Le_Beau Understood. One of the new features coming just to keep in consideration is the addition of multi-configuration support within a single library. This will allow you to enable/disable command groups and commands by configuration. That way you can use a single library for different scenarios - i.e. with wingman commands disabled for multiplayer and enabled for single player…things like that (or even more creative scenarios ). Naturally you’ll be able to switch between configurations using outputs from voice commands.
-
@foxster you make dreams come true! You are thinking big!
-
An update on the next release, I’m just about finished with the new features, including supporting the Hat switches for PTT functionality and multi-configuration support so v1.6 will be out soon - this weekend-ish maybe? Lets say a couple of days (I know, here everything is a couple of weeks, but honestly - this really just isn’t as complicated).
For the future I’m still contemplating adding in full joystick mapping so that FoxVox will be an all-in-one voice and joystick mapping app so I don’t need to combine it with Joy2Key or Joystick Gremlin. Granted these are both fine and functional software that I use currently, but neither one quite hits the perfect suite spot for me, and I’d really like to have a single app to configure and manage all the inputs. Being the crazy fool to write this app, I may just do it, but in the spirit of upgrades with 4.36 rolling out, I also wanted to ask if anyone would like to see any other improvements beyond this - any suggestions or criticisms you’d like to see addressed (within reason or you risk a derisive witticism from @Aragorn - btw love the sense of humor ) ?
Thanks everyone, best regards and happy flights!
-
thanks for the preview mate! I’d love to see a new BMS library integrating the new voice commands for 4.36 if that’s not asking too much
All the best,
Uwe
-
Version 1.6 is now out. Here’s a video detailing a few of the new features. Also, view the changelog here for a complete list and an important note regarding the POV/Hat input for PTT:
https://foxster.itch.io/foxvox/devlog/378235/foxvox-update-v160
@hoover I’m still working on the new commands for 4.36 video and library update as requested, but coming soon!
-
@foxster love your app! I use it every day with zero problems. I haven’t got around to add the new commands of 4.36 yet, but I will soon. I have only 2-3 word commands like GROUND TAXI, but I can speak the full sentence like “whiskey 2-1 GROUND request TAXI to takeoff runway” and it works like a charm! Thank you for a great app and for supporting it! Will the old commands file be compatible with the new version?
-
@danaos75 Yep, absolutely! Still the same at its core. Glad to hear it’s working well for you
-
Guess its finally time to switch from DWVAC :).
When the time comes, where can I find the library for BMS .36?