Need help with custom expansion not loading in MPC DAW

I have made about five or six custom MPC expansions now and they load just fine in my hardware but a couple of them error in various ways when I try to load them in the MPC DAW. Is there a list of guidelines for what can and can’t be included in an expansion in order for it to work in the DAW version?

No guidelines, but I can almost certainly pin down what the problem might be. However, need more info, for example, which specific MPC versions are you running in standalone and MPC Software? And exactly what errors are you getting, including details on what you are doing that triggers them and detail the wording of any error messages.

MPC-Tutor wrote:No guidelines, but I can almost certainly pin down what the problem might be. However, need more info, for example, which specific MPC versions are you running in standalone and MPC Software? And exactly what errors are you getting, including details on what you are doing that triggers them and detail the wording of any error messages.

Created with MPC Expansion Builder 3.7 and I'm trying to bring it into MPC 3.7 on my PC. Currently I'm still using 3.6 on my MPC Live (OG model) and my Akai Force and all my expansions load fine on there by copying the folder over to the Expansions folder. But, for example, when I try to load this expansion I just finished in the DAW, I get the following error:

Image not working, what is the text of the error?

MPC-Tutor wrote:Image not working, what is the text of the error?

"This expansion pack file is invalid"

I've never seen that before, not sure what could trigger it. The expansion builder is effectively just zip compressing your folder, the only file it adds is an XML file, so perhaps the new expansion builder app is messing up XML creation under certain circumstances. Other than that, when you import it, the main MPC app creates a cache file from all the contents so perhaps there is something in the manifest that is triggering a bug, perhaps a weird file name (unsupported character, encoding issue etc).

I'm afraid the only way to troubleshoot this is to investigate it step by step, if it's not obvious what the connection is between all the non-working XPN files then you might need to start testing stipped down versions, gradually adding files until you create an XPN that won't import.

I've been making some expansions the past few days in MPC Software 3.7, no problems so far.