Pad Perform settings does not save?

Question, is the Pad Perform bugged out?

For example, it does not save per project, so if I work on a lot of different projects, I have to take pictures like its the 70's and name them just to keep track on what I have been using.. And I'm not good enough to simply hear some chords and be able to name them.

It seems to randomly store in system memory, where the last Pad Perform set up used may be what is still there the next time I turn on the MPC.. And that's what you'd get no matter what project you load up..

But even here it is not something you can count on.. Sometimes it is NOT the last set up I used..


And so I assume it's bugged.. Unless there's some setting I've missed?

Sadly I'm at work so can't double check what my latest update is.. It should at least not be the very latest as I remember I saw nothing of interest there to motivate taking the update.

I would say it's a bug because it's not doing anything good for the workflow to have it behave this way. Saying that I've only started using the new mpcs since last may and pad perform has always been this way for me.

Pad perform is just a temporary state that you enter to record a performance, like 16 levels. There is nothing you can recall at a later date. The last config you use is not saved in the project file.

Imo it would make sense for pad perform to automatically set itself to the scale and key used in your project. So ideally you should be able to set a project key and scale somewhere (you can do this in the Force) and the default pad perform settings adjust automatically.

It's not a bug, but I would suggest you send it as a feature request.

Ah yeah, that seems to only address saving the ones you create yourself, I meant the ones already on board.. But I'll have a closer look next time I'm on the X

Thanks!