MPC4000 to X import issues

Anyone with an MPC4000 and an X have any problems with directly importing projects from the 4K? Generally I’ve just opened the contents of a 4K folder in the X and it initially works fine but over time begins to have problems saving - I’ve built up a LOT of temp projects and duplicate folders this way. Can’t be sure but it seems to be something to do with the old AKP keygroup programs?

I’ve not encountered any real conversion issues so far,but I’ve not imported over projects as a whole file although sometimes the unit would crash if I loaded too many drum kit programs from 4K but not sure which OS my newer machine was on at that time I’m currently on 2.12 and not had any problems since.

I’ve just imported the sequences over individually from my 4K projects and also any drum kits as single programs rather than as Multis other than a few missing random samples inside the drum kits which seemed to be some kind of loading bug as they loaded fine after a second attempt not seen any really issues,I then saved all those programs and sequences as a new project on my newer mpc,it went pretty smoothly in all and my projects sounded as they were recorded on the 4k.

Drum Kits in akp format from the 4K load in no problem,the only thing I had to work around was the key assignments that the samples were placed on inside the 4K drum kit ie the 16 pads on the 4K don’t have the same standard note numbers as the newer MPCs as a default or that may have been my own way of assigning note numbers on the 4K as I don’t use the default layout on the 4k


So the kits won’t automatically be assigned on the direct 16 pads on the new machine as the standard pad/note number assignments aren’t the same across the two generations so you may need to do a little housekeeping after importing if you want them on the 16 pads/Banks,and I didn’t want to reassign them in the 4K just to correspond with the newer mpc notes as it would have been too much work and would mean I’d have to re-edit my sequences too to the correct notes triggered and a load of hassle
it didn’t matter for me anyway as I have the Key 61 so I could find where they were on the physical keyboard anyway

Ah yeah, thanks for these. My point was more that the AKP programs seemed to be corrupted - i.e. they’re causing crashes or errors saving the project once they’re in the X. Would never expect perfect translation but I didn’t expect the transfer to cause bugs in the system…

from the knowledge part of this website:
full story: https://www.mpc-samples.com/article/mpc ... tibility-1

The native program format on the MPC4000 is the AKP. This can be configured to be either a DRUM or KEYGROUP program. AKP format is supported by both the MPC5000 and the MPC Software, but only basic information is successfully transferred.

That‘s why you can start with it, but the details are messed up... the formats are just too different and it would be a real pain to translate the old format into the current xml syntax.

The only issues I've noticed (and I have not done all that much really) is that programs I've made and saved on the 4000, often have messed up ADSR settings.. (I know it's not called exactly that on the X)

So the way it manifests is that if I load up one of these older programs, say a drum program, then all drum hits are just short clicks, and I have to manually tweak the ADSR to where it should have been.

I assume filters are off as well, as there's a different range available, and the X would not really know what it should use instead.

Ibunshi wrote:The only issues I've noticed (and I have not done all that much really) is that programs I've made and saved on the 4000, often have messed up ADSR settings.. (I know it's not called exactly that on the X)

So the way it manifests is that if I load up one of these older programs, say a drum program, then all drum hits are just short clicks, and I have to manually tweak the ADSR to where it should have been.

I assume filters are off as well, as there's a different range available, and the X would not really know what it should use instead.

I think thats how it is regardless of the format you're importing. I've dropped a bunch of old Akai S1000 format CD's into it, none of the envelopes work out right. Like you said they're almost completely closed so you get a little click if anything. I've even had programs panned all the way to one side. Works about as well as Chicken Systems Translator does heh. You just get a generic program with no settings, but it should keep your keymapping intact at least.