I’m not sure if this is a feature request or if this is possible, but is there any world where an engaged ML10X loop could be attached to a Toggle Group so that whenever the Loop is engaged your button would light up?
I am programming a live show and creating presets for each song with certain loops engaged and disengaged. Each loop is a Pedal. So I would like to be able to engage a preset where Loop A (Overdrive 1) is engaged and then when I go to a separate page where all of my pedals are listed, I would see that Loop A (Overdrive 1) is engaged and highlighted.
Is this already possible? It seems that being able to attach ML10X loops to Toggle Groups would allow this.
Thanks!
Hi. Are you using a Morningstar MIDI controller? As you correctly pointed out, you can add all the switches you have programmed to control Loop A, to the same Toggle Group. That way all these switches will be in sync across the different banks.
I’m using an MC6 PRO and ML10X’s.
So, that’s not exactly the issue I’m running into. I am able to successfully sync my pedals via Toggle Groups. I am trying to do this…
Create a Preset that engages several loops at once (via “Set Loops” on the ML10X) and one of those loops is A-tip (Overdrive 1)… when I go to a page that shows my pedals, Overdrive 1 is not “lit up” because I didn’t use a preset to engage it in the first place.
I hope that makes sense.
@james it would be awesome if you could assign ML10X loops to Toggle Groups or at least have a way to visually access whether they are on or off on the MC6 Pro.
I have also been looking for a way to “Engage Preset” for a dummy preset that is only triggering a second Toggle Group. (I have an instance where I need Loop Groups AND Loop Reset Groups.) PS. I could also use more of these groups! I’m running out! 
)
If you stay within the same bank you could simply add a ‘set toggle’ message to your preset which mirrors the ‘set loop’ message.
If you want to set the toggles on a different bank it might be feasable to programm a set toggle message to that bank and trigger it via ‘engage preset’.
I get a big confused about Set Toggle. Could you give me some more insight into what you just suggested?
Sure,
in the ancient days of the MC we didn’t have toggle groups, we had to use ‘set toggle’ messages. 
Toggle groups were implemented to streamline certain use cases of set toggle messages.
While it is more complicated to set them up ‘set toggle’ messages do offer more flexibility.
A ‘set toggle’ message does what it says. It will set the position of a preset or multiple presets without sending any messages. That’s exactly what you need I think.
If you have individual presets for each loop of your ml10x but want to use a ‘set loop’ message to load something like a ‘scene’ that has specific set of loops engaged and you want to have the state of said loops reflected by your individual presets you’d just have to add a ‘set toggle’ message to your ‘set loop’ preset that ‘engages’ the presets which are associated with the loops engaged.
1 Like
Something I like to do is to have a “Stompbox” or “Pedalboard View” bank which lets me engage/bypass all my pedals. If I’m using an ML10X, this means I engage/bypass the ML10X loop (and just leave the pedal itself engaged). All loop engage/bypass commands call presets on this bank instead of directly commanding the ML10X, which means there’s a “home base” for the status of the loops.
The presets for this bank each look something like this (Togle Mode = off):
- Press (Pos:1) - Engage Loop
- Press (Pos:2) - Bypass Loop
- Press (Both) - Toggle
- Long Double Tap (Pos:Both) - Engage Loop
- Long Double Tap (Pos:1) - Toggle
- Long Double Tap Release (Pos:Both) - Bypass Loop
- Long Double Tap Release (Pos:2) - Toggle
The first 2 commands are typical for toggle-based presets. #3 takes the place of turning Toggle Mode ON (because I want to control the toggle completely manually). #4-#5 use Long Double Tap to force Engage and set the toggle, while #6-#7 use Long Double Tap to disengage and reset the toggle.
Long Double Tap and Long Double Tap Release are now effectively “remote-control” triggers. Instead of directly turning those loops on and off, I call these presets and engage those actions. If you want another “copy” of these presets on another bank, you could sync them up with toggle groups if desired.
So, I totally get the idea of engaging presets instead of directly engaging the ML10X. I’m not exactly sure why I need the 7 presents for one loop and how it works exactly. It’s fascinating though. Quite interested in how this is working for you.
Admittedly, my method is right on the edge of being a hack. You can’t directly call messages from other banks, but you can “engage” presets from other banks, meaning you can simulate a “press” on bank 3 while still on bank 1, for example. So messages 4-7 are there to give me two “remote control” messages. “Long Double Tap” to engage the loop and “Long Double Tap Release” to bypass.
The reason I’m calling a preset from one bank into another bank is because it lets me have a bank that always reflects the current status of the ML10X (as long as it is updated each time the ML10X switches presets). This is necessary because the ML10X doesn’t do two-way communication in standard MIDI.