Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
By thunderous.commander Fri Jun 19, 2020 2:48 pm
Hi, I’ve experienced the same problem but when I went back to 2.7, the beats I finished in 2.8 wouldn’t load in 2.7. The chops were still assigned to the pads, but all sequences were gone. So I thought cool, I just have to remember there are 2 beats I can only play in 2.8 and go back to 2.7. As I was making another beat in 2.7, every time I wanted to use any vst, the whole thing crashed. Before I installed 2.8 I never experienced any issues at all.
Has anybody experienced this ?
Maybe it’s worth mentioning, that the installation of 2.8 didn’t erase the previous 2.7. Instead I have an icon on my desktop for 2.7 and 2.8, so I wonder if they are clashing and the best thing would be to delete both and then try to install 2.7 again ?
User avatar
By EnochLight Fri Jun 19, 2020 5:26 pm
thunderous.commander wrote:Maybe it’s worth mentioning, that the installation of 2.8 didn’t erase the previous 2.7. Instead I have an icon on my desktop for 2.7 and 2.8, so I wonder if they are clashing and the best thing would be to delete both and then try to install 2.7 again ?


You're referring to the desktop software? Did you rename your desktop shortcuts? The default MPC Software just reads as "MPC", and the shortcuts will always point to the same install directory executable, which is "MPC.exe" (at least on Windows).

Or are you talking about the actual firmware update executables (in which case, it won't matter)?
By thunderous.commander Sat Jun 20, 2020 8:48 am
Yes, desktop version. When I opened 2.7.2 it asked me if I wanted to update to 2.8, which I did. It created a new icon, so I moved the old in the bin. When I found out about the issue, I just moved the old icon back to desktop. They both look identical, but one starts 2.7 and the other one 2.8.

Btw I am on Mac still running El Capitan
By tonyj Sun Jul 12, 2020 6:24 pm
I've been putting off the new update...
I just did it today and this is the first thing I ran into..
At least this makes me feel like I'm not going craZy..

Anywho, for non-destructive assigning I did what somebody suggested earlier and just assigned the sample to the pads..hit each pad and select the slice accordingly..fastest work around this silly bug