I’d leave it like you’ve done it in the screenshot. The shift feature is intended to be used in scenarios where a simple toggle can’t do what you want. If you just want to toggle between to different states of a single pedal there is really no need to use ‘shift’.
All right. If you want, you can help me solve the last problem.
Now activating a preset (B for example) deactivates the strip on F as I wish.
Then, to activate the dual reverb engine, I press F and the strip on F continues. All is fine.
The problem is that when I press B a second time to activate the Od200 boost, it turns off the dual engine reverb but the strip on F stays on. And that’s not so fine.
What I would like is:
Either the strip on F turns off when the reverb goes to the engine A (only one reverb)
Either the dual engine stays ON and does not turn off when I activate the boost. (this second solution ist my favorite)
It doesn’t matter what the solution is but what I would like is for the synchronization to remain correct.
Thank you a lot.
To achieve this you can set the ‘set toggle’ message in your first screenshot to ‘pos both’ instead of ‘pos 1’
.
.
.
.
Not sure what is going on exactly. I’d have to see the whole preset, but apparently you have a message in your preset that toggles the reverb to ‘Engine A only’ regardless of what position you are in. Therefore I assume that whatever message this is, it’s set to ‘pos both’. If you set that to ‘pos 1’ it will only trigger if your preset is in the default/disengaged/position 1 state.
‘Default state’ , ‘disengaged’ and ‘position 1’ are three different ways to refer to the same thing, which might be confusing at times.
On All my preset A, B, C, D, E i think the position of the reverb is Set to both, aß you mentionned.
I’m at work. When I go home tonight i will vetify that.
I have try your first advice, it works fine. When boost ist activated , the “dual engine” returns to “mono engine” and the strip on F disappear.
the second variant didn’t work, but anyway, the first one is perfect.
Thank you 
hello people, how can i solve this problem please
here is the bank
Morningstar_MC6PRO_Bank_Backup_Blues Driver_20240607_183117.json (89.2 KB)
@james ? an idea ?
Yes, its a bug! We’ve got a fix already, planning to do a release early next week.
I can share the file here first if you want to give it a go this weekend.
[2024-06-07_MC6_PRO_Firmware_v_3_12_11_beta.hex|attachment
EDIT: I was thinking of a different problem than what you were facing so I struck off the text above. It’s not a bug.
Thank you,
i will test that new firmware within 30 minutes
Hello,
na changes on my problem
i have two possibilities.
1: in the bank settings, whe clear all preset toggles (wich is the case in my last video), the problem remians the same
2: clear all preset toggles is set to off.
i have no feedback wich effeckt is ON all strip are illuminated
honestly, the mc6 pro is more and more complicated for me. I really begin it was an error to buy it; it’s a pain in the ass to programm it to work as i want…and honestly, without @GuitarWolf i think I would have already thrown it out the window.
why do I say this?
I have a Walrus M1 pedal.
if I activate the chorus for example (background and strip on) and I switch to the phaser (which will of course be effective, tonally speaking), the background and strip of the phaser light up but those of the chorus do not go off.
I don’t understand how the pedalboard can display that 2 effects of the same pedals are on when this is impossible in reality.
You will tell me that I did not program it correctly, of course, that must be true, but it is unnecessarily complicated.
Why does activating my OD 200 boost turn off my chorus background? I can’t find the explanation for that either.
I spend hours and hours in my office trying to program instead of playing guitar.
sorry, I’m not in a good mood at all, it annoys me to have to PM @GuitarWolf , who until now has always helped me.
Sorry, I mis-interpreted the issue in your video ( I was skimming through your video and assumed that it was a problem that was unrelated to yours ).
So, I just watched the video again, the problem you are facing is that when you select another preset to activate, the previous one does not de-activate. Is that correct?
The controller simply does what you tell it to. Preset A may toggle off when you select Preset C (as per your video), but if you didn’t add a message to send (to turn off your M1) when Preset A gets toggled off, then nothing will happen.
Add this message to your Preset A:
When you select Preset A, your M1 will engage. When you select Preset C, Preset A will be “disengaged” and will trigger this CC#31 value 0 to be sent, which will bypass your M1.