FoxVox Free voice control software for BMS
-
@Vikingo11 Just posted a new update for you. Sorry you’ve been the guinea pig, but I’m glad you reported the bugs. It seems to be a case of older code being affected by the new updates but not manifested during testing. Unfortunately I have been unable to officially reproduce your error even knowing what most likely caused it, but I believe I have fixed it. I also found another bug with the PTT variable auto-mapping to BMS not detecting controllers correctly after a computer restart which I was unaware of. This has been fixed also, so I recommend this update for everyone. Let me know if it’s working now
.
-
@Nightflyer said in FoxVox Free voice control software for BMS:
Is there a way to use the new Windows Voice recognition System
I spent some time trying to implement the MS Speech Platform 11 into FoxVox. Actually it was surprisingly easy to hook everything up, but unfortunately it just isn’t compatible in runtime with the .net core architecture. It relies on the full .net framework (older 2.0 at that) and I just couldn’t manhandle the code into a clean workable solution. Who knows, perhaps MS will one day port those libraries to the .net core, but I wouldn’t hold my breath waiting. I was a bit surprised when they updated the system speech libraries though, so it could possibly happen…
-
@foxster thank you for the suggestion.
I finally worked out my problem - the sound file I was trying to use for PTT Active was MikeClick.ogg from the Falcon BMS 4.37 sound directory where all sound files seem to be .ogg format.
Once I converted the .ogg file to .wav format it worked fine, problem solved. -
@foxster Thank, I love your software so happy to be the guinea pig. I have installed v2.6.2.0 and opened up the shared library v4. However, the PPT variable is not auto-mapping to BMS. Do I need to manually map UHF/VHF buttons to the various groups? In the README-file it says “1. Set PTT binding to UHF/VHF channels”. I remember that it was automatic in an earlier version of FoxVox, and I recall that one had to put some parameters into the plugin FoxVoxParser.
-
@foxster I figured out how to connect the plugin FoxVoxParse, switch it on, insert the path to the BMS - Auto.key in the parameters. The PPT-buttons was detected automatically, but when I press any of the PPT-buttons the program crashes. Please find the log files below
Index was out of range. Must be non-negative and less than the size of the collection. (Parameter ‘index’)
*Inner Exception: Empty
at System.Linq.Enumerable.WhereListIterator`1.ToList()
at HOIbpDbbE4qNrERg5dP.e1XnYfb2yiAZgHUWgvS.vvpbpZcORK(srWNSuIl1UgYT9YEMIE input)
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallback.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()*Index was out of range. Must be non-negative and less than the size of the collection. (Parameter ‘index’)
*Inner Exception: Empty
at System.Collections.Generic.List
1.RemoveAt(Int32 index) at HOIbpDbbE4qNrERg5dP.e1XnYfb2yiAZgHUWgvS.<>c__DisplayClass80_0.T7Y6riMDYu(cbFI9AIwrJ2RDrXvyvd m) at System.Collections.Generic.List
1.ForEach(Action`1 action)
at HOIbpDbbE4qNrERg5dP.e1XnYfb2yiAZgHUWgvS.vvpbpZcORK(srWNSuIl1UgYT9YEMIE input)
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallback.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()* -
@Vikingo11 Seems like the ‘fix’ didn’t quite work…Looking into it.
-
Update to v2.6.3 is posted as a hotfix to address the PTT issue.
https://foxster.itch.io/foxvox/devlog/730866/foxvox-update-v263
-
@Nightflyer I was finally able to get the WSP 11 working in FoxVox after a bit of effort figuring out the faulting Microsoft.Speech.dll assembly. It will be available soon in the next update. This will bring a lot of new languages into FoxVox in addition to the alternative engine.
-
Hi,
I have this error about the joystick (for crew chief interaction)Every other devices are correctly detected (winwing rudder, virpil throttle).
The stick is a VPForce Rhino FFB base + virpil alpha grip, and it is connected and correctly working in BMS. -
Update to version 2.7 is now out. There are some very nice new features in this update along with fixes from the v2.6.x series. A few things worth mentioning:
- Added support for MS Speech Platform 11 recognition.
- Added new output type for direct 1-to-1 keybinding.
- Added full support for vJoy devices, including Pov Hat switches and analog outputs.
- Changed mouse cursor move output for more compatibility (works now with BMS).
-
@Virus I just released version 2.7. Please update and let me know if you still have the issue. It could be an issue with syncing between the FoxVox Parser plugin and BMS, or it may be fixed with the update. If after the update it still doesn’t see the device, I’ll address it with you. Thanks!
-
There was a new problem in the release v2.7 with keystrokes not being recognized in BMS anymore due to a new feature introduced to support legacy keypresses that inadvertently set a flag to indicate Unicode Scan Codes. I did not realize that was included in the latest release, so hotfix v2.7.1 is now available. There was also an issue with vJoy button labels being shifted by 1 which is now corrected.
-
@foxster I installed v2.7.1 and connected the plugins and my BMS - Auto.key but the push-to-talk buttons is not automatically recognised by my Thrustmaster Viper TQS. Any suggestion for a fix?
-
@Vikingo11 I’m not sure if something has changed in the BMS key file or not with the update. Are you running the latest BMS v4.37.4? Others seem to have reported this same issue so I’m looking into it. In the meantime, you can clear the PTT and set it directly. I do want to find out why the auto-binding isn’t working any more so I’ll keep investigating…just need a weekend with a couple of free hours.
-
@foxster yes, I have upgraded to v4.37.4. I thought the culprit was my new Thrustmaster Viper TQS. I look forward to hear from your investigation and in the meantime I will set the PTT manually. Cheers!
-
@Vikingo11 When you have a moment, I need three things from you to troubleshoot.
First, from within FoxVox, click the plugin to view the parsed BMS variables and do a search for SimTransmitCom1. Right click it to copy the value and paste it here for me.
Second, click on any PTT setting to bring up the PTT input window and click your UHF button to display it. Capture a screenshot of the button description as shown in the window like in the example pic below. You can cancel the window afterwards - no need to actually set the PTT.
Third, copy the name of the controller as found in the DeviceSorting.txt file located in you BMS user config directory. It should have an ID number followed by the device name. I’d like to see if the product name of your controller is consistent between FoxVox and BMS or not.
Thanks!
-
@foxster I got it to work! I removed the shared library Falcon BMS 4.37.3 v4, and reinstalled it. That solved the issue. The auto connection works like a charm now.
For your reference, I attach the screenshots.
-
@foxster said in FoxVox Free voice control software for BMS:
@Virus I just released version 2.7. Please update and let me know if you still have the issue. It could be an issue with syncing between the FoxVox Parser plugin and BMS, or it may be fixed with the update. If after the update it still doesn’t see the device, I’ll address it with you. Thanks!
Copy, I’ll try and let you know.
Is the profile still the same? -
@Virus I just posted a new library update for the new BMS 4.37.4 update. The new library file is available here along with information about changes, setup, etc.
https://foxster.itch.io/foxvox-libraries/devlog/745960/foxvox-falcon-bms-libary-v4374-v1-update
-
@foxster I installed the latest library, and everything works well except for the fact that I cannot access MS Speech 11. See the screenshot below. Speech Recognition is activated on my PC.