Triggering Profiles .... Triggering Folders, Groups!

Hi @Reuven_Amiel,

Currently there is now way AFAIK to assign Tiggers to switching the SoundFlow Profiles.

You may be able to achieve the workflow you are after by using a globalState variable to control how the midi trigger scripts respond.

Is there any chance you could make it to the SoundFlow hangout this Wednesday (https://soundflow.org/hangout)? It would be much easier for me to walk you through how to do this in the Zoom session. :-)

@Reuven_Amiel

Actually here is a way to demonstrate how to do it...

Say that you wanted to have midi notes react differently when in three different modes.

In its simplest form you would set it up as follows;

---

• Create three scripts to set the individual modes.
• Name them "Mode 1", "Mode2", "Mode 3".
• Add the following script to the "Mode 1" Script;

globalState.myMidiTriggerMode = "mode1";

• Add the following script to the "Mode 2" Script;

globalState.myMidiTriggerMode = "mode2";

• Add the following script to the "Mode 3" Script;

globalState.myMidiTriggerMode = "mode3";

• Create a new Deck and name it "Mode Switching Deck"
• Add the three Mode commands to a deck;

___

• Create a new script and name it "Middle C".
• Assign a MIDI trigger to the script.
• Add the following code to the script;

function actionOne() {
    log("You are in Mode 1, run Action 1");
}

function actionTwo() {
    log("You are in Mode 2, run Action 2");
}

function actionThree() {
    log("You are in Mode 3, run Action 3");
}

function defaultAction() {
    log("No valid mode found, run the default action");
}

function main() {
    let currentMode = globalState.myMidiTriggerMode;

    switch (currentMode) {
        case "mode1":
            actionOne()
            break
        case "mode2":
            actionTwo()
            break
        case "mode3":
            actionThree()
            break
        default:
            defaultAction()
            break
    }
}

main();

Global State variables allow you to store variables that can be used in more than one script, so by using the Mode buttons on the deck to switch modes, you can then trigger the "Middle C" script via your midi controller and the script will react differently depending on what mode you are in.

You can then add the code you want to run in the associated action functions.

If no mode is set the defaultAction function will run.

Let me know if that makes sense. :-)

Thanks for your help Kitch, will check this out!