As soon as I saved the settings and entered the bank, the MC6 PRO crashed and rebooted and was then stuck in a boot loop. The startup bank home screen did not even appear, the restart was briefly after the display of the Morningstar logo in the left display.
Fortunately, I could start in safe mode. After removing these messages and restarting, the MC6 PRO worked normally. Tried to add them with “On Enter Bank - Execute Only” - boot loop again, so it was no coincidence and the error is reproducible for me.
Just sending a program change in state 1, setting the pedal back to bypass in state 2 (so that I can toggle between preset engaged and bypass), some housekeeping for the toggle state (need to do this manually as I also have long press actions on some other similar presets) and setting a position in a message scroll list based on the current preset number so that this scroll list is in sync with the directly selected program.
Just encountered another situation where an “engage preset” action reproducibly crashes the MC6 Pro, this time not in a boot loop, but in an action attached to a button.
This happened when starting to set up a sound bank where each button should engage several pedal presets from other banks controlling the individual pedals.
When setting up the first preset on this bank, I had only a single “engage” action for a preset for the first pedal. This worked fine. Then I added a second “engage” action for the second pedal. Now the MC6 Pro crashed when pressing the respective button.
Is there a problem with more than one “engage” action in a row? The action on load of the startup bank which put the MC6 Pro in a boot loop also had two “engage” actions …
Creating another “All Banks” backup in case you need this for troubleshooting.
This preset sends some MIDI messages depending on position, changes the toggle state and modifies a message counter and works perfectly fine on its own when not engaged from the other preset.
Once I disable the “Toggle Preset” action in the target preset by setting its action to “No Action” the MC6 Pro no longer crashes when this preset is engaged from the other preset.
FYI: the presets engaged at startup causing the boot loop were also using “Toggle Preset” actions.
One additional test: with the “Toggle Preset” disabled for the engage preset targets, these preset can also be used safely (without reboot) in the “On Enter Bank - Execute Once Only” actions for the startup bank.
So the problem is not sending an “Engage Preset” action, but the erratic behavior of the invoked preset.
