Some progress related to bypassing and engaging loops in Advanced mode! If you do give it a go, let me know how it works for you.
Firmware
Please select the appropriate firmware for your controller. If it is the REV_B design, you’ll it see printed on the enclosure, and the USB port is orientated horizontally (REV B) instead of vertical (REV A).
2024-06-28_ML10X_Firmware_v_1_1_3_BETA.hex (521.7 KB)
2024-06-28_ML10X_REV_B_Firmware_v_1_1_3_BETA.hex (557.1 KB)
Overview
Consider this connection:
When A Tip is bypassed, the connection will look like this:
Pretty straightforward stuff. The complication arises when the signals split and merge.
Consider this slightly more complicated connection:
An A Tip bypass will look like this:
Another even more complicated scenario:
An A Tip bypass will look like this:
Basically, the prior loops will take on the connections to the outputs on A Tip. This may or may not work for your use-case.
Feedback Loops
Consider this scenario:
Now, if A Tip is bypassed, the connection will look like this:
You can see that there is a feedback loop which will introduce a whine/noise if your signal is on high gain:
Cut/Restore Outputs
If using the ML10X message type on our MC controllers, on top of ENGAGE and BYPASS of loops, you can also choose to CUT or RESTORE the output of the loops.
In the same scenario earlier, instead of bypassing A Tip, you can choose to cut the output on A Tip, which will give you a connection like this:
This will give you the ability to merge, or A/B certain pedals by breaking the merge connection.
MIDI Control
CC Messages
Engage and bypass of loops follows the same CC implementation for Simple Mode. For Cut and Restore of Loops:
CC#30 - CC#39 controls A Tip, A Ring, B Tip… ~ E Ring
Value 0 cuts the signal, 127 restore the signal, 64 toggles between cut and restore
