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 ivato Mon Jun 23, 2025 6:47 am
Hi there,

MPC One user.
So I am still on 2.15.1. So far, the previous iterations of 3.x looked so buggous that I'd rather wait.
I am worried about the migration of projects I am still playing on, afraid that opening it on a 3.x OS may break things like i've read it on these forums.

The day I update my MPC One, I will prepare my projets before, by removing all "drafty" sequences. Some have no consistent tracks ie Seq 1 has a plugin on track 1, Seq 2 has a drum program on track 1, ..
I will clean all that stuff, convert songs into sequences, delete draft sequences, purge unused samples and programs to have a unique sequence per project, and backup everything.

I don't touch anything on the internal drive, everything I do is saved on a SD.

Well, with all this in mind, do you think it is safe to jump to 3.5 or still risky ?

I can't see any feedback about 3.5 here.

Regards,
User avatar
By Neodymium Mon Jun 23, 2025 9:08 am
I did this yesterday moved to 3.5, and then came back to 2.15 checked things out and tried 3.5 again, but I didn't like it for number of reasons. So I've returned to to 2.15. My Project still runs ok.

Just to be sure, I would make a back up of you SD drive. Then give it a go, if you don't like what it does to your project (Like mine separated all my External Synths into 2 tracks, 1 midi and 1 audio, so my track count increased form 16 to 23). I didn't realise what happened and deleted the 7 extra tracks and later accidentally saved it. I don't think it mattered though, as it had renamed it with 'Import' added to the end. I also lost all my Midi learns about 220, so I went back. Found the original file and everything worked. I think having a duplicate back up of your tracks just frees you to explore them and mess around with them in 3.5, and you don't have to commit, you can just go back and load your back ups.
By ivato Mon Jun 23, 2025 12:39 pm
Ok Thank you for your feedback.

@all

No more big issues ?
I have readen about very bad issues like samples not playing, plugins crashing MPC, notes mangled in the piano roll on previous 3.x versions …
User avatar
By MPC-Tutor Mon Jun 23, 2025 12:46 pm
Back up everything and try it out, you won't lose your original projects as you have the MPC2 backups. Regardless, MPC3 uses a separate copy of your imported project with a different name. Sure there are plenty of bugs, as there are in 2.15.1, you just have to decide which bugs you can live with. If you don't like it, downgrade back to 2.15.1. There is nothing 'risky' beyond the standard risks involved in upgrading firmware on any device, e.g. having a powercut mid-update, which is normally still fixable by force-booting into update mode.

But if you just don't like the idea of upgrading, don't, you can just stay on 2.15.1.
By 40Beatz Mon Jun 23, 2025 1:46 pm
My Advice is to Backup Everything to another SD Card or a 3rd one too lol. Use that 3rd SD Card as your Experimental MPC3 SD Card. Now you're free to open and resave your MPC2 Projects in MPC3. Mind you when you do that, the Those Projects will probably be "Corrupted" in MPC2. But that's ok bcz you have TWO other Backups tucked away somewhere.
Give MPC 3 some time. Don't give up on it so quick. Bcz at the end of the day Akai will stop support of MPC2 (If they haven't already). It'll take a lil getting adjusted to a Few things. But after awhile you'll appreciate the workflow. There's a lot of Perks in MPC3. At the same time there's a lot of "Why the Hell They Change That?"
Might as well get use to it. Akai may be a lil slow to address every Issue but I believe its coming.
By Elektrobolt Tue Jun 24, 2025 2:21 pm
ivato wrote:Hi there,

MPC One user.
So I am still on 2.15.1. So far, the previous iterations of 3.x looked so buggous that I'd rather wait.
I am worried about the migration of projects I am still playing on, afraid that opening it on a 3.x OS may break things like i've read it on these forums.

The day I update my MPC One, I will prepare my projets before, by removing all "drafty" sequences. Some have no consistent tracks ie Seq 1 has a plugin on track 1, Seq 2 has a drum program on track 1, ..
I will clean all that stuff, convert songs into sequences, delete draft sequences, purge unused samples and programs to have a unique sequence per project, and backup everything.

I don't touch anything on the internal drive, everything I do is saved on a SD.

Well, with all this in mind, do you think it is safe to jump to 3.5 or still risky ?

I can't see any feedback about 3.5 here.

Regards,

I can only speak for my own usage (MPC X). This is important to know when reading my opinions, since some people have a nasty habit of reacting like opinions are declarations of war.

I have not experienced any general increase in "issues" between the 2.n and 3.n versions. For me, at this point:

* The MIDI issues from v2 are currently also present in v3.
* The lack of custom time signatures is missing.
* Some minor screen operative peeves that I've posted about elsewhere on MPC Forums.

Except for the screen stuff, these things are supposedly in the pipeline to be fixed, as per announcement.

If v2 does not receive the MIDI fixes for example, that means v3 will then have surpassed v2 significantly, since essential MIDI operations has always been at the heart of any MPC.

As for the actual upgrade and regarding old projects... always make a backup of projects, before and after. I am a LONG time (since 1970's) user of music equipment, and backups were almost always needed in some way really, but in the last 15-20 years or so it became almost a necessity. Even when you think that they are unnecessary backups.

I also keep older backups for a while. I am a high functioning individual and create a loads of stuff, and I want to make sure that my creative efforts are safe. If you depend on technology to do that for you, one day you will be reminded that technology is only so good. Never fun to experience.

On a side note, I was also a professional software engineer for 45 years, so I had a habit of depending on various solutions, e.g. github.com which provides a sort of external backup "trail". It is much more than that, but it's an example. Music equipment does not have these kinds of options, or they come with their own solutions, by brand, which when you have lots of equipment is something I rather not engage in. I got music equipment to make music, not to form a one-man IT department to manage 50 small semi-unreliable computers. ;)

Anyways, I am enjoying v3 on my MPC X. No more buggous than v2 IMHO.