Free MPC to MPC Sample Expansion Batch Converter

Hi all,

Hoping this provides helpful for others as it did for me.

Recently, I found out that it is possible to convert my existing (Live 2 in my case) expansions, into an MPC Sample project/kit. While that provides helpful, it is very tedious for someone that has A LOT of expansions (About 22GB in my case).

This batch converter works very easy and fast - you point it to a folder that has you original expansion and it produces ready to copy MPC Sample project files. It retains the projects intended BPM as well as mute groups.

Initially, I convert it into .mpcsample files, but it was hard to figure out the structure due to me not being able to connect a view the files directly on the MPC Sample's internal HDD. This conversation is, in a way a "workaround", as it translates these kits into projects, however it is very easy to retain them as "kits", since as soon as you rename while saving the work you've done, MPC Sample will automatically create a new project under it's default folders, while leaving your kit project untouched. (I simply created a Kits folder on the SD Card to have is separate from projects).

This converter is 100% free. I personally tested it on macOS but I'm hoping it will work on Windows without issue.

The github page contains instructions, description, explanation - and I'll gladly try helping anyone who would be having trouble getting this done.

This was a complete life saver for me, since I was starting to get bored with the few kits that exist by default no the Sample, and here I am now able to use every single expansion from my Live 2.

https://github.com/ab1428x/mpcsample-kit-converter

Just be careful when converting xpm files because it will retain any insert fx, drum fx etc. while most will play back in the sample I’ve found that it’s fairly easy to overload the cpu and there’s no way to turn off or edit any of these fx once loaded into the sample. There is a reason why they created the ‘flattened’ mpcsample export!

That said, should be easy to vibe code an optional flag to null the fx if required.

MPC-Tutor wrote:Just be careful when converting xpm files because it will retain any insert fx, drum fx etc. while most will play back in the sample I’ve found that it’s fairly easy to overload the cpu and there’s no way to turn off or edit any of these fx once loaded into the sample. There is a reason why they created the ‘flattened’ mpcsample export!

That said, should be easy to vibe code an optional flag to null the fx if required.

This converter doesn't carry any FX at all. It only reads the pad to .wav assignments and mute groups from the .xpm, then builds a completely fresh .xpj from a clean device template.

The output is equivalent to what you'd get from a hand built empty project with the samples dropped in. So the CPU overhead issue shouldn't apply here.

How does it handle layered pads?

MPC-Tutor wrote:How does it handle layered pads?

It just takes the first/main .wav in that instance.

I'll see if there is something that can be done to have it converted on the fly, or add the layered ones to empty pads and then Pad Link them.

It does support multi layer pads, be it velocity switched, layered or round robin, you just can't edit anything other than layer 1.

MPC-Tutor wrote:It does support multi layer pads, be it velocity switched, layered or round robin, you just can't edit anything other than layer 1.

cool - thanks for the comments and background information. I'm relatively new to the MPC ecosystem as a whole (barely a year), and this is my first stab at actually making any tool for it.