Importing MPC3 projects into Force

Has anyone had any success in doing this?

I know back on (I think it was) MPC2.15, you could impot your projects to the Force and open them without issue, but I just recently bought an MPC One and updated to the most recent beta firmware, and I'm not able to open any new projects on the Force. Ideas for workarounds? I sent a ticket into akai and left feedback on the beta feedback form, but if anyone has had any workarounds, I'd love to hear it.

Using the MPC as the idea machine while I'm out and about, and then putting the idea into the Force to finalize the track is my ideal scenario, but it might also just be a pipedream

I believe mpc3 projects are structured more like force projects , so it might be possible in theory by manually editing the xpj. Unlikely though but maybe wait until it’s not beta and also perhaps they’ll update the force anyway. In the meantime you should be able to export patterns and xpm from the mpc to your force

MPC-Tutor wrote:I believe mpc3 projects are structured more like force projects , so it might be possible in theory by manually editing the xpj. Unlikely though but maybe wait until it’s not beta and also perhaps they’ll update the force anyway. In the meantime you should be able to export patterns and xpm from the mpc to your force

Didn't even think about exporting pattern data and bringing it over to force. Might try that out tomorrow. Thanks for the tip might hold me over until a (hopeful) fix in the future.

[Edit] you're right about MPC3 projects being structured more like Force projects. In fact, it feels like watered down Force firmware. Imo they should just be working on integrating the MPC into the Force OS as closely as possible instead of spending resources developing something different, and yet so similar.

I'd love to see a day where the workflow between the two is nearly indistinguishable, since then the MPC could just be a more portable Force, which is what it deserves.

The only differences now is the Force clip-matrix & some of macros & the MPC sample engine improvement like 8 sample layer per pad vs 4 on the Force & extra plugins.

I hope Akai make a MPC64 or whatever & use 1 OS for all other MPC models.

B-Wise wrote:The only differences now is the Force clip-matrix & some of macros & the MPC sample engine improvement like 8 sample layer per pad vs 4 on the Force & extra plugins.

I hope Akai make a MPC64 or whatever & use 1 OS for all other MPC models.

Oh yeah, I forgot about the 8 layers.

I can't imagine that would be that much work to transfer to a new force update.

But my point stands; they're so similar they might as well just put them all on the same OS. That would be so sick. MPC64/Force2 or whatever.

GingerWitch wrote:But my point stands; they're so similar they might as well just put them all on the same OS. That would be so sick. MPC64/Force2 or whatever.

If they decide to continue the Force line I think they may well merge the OS, but the fact that they stopped manufacturing the Force a while back would suggest that isn't going to happen. That's said, one of Akai's staff and long time Force user, Tom nice Things, has recently hinted that there is something on the horizon (but that could just be a 3.3.x final bug fix release).

MPC-Tutor wrote:If they decide to continue the Force line I think they may well merge the OS, but the fact that they stopped manufacturing the Force a while back would suggest that isn't going to happen. That's said, one of Akai's staff and long time Force user, Tom nice Things, has recently hinted that there is something on the horizon (but that could just be a 3.3.x final bug fix release).

That fact that they stop making it & stop OS updates at 3.3 while the MPC is now on 3.4 makes me think they rather focus on something new that part of the MPC3 from the start. Hopefully the Force will get that last update but I rather get a new gen MPC64.