I did this and the only way I could find, was to make 56 or so different macros. I will try and use it tomorrow or later today to actually show the synth settings as I am turning the CC controlling dials of the synth itself, and the midi controller which I use to control it.This MIDI use, using a file, seems like a possibility. I made a screenshot, I will look into it and see if I can get anywhere with this. I will look into script writing for the possibility. Probably a better option than making ~49 different 'or' midi equals 'n' options in the Macro or 50 different macros probably as the or wouldn't call a different result would it. So it would actually need that many different macros. Script would be only option then.
I found at least 3 bugs in the Advanced Scene Switcher as I was doing this, mostly related to updating the Macros as I was duplicating them. As they are duplicated, they continue to reference the first in a line of duplicates, rather than updating to reference the most recent macro duplicated. This caused problems if I would look back at the duplicated macros before closing the window and reopening it. Looking back at duplicated macros caused the values in them to revert to the original duplicated macro, and get saved wrong.
A second bug I revisited several times as I made 56 or so macros, was if I made a 2nd macro with the same name as another (I was changing only the number of the macros, to match the sent CC value per macro). If I mistakenly made a 2nd 104, it would freeze the Automatic Scene Switcher window irretrievably. At first I thought all OBS was frozen, but using Ctrl-Q to close the window (a hotkey in my case has this) twice, makes it close without closing OBS.
I was having some problems with the MIDI fields marked 'ANY' in the first screenshot in your post (warmuptill), they can't seem to be changed to get only the CC without its changing value. I tried a number of ways to get the CC isolated, because in the 2nd macro that assigns a text output per variable, the changing of each dial passes several values that can cause the * field below the if a variable section to be activated thus calling up several different texts in succession by accident because a dial with cc of 73 will pass all the values between 0-127, and that activates all the other CC variable text to be written to the file.
I couldn't get the CC alone, so I had to use the * that allows 'partial' matches to activate the macro.
Last edited: