MPC 3 old projects

Hello. Anybody tried to open old Projects after the new MPC 3 beta update ? Everything working fine or complications ?
Don't wanna risk the update when older projects get problems. In the description I'm reading something like "legacy project import", but I'm not sure if these three words answer my quetion", that's why I'm asking here. Thanks. Heiko

Yeah I'm waiting for the YT guinea pigs to try first and wait for the reports before I even think about upgrading (when it's released). If there could be complications then it's not all bad though - it will force me to actually finish the 15 or so tracks I have on the go before I jump to 3.0

I meant to add - Andy Mac made it look easy to import projects from Ver2 so I'm hoping its not a problem but the workflow seems too different for there not to be a single problem - I've heard others mentioning that Programs doesn't even exist on 3.0 anymore so I'm not sure how 3.0 deals with it but fingers crossed. It would seem a bit odd for it not to work when there will be a LOT of people with older projects that they want to continue working on after upgrading.

I'm waiting until they release it myself

But if you import it, save it to a different location/name, most likely you'll be fine...

make a folder for your 2.0 beats and another for your 3.0 beats
and then you can downgrade your OS if you want things as they are and can open your old projects...

Don't think that a DOWNgrade is possible after update. I'm not in hurry, so I will wait until things are getting clearer, cause more questions will follow.

You can install any version of firmware that is functionally compatible with the hardware. So you can upgrade/downgrade from any point available to you.

That said, if you load a project from MPC 2.x into MPC 3.x firmware, it will upgrade the project, so if you overwrite the project from MPC 2.x with the MPC 3.x firmware, it is one way and you will no longer be able to load the project into MPC 2.x. Make backups, save new versions of your projects... be persistent

NearTao wrote:You can install any version of firmware that is functionally compatible with the hardware. So you can upgrade/downgrade from any point available to you.

That said, if you load a project from MPC 2.x into MPC 3.x firmware, it will upgrade the project, so if you overwrite the project from MPC 2.x with the MPC 3.x firmware, it is one way and you will no longer be able to load the project into MPC 2.x. Make backups, save new versions of your projects... be persistent

Yeah that makes sense, as does making separate folders for 2.X and 3.X. Thanks

Yeah, I'm persistent in my projects, without self made problems. But I'm not persistant in speculation and telling what is what, somewhere between warm and cold. So I'm not sad about 2.0, no problems with it. Just interested in 3.0 FACTS so far.

I think MPC2 projects will translate over best in early MPC3 versions. Chances are that with every update new features will be added or changed making it harder for MPC3 to import MPC2 correctly. I would update projects asap after MPC3 release, or track everything out. In case you really need the option to go back to MPC2 projects in MPC2 environment consider getting a cheap second hand MPC One for this reason.

Back all your "old' projects up first before importing into MPC 3 where you save them under a different name like: "New Old Beat 01", "New Old Beat 02" etc, etc...

Not backwards compatible.

Load projects and make sure to save in a new os3 folder unless you don't want to use it on os2 again.

Some sorting will be required if you use multiples of the same program/plugin.

Planemo wrote:I meant to add - Andy Mac made it look easy to import projects from Ver2

In the official video he only showed loading a single sequence from a 2.0 project, not the whole project. This really jumped out at me.

I've seen one YouTuber seeming to load full projects, but I'm not clear whether these were pre-prepared to make it look smooth - e.g. uniform track/program structure across all sequences. Because in any other case you'd expect there to be a bunch of extra tracks or other hacks/workarounds seeing as how different the OS structures are at base level. And given the YouTuber involved I'm not going to take this in itself as definitive proof that it works well.

Apparently Akai are saying that 3.0 projects can be opened on 2.0, which tbh would seem fairly credible and probably easier than going the other way, at least in terms of just track/sequence structure.

Force can load your mpc projects, dont be shocked if mpc 3.0 can as well.

Loaded up a fairly complex 2.x project without too much drama, but it was well structured (e.g. same track order throughout and consistent program assignment per track) so not sure how it deals with some of these crazy muddled up messes that some people like to make

Have to accept it's going to use MIDI tracks + routing to deal with programs used on multiple tracks

So far I'm also finding mpc2 kits and programs don't need any tweaking.

MPC-Tutor wrote:Loaded up a fairly complex 2.x project without too much drama, but it was well structured (e.g. same track order throughout and consistent program assignment per track) so not sure how it deals with some of these crazy muddled up messes that some people like to make

Have to accept it's going to use MIDI tracks + routing to deal with programs used on multiple tracks

So far I'm also finding mpc2 kits and programs don't need any tweaking.

Same here, so far so good, just learning the way around and where things have moved too.
I always did my projects in a 1:1 layout across the sequences as well, so my Song bounce was ready to go.
Still getting used to the Digital Performer way of working with the multiple MIDI tracks to one program, not too bad though.

For the most part, its still the same MPC, new coat of paint, its not like they reinvented anything in here.