Loading MPC Windows 7 Projects into MPC Windows 10

Hey Gang,

Has anyone successfully loaded an MPC project made in Windows 7 into MPC Windows 10?

The Windows version is not relevant, it depends on the MPC Software version you are running in each system. Generally speaking, the latest version of the MPC Software will load a project made in an older version of the MPC Software, but the reserve direction is typically problematic.

mike841 wrote:With all respect MPC-Tutor,

The Windows version is completely relevant.
Any project made in Windows 7 will not load into Windows 10 no matter what the MPC version is.

Maybe I'm misunderstanding your question. but an MPC project file, XPJ is platform neutral, it does not matter which Windows OS version is it made on, nor does it matter if it was made on a Mac. The MPC Software will load an XPJ file regardless of where it was created. What is important is what MPC Software version it was made with.

The OS that was hosting the MPC Software, be it Windows, Mac or Linux (i.e. standalone MPC) is not relevant.

That's what I thought. So I contacted Akai who replied the same way you did. So I thoroughly retested and relayed my findings to Akai. A couple of days later they refunded my money with no further comment. The only variant in my tests was the OS.

Need more info on this, as that makes no sense, it's a bit like saying a WAV file recorded in Windows 7 somehow doesn't work in Windows 10. There must be some other reason for the issue otherwise all third party developers would be in trouble as their expansions would only work on the platform they were created in. And we know that's not the case.

What exactly is happening when you try loading the XPJ in Windows 10 - error message, crash, partial load of some resources, nothing at all? How are you loading it - double clicking from explorer, dragging into the MPC grid, using the file browser? What version of the MPC Software was used to make the XPJ, and are you loading it into the exact same version in Windows 10? How was the project transferred from Windows 7 in the first place, via disk? Could the disk be corrupt?

Could you post a link to the XPJ in question, e.g. dropbox or similar? I don't want nor need any of the samples, programs or sequences, literally just the .XPJ file.

No problem. Appreciate the help.
https://1drv.ms/u/s!AlFYEX5xMPCKd7t_8WwUTa4ZXxs

Thanks I’ll have a look at this tonight. Could you provide more info as per my previous post?

Sorry forgot..

1. Upon loading the project, MPC immediately closes, as if I had hit the "X" tab.
2. I loaded the project two ways, from an MPC X and by Drag-N-Drop into the MPC software.
3. I made the project on version 1.0 on an Akai Rennaissance.
4. The project was copied from a Windows 7 computer onto a thumb drive, copied from thumb drive into the MPC projects folder on a Windows 10 computer,

The MPC Software version used to make the file was 1.7.1, it loads on my Mac running 2.10.1 without crashing, obviously missing all the sounds and programs etc.


Looking at the file list in the XPJ I suspect the problem is related to the VST plugins you are loading, which seem to be Stylus RMX and Spark (which I can confirm is incredibly buggy in the MPC Software). My suspicion is that the MPC is trying to load one of those and this is causing the crash.

It's not clear why Akai would refund you your MPC Software purchase price for this type of issue, all very odd. The first thing I would suggest is removing the Stylus and Spark XPM programs from the projectData folder (or rename them) and see if the XPJ now loads without them present. If it's still crashing, start a new project in MPC 2.10, then drag and drop individual programs from the projectData folder (try all of them including the MIDI ones), then try the 'all sequences' file and so on. something in there is clashing, but I'd bet money on it being related to third party VSTs.

Well, that just changed my plans for tonight.
Thank Tutor, I never would have thought of this.

Mr. MPC-Tutor Sir.

Whenever your paddle is ready, I have assumed the position sir.
But if you would be so kind to answer one last question, how could MPC v1.9 and v2.1 open a project that v2.10 could not?

mike841 wrote: how could MPC v1.9 and v2.1 open a project that v2.10 could not?

This troubleshooting info would have been something useful to share in the original post.

If the project is working in 2.1, why are you still trying to load the original 1.7 project? Save a copy of the project in 2.1, or whatever the newest version of the MPC Software is that will load it and use that newer version for your troubleshooting.

But most likely Akai have changed the way they handle VSTs in 2.10 which is why the project is working in other versions. They might have tweaked something to accommodate one plugin and this has caused problems with other plugins. Have you tried starting a fresh new project in 2.10 in Windows 10 and loading some of these plugins into that project. Are the plugins up to date? Legit or cracks?

VSTs are a problem as they are created by third parties, Akai cannot control any aspect of the VST. Which is why I'm surprised they refunded you, certainly not before making you rule out any issues with the plugins (i.e. as per my recommendation to disable the plugin programs before loading).

It got complicated, that's why I didn't go into specifics.
They didn't just refund me out right. there was a lot of back-and-forth and I bought two upgrades on their recommendation that didn't work. They only refunded one.

Why didn't I trouble shoot with 2.1? Because I trusted Akai and they said all newer versions can open older versions. I mean, of the four or five emails between us, not once did they suggest any trouble shooting tips. Only for me to upgrade. So, (unlike yourself) being unaware of how xpj files work, coding, ect. I concluded that it must be the Windows version that was at fault.

Did disabling the plugin programs fix the project?

Oh absolutely! You were right on the money.
It was both Stylus RMX (because it needed an update) and the Arturia plugs (I don't know why).