The SoundFlow Editor
You open the SoundFlow editor app by chosing Open SoundFlow from the icon menu or by pressing Ctrl+F1 if your current profile has enabled default triggers.
Here's a look at how the SoundFlow Editor app looks like on the Commands page.
The GUI is divided into a few sections.To the left you have the packages and commands section:
This section is like a folder/file hierarchy. You select the folders (packages) on the left, and the contents of that folder (the commands) is shown on the right. In this example we have selected the All Commands folder, so the right column will show us all available commands.If we select a different folder, the right view will only show us the commands in that package/folder. For instance, here are the commands in the Automation Modes package:
To the right of every command you can see the currently active triggers for that command.
To change the triggers for a command, you'll need to look at the Command Triggers section which is located in the top right quadrant of the GUI. This section shows the triggers for the command you have currently selected in the Commands section to the left.
If you want to assign a new trigger/shortcut to a command, click the New Trigger button:
If you want to change an existing trigger, hover over the trigger and you'll see the options to change the trigger:
These buttons are to edit, learn, disable, or delete the trigger, respectively.If the trigger is a built-in SoundFlow trigger, you can only disable that trigger. If you want to assign a different trigger, disable the default trigger and add your own.
The bottom right quadrant of the commands page is dedicated to display details about the command you have selected.If you have selected a built-in SoundFlow command it will display documentation about the command, like this:
If you have selected a custom command that is installed from a 3rd party or that you have locked, it will also display the documentation from that command, like this:
If you have selected a custom command that is unlocked, the Command Details section will show the source code of the custom command:
If you click the INFO tab instead of the SOURCE tab, you can edit information about the script. If you later publish/share the script or the package the script is a part of, this text is what will be displayed to the users who install your package.