Recent Posts

51

General Discussion / Re: Multiple callsign simple smart solution

« Last post by SemlerPDX on March 25, 2025, 01:06:13 PM »

SemplerPDX,
Your example is what I’m trying to achieve.
For some reason when testing it doesn’t work for me.
I can't get VA with the same lines you typed to recognize the callsign.
Weird.

I would assume that you are not respecting the proper logical flow of this concept:  First VA needs to load your profile, then it needs to load some command from within that profile (set to execute anytime this profile is loaded) containing key variables used by the profile (such as the callsigns variable) so it "knows" what this variable means.... then, it needs to "reset the active profile" as an action within that command.  This will reload all commands in that profile (including those with a variable in the "when I say" portion), thus populating that command with all the callsigns it just read.



It is a multi-step process to use variable command phrases, and so long as you follow the above steps, your profile will work with variable command phrases loaded from text variables.  There are other ways, of course, even plugins to accomplish this, but this is the general "easy" way.

52

How Do I? / Re: Open the audio Bible by voice via VoiceAttack

« Last post by EricM on March 24, 2025, 10:49:04 PM »

I am interested in implementing this for you.

I need to understand the file tree better to solve for corner cases, e.g. Is it "firstJohn", "1st-John", "1_john", etc.

If you could share the audio files or where you got them, that would work.

If that isn't possible or if they cost money: You can get the whole file tree by running the following command in command prompt (without the quotes) "cd = \bible && tree /f"

Alternatively (if this doesn't work out), I googled "bible pc voice controlled for the blind" and google served this electronic Bible Audio player for kids and the blind
https://www.ebay.com/itm/256468428287

53

General Discussion / Re: Multiple callsign simple smart solution

« Last post by Polaris on March 24, 2025, 03:39:20 PM »

Gary,
Flight sim multiple commands with callsigns spread evenly through the commands.
Copy regarding CMD.

SemplerPDX,
Your example is what I’m trying to achieve.
For some reason when testing it doesn’t work for me.
I can't get VA with the same lines you typed to recognize the callsign.
Weird.

54

General Discussion / Re: Multiple callsign simple smart solution

« Last post by SemlerPDX on March 24, 2025, 01:48:43 PM »

Issue:
Profile has many commands containing a callsign in different locations in the command.
That callsign changes very often.
Current solution: export> edit by search and replace note editor > import.

Trying to implement the following with no luck:
1. Change each callsign occurrence to the following: “{CMD:mycallsign} “
2. Add the following command to profile and to  options>profile exec>execute command when profile is loaded:
“ Set Text [mycallsign] to 'Viper' “

Would appreciate help.

I would allow users to say any callsign, even if it is the incorrect one.  Should not punish voice commands for speaking the incorrect item:  allow them to role play as they want, but do not require a same-same callsign to be a rigid requirement to issue any voice commands.

Create a text variable containing all callsigns, delimited by semicolons ";" and then use that dynamically in any command phrases instead of hard-coded callsigns - for example:

Code: [Select]

Set text [Callsigns] to 'Amber;Angel;Argos;Avenger;Banshee;Barrel;Bat;Beast;Bison;Blackhawk;Blackjack'

...then in the "When I say" section of your commands:

Code: [Select]

[{TXT:Callsigns}] Do a Barrel Roll
...the example above would allow for a command phrase of "Amber Do a Barrel Roll" (or any such callsigns present in the Callsigns text variable -- just note that anytime this variable changes, the active profile would need to be reloaded for these new callsigns to be available as command phrases).

55

General Discussion / Re: Multiple callsign simple smart solution

« Last post by Gary on March 24, 2025, 01:21:53 PM »

What exactly is it that you are trying to do?

{CMD:mycallsign} is not something that exists.  The {CMD} token renders the name of the executing command (there is no parameter).

56

General Discussion / Multiple callsign simple smart solution

« Last post by Polaris on March 24, 2025, 12:59:34 PM »

Issue:
Profile has many commands containing a callsign in different locations in the command.
That callsign changes very often.
Current solution: export> edit by search and replace note editor > import.

Trying to implement the following with no luck:
1. Change each callsign occurrence to the following: “{CMD:mycallsign} “
2. Add the following command to profile and to  options>profile exec>execute command when profile is loaded:
“ Set Text [mycallsign] to 'Viper' “

Would appreciate help.

57

Profile and Command Discussions / Re: Start/Stop WSR listening when switching VA profiles

« Last post by Pfeil on March 22, 2025, 03:41:12 PM »

A command can be assigned to the profile-level "Execute a command each time this profile is loaded" option, which can in turn contain the relevant actions.

58

Profile and Command Discussions / Re: Start/Stop WSR listening when switching VA profiles

« Last post by Dsotm44 on March 22, 2025, 07:31:42 AM »

Many thanks for the quick reply!

I am using Win10 so the small overlay is still there. You are correct that the window cannot be targeted. Annoying but if I get a solution working I will update here

Many thanks

Edit**
Follow up question - can action be set up that executes on auto-switching to a different profile without the need for a voice command to trigger the action?

59

Profile and Command Discussions / Re: Start/Stop WSR listening when switching VA profiles

« Last post by Pfeil on March 22, 2025, 07:05:14 AM »

Are you using Windows 11? If so, that application will no longer be available after you upgrade to 24H2 or later.

Aside from that, there may not be any "normal" methods like keyboard shortcuts available to toggle listening, as given that the WSR application is more aimed towards an assistive context almost everything is intended to be done through voice recognition.

It's also not a normal window, and as such can't really be targeted. Though, as the WSR GUI is normally always drawn over other windows (this would require not having it minimized), you could try using a mouse click on the orb button to toggle the listening state.

60

Profile and Command Discussions / Start/Stop WSR listening when switching VA profiles

« Last post by Dsotm44 on March 22, 2025, 06:05:47 AM »

Hi new to VA - read everything I could but could not find a solution to this.

Have set up multiple app profiles which switch automatically with window focus which is great. However one of the profiles is my desktop where I need to use MS WSR for a lot of stuff. Is there a way to set up a command in an app profile to also "start/stop listening" in MS WSR when going to and from the Desktop profile? (without resorting to external scripts or Text to speech)

Many thanks