I’ve been using the ML10X together with a MC6Pro (and now a MC8Pro) for a little over a year and I realised I actually had a lot of questions about getting to my ‘Ideal Use Case’ of using them.
When I first got the ML10X I imagined using it this way:
I’d recall preset on the ML10X using a PC message - preset would have the pedals I wanted routed in the way that I wanted. But they’d all be bypassed.
I’d then send CC messages to trigger on/off various loops.
Next song comes along, I recall another preset on the ML10X with a different order and bypass/engage loops again as per normal. I get that this works in a “Simple Mode” but working with Stereo chains, I was hoping it would work in “Advanced Mode” as well.
What i’ve tried:
I’ve tried setting up presets with pedals ordered the way I want them. On the preset in the editor i disengaged all the drive pedals. But somehow when I recalled the preset, everything was engaged. I bypassed all the drive pedals (figuring i could just engage them when i needed them) and there was this loud hiss (the kind you here when there’s a buffering/impedance issue).
I read this topic on how its not a straightforward solution given the potential for feedback loops or issues with the signal flow ( [BETA] Engage/Bypass loops in Advanced Mode ) . Also, the thread is more than a year old now so I’m not sure if any progress has been made so far.
So the TLDR question is: how can I get to the Ideal Use Case? Am i missing something? Apologies if this has been discussed before. I havent scoured through everything yet.
The firmware’s existing feature set, even in the beta, is pretty stable at this point. Many of the issues you describe are fundamentally signal-based not software-based, and that’s just the nature of advanced mode.
Depending on your advanced mode signal chain, you may have to figure what turning things “on” and “off” means, due to the feedback loops you described. Does it mean cutting the output from a particular loop (because a “bare” connection will cause feedback), or if it’s a MIDI-enabled pedal, bypassing the pedal but not the loop? I often end up having custom engage/bypass sections for each ML10X preset.
Would you like to share a screenshot of the signal chain that you’re describing here?
Here’s the signal chain that I tried to see if i could implement a simple on/off for my drive section.
The trouble im facing is that i cant seem to get the loop bypass messages to work. Does it mean i have to do a combination of Cut and Restore commands in order to bypass a pedal?
Actually, since you’re never merging, this signal chain should presumably let you bypass everywhere. You’re saying you get the sound of feedback when you try to bypass the drives? That shouldn’t be happening.
I run my ml10x and mc6 pro very similarly to this with 0 problems, the only immediate difference I notice is I use the Morningstar message type to control the ml10x. Next time I’m at my pc I can look which firmware versions I’m using if that’d help.
