I mean, the possibility to choose between Off/On or On/Off, so when I assign multiple devices to a single footswitch I can Activate a module and deactivate another one
You can already do this. Just assign both blocks to the same footswitch, and then save your preset with one block active and the other bypassed.
Sorry to revive an old thread, but this seems like a related question… What decides the LED behavior when I have multiple blocks assigned to the same footswitch (with some reversed)?
For example, if I set up a footswitch to turn ON blocks X and Y and turn OFF block Z in position 1, that footswitch then turns OFF blocks X and Y and turns ON block Z when I press it (position 2). The state of the footswitch LED as well as the tile on the screen (in Stomp/Gig mode) will toggle on and off as I press the footswitch. That is all great. The LED indicator, however, seems to be unpredictable. Sometimes the state of the LED (and tile) will follow block X, sometimes it follows block Y, sometimes it follows block Z. It may follow one block for a bit, then decide to follow another block later.
There is probably some pattern or relationship that I am missing. Is there a way to set (or at least know) which block will control the LED behavior when multiple blocks are assigned to the same footswitch?
I want to be able to look down at my QC and be confident I know what state it is in.
Again, sorry for reviving an old thread, but I think I’ve figured it out—and it’s frustrating.
After some testing, I think the state of the LED is simply decided by which block appears first in the signal chain. QC seems to treat that block being on or off as the lit or not lit state of the LED, and therefore the on or off state of the stomp in gig view.
Which is frustrating, because there doesn’t seem to be a way to change this. As an example, the situation I’m in right now is as follows:
I have three blocks in a row: X, Y, and Z. X is an “always on” light gain, while Y and Z are two heavier gain stages going into each other. I’d like to effectively group Y and Z so they turn on and off together (as I think of them as my “heavy” sound). But using them with X also on is too much gain, so I want to turn X off whenever Y and Z are on and vice versa. The way I make sense of this in my head is basically “heavy” or “not heavy”—and I’d like gig mode to have a slot that, when off, is in “not heavy” mode, and when on is in “heavy” mode. I’d probably label it something like, oh I dunno, “Heavy”.
Issue is, because X comes before Y and Z in the signal path, the on/off state of the slot only ever corresponds to X. So in the “on” state it’s “not heavy” and in “off”, it’s “heavy”. I suppose I could label the slot “Not Heavy” and let the double negative work itself out when I turn it off, but somehow I don’t think that’s going to lead to clarity during a gig.
If anyone has advice here, It’d be much appreciated. Or if anyone could corroborate what I’m seeing in terms of the first block in the signal chain being the one used for the LES state, that’d also be great.
Update: I’ve found a dumb workaround. I shouldn’t have to do this, but I’ve since it’s jungle law out here in terms of getting any responses, updates, or reactions to feature requests from devs and we have to help each other find dumb workarounds, here it is:
Use a dummy gain block or something similar first in your signal chain to force the QC to recognize it as the decider of the LED status. So in my example of blocks X, Y, and Z in a row where X decides the LED status but I want Y and Z to do that, I’d add a gain block set to 0dB (doing nothing) before X and also assign it to the same stomp as X, Y, and Z. Then I’d make sure the gain block was set to the same on/off state as Y and Z (so they all turn on and off together), et voila.
Thanks for sharing this! I’m traveling this week but will give it a try when I get back to my QC.