I want to check the behavior of loops in a simple preset. I know that you cannot engage/disengage loops with CC messages in advanced mode (I also know that a beta is in the works that allows this).
In simple mode, however, it seems that you can only engage/disengage loops with CC messages IF the loop is part of the current preset. For example, If I create a preset with with loop 1 the input/output tip path and loop 2 in the input/output ring path, then sending a CC message to toggle loop 4 will have no effect because loop 4 is not part of the preset. This is what I am encountering.
If I want the five loops to behave like a traditional pedalboard, then it seems I need to create a preset containing all five loops in their bypass state, then I can toggle them on and off with CC messages. Is this correct?
Thanks in advance.
You can’t engage/bypass loops not that aren’t connected to anything, because the engage/bypass behavior is basically turning on and off connections between loops. So if you have A → B → C and D and E are unattached, then toggling D and E doesn’t mean anything because where are they getting signal from, and where is it going?
Every preset should have all pedals you want in that signal chain connected. From there, you can engage/bypass the loops in the signal chain.
Thanks for the answer. I should clarify a bit. I have pedals connected to all ten loops. I have since created a preset that has all the pedals in both signal paths (tip/ring) but all bypassed in the preset. With that preset, which I named pedalboard, I can engage/disengage all pedals with CC messages.
The situation I mentioned in my original post also has pedals in all ten loops, but the preset I created only contains the pedals in loops 1 and 2. Loop 4 has a pedal, but it is not in the preset. In this situation I can use CC messages to turn on loops 1 and 2 but loop 4 (even though it has a pedal) does not engage if I use a CC message to try and engage it.
This lead me to the conclusion that to use CC messages to engage/disengage loops in simple mode, the preset must contain an instance of that loop in one of the signal paths, tip or ring.
If this correct? It just changes the way I might approach creating presets.
Thanks again.
Yes, if you want to be able to control the engage/bypass state of a loop, you need to have it somewhere in the signal path. Well, you CAN set it as engaged or bypassed while disconnected, but it won’t do anything.
The way I think of each preset is that it’s the entire signal flow for that moment on my board. I’d only leave effects out of that signal chain if they absolutely were not going to be used unless I changed presets. Otherwise, I’d have them looped into a signal path.
Now, one thing to note is that there are two ways to think about the engaged/bypass state for each preset. Normally, each preset loads a default state. In this example, the chain goes input → A → B → C → output, but B is bypassed:
Every time you call this preset, it engages A and C and bypasses B. Once the preset loads, you can choose to engage/bypass them afterwards, but it loads into that default state.
UNLESS you set the “Loop Bypass Persist” setting in Controller Settings to ON. In that case, presets only rearrange your signal chain, but the engage/bypass state remains the same until you set them otherwise (on startup, they default to the engage/bypass state of the first loaded preset).
Great! Thanks for the detailed explanation. I basically do the same thing treating the entire signal flow for that moment on my board. However, the other options you discuss open up other possibilities.
Thanks again.
@jason.nguyen Thank you for the point about Loop Bypass Persist. I thought my device was faulty.
I couldn’t find any info about the Loop Bypass Persist in the online manual. I searched for ‘persist’ but it doesn’t appear in the document.
I think it was introduced in the 1.2beta, so hasn’t been added to the manual. Which firmware are you on?
Hi Jason,
I am running the 1.2beta (1.2.251124441) software on my ML10x
Gotcha. Yes, I guess it hasn’t made it into the official documentation yet since it’s technically only available in the beta, but I just added it here for future reference:
