I think the manual is a bit misleading on saving EFX parameters.
It states:
Saves the main parameters of the effects assigned to BUS 1 and BUS 2.
But, on v4.05 at least, it actually seems to save all of the parameters for BUS 1/2 FX whether they’re assigned or not.
Couldn’t find that in the update procedure steps? Anyway the update seemed to work fine
But my effect params are still not retained after a reboot, when I use the fx save command :S
Edit: Apparently I didn’t look hard enough.
Take look at steps 9–12 of the update procedure (bottom of the update page).
I wouldn’t expect the update to fail without doing this, but some of the settings may need to be initialised to avoid unexpected states due to new and/or changed settings between firmware versions. It’s possible Roland just ask people to do this as a precaution, but it’s the first thing they asked me to do when I contacted them about another issue.
At least one reason for doing this, presumably, is to ensure their test unit and your unit are in a comparable state when testing for bugs. The downside is that it takes a bit of time to redo all of your settings – especially for the BUS 3/4 favourites.
Oh shit you are right!! It was at the very end of that gigantic list, I need to be more patient haha
Expected it in the beginning of the process. Will do a reset asap
I don’t believe I’ve ever did a reset upon updates and no problems here minus same user bugs.
It is a long list.
It’d be interested to hear if that sorts it for you.
If it doesn’t, you could try using the same BUS FX settings that I’m using perhaps removing a few variables for good measure.
1 Setup
Disconnect all cables other than the power cable.
Start a new project.
Set EFX Knob mode to Direct.
Bypass BUS 3/4.
Set Direct FX1 to Filter+Drive.
Set the Other page parameters to All, Bypass, BUS1, BUS3, Scatter.
2 Test
Ensure you’re on BUS 1.
Set Filter+Drive cutoff to 20.0 Hz.
Save the EFX parameters: [SHIFT] + [MARK] for 3s (until the pop-up displays).
Switch the device off and on again.
Hold [REMAIN] + [Filter+Drive] to view the parameters.
The cutoff should be set to 20.0 Hz.
Oh no…. I don’t feel like being a beta tester tbh 
I did the factory data reset
I have Drive on Bus 1, Delay on bus 2.
Tested every combo. Save bus 1, cycle power, save bus 2, cycle power, save bus 1 and 2, cycle power and then I was so tired from it that I did it a bunch of extra times because I forgot
It seems to work for bus 1 only some times, and bus 2 maybe one time IIRC…
Huh 
I tried it out about 20 times this morning and it worked every time from BUS 1. I couldn’t get it to work from BUS 2 at all, though I guess I only tried that about five times.
The only thing I can think is that it’s an intermittent issue and I lucked out all morning or there’s something different between our setups.
Thanks for the testing and help!
I’ll try to dig into it more this weekend, make a blank project and run the same test that you shared above, and let you know
No worries!
Hopefully you’ll at least be able to save some default parameters for your favourite FX if it’s working some of the time!
Can anyone else confirm if this bug is happening (or not) for them?
A video I sent to Roland … they acknowledged the bug multiple times but then a month later my ticket is marked as “solved”. I’m interested in selling my SP and trying to gather info if this is just my machine or not. thanks! 
@Affectionate-Bee-781 i am not using catch mode but i just tried it running fw v4.05 and i believe it works as expected, maybe try to update your unit to latest version to see if it solves your issue?
as for the saving efx parameters on bus 1-2 i don’t think you can save two different settings for the same effect hence it’s not doing anything when saving from bus 2. i don’t think it’s a bug either i remember wanting to set up hp/lp super filter and it always saved just last setting and that was prior 4.04 firmware…
been testing sp heavily since last fix and it seems stable even in dj mode and i haven’t run into any of the previous bugs that made me want to throw it out of window so good on my end so far.
Hmm, I can get my updated MKII to behave as in your video, but only some of the time - it mostly respects the catchup setting, and I can’t find a consistent way of making it happen (e.g. one FX on, one off, or changing a value before hitting a pad). But it certainly takes the immediate knob value on some occasions, so I’ll try some more research into what might trigger it.
@doparoma @NickD thanks y’all! I should have mentioned, that’s an old video. I can replicate this on 4.05 (it’s been happening since 3.02 when I got the machine).
@NickD Yes, it doesn’t happen for me all the time but often enough in my workflow to be frustrating. Thanks for validating that it’s happening to you too (and not just a ghost in my machine 
)
FWIW, Roland got back to me again and said they passed it on to the developer. Maybe if other people open a ticket it will help 
Hi all. I may have missed a point in the manual, but is it possible to restore an old backup on new firmware? I just caught one of the projects loading forever after restoring from an old backup. The unpleasant thing is that there was no reaction to the main switch. Restoration was done with the ipad connected. And the project is already booted from the batteries. I was able to turn off the device only by removing one of the batteries. I would also like to note that the update to the latest version was performed strictly according to the instructions and there were no problems in operation up to that moment.
All I experienced was kinda the opposite (I wrote about it somewhere above): with restoring a latest backup made on 4.04 to a firmware 3.05 because I had rolled back to that firmware (because of annoyance with the bugs).
My projects lost all the settings: volume, gate, sends, all was back to default.
I tried to make it work and then realised that I already had the 4.04 App installed on my PC so the 3.05 SP would be witout App; So back to 4.04 and restoring the backup and all settings were good again. Did not have many bugs since then.
Now on 4.05.
I have noticed “floating” parameters in projects after some time on the same firmware version. Can “bank protection” help to keep them in the same state?
So I did some additional testing and I can reproduce it every time:
It seems to remember the Filter params on bus1, but it forgets the delay TIME ie. 1/2, every single test for me…
I’m only half following this but if you save the delay while on Bus 1. Does it save the changes when loaded into Bus 2?