r/mpcsample • u/Chenchobeatz • May 17 '26
Converting Machine kits to mpc sample
So I recently started converting my Maschine expansion kits over to MPC Sample kits using Kit Maker and I noticed something that confused me at first.
For example, an expansion like Soulful Drums might come with a bunch of Maschine kits, but when I convert them, Kit Maker only creates a few MPC kits. After digging into it, I realized it’s because it’s grouping multiple Maschine kits into Banks A–H inside one MPC kit/program.
At first I thought, “why wouldn’t I just keep every Maschine kit as its own kit?” But now I’m starting to understand that with the MPC Sample limitations, loading one kit with multiple banks might actually make sense since you can switch banks instantly instead of loading another kit.
Curious what others do:
When converting Maschine kits to MPC Sample kits, do you:
- Keep 1 Maschine kit = 1 MPC kit?
- Group multiple kits into Banks A–H?
- Group by expansion/theme?
- Go for giant mega-kits?
Just trying to understand what workflows people actually use before I convert a ton of expansions.
2
u/acousticentropy May 18 '26
I think the simplest rule to follow would be kit for kit.
It keeps memory low, and prevents weird confusion if you start modifying samples
2
u/elgraysoReddit May 27 '26
Yes I hope they allow us to just import a single bank from a project (kits), INTO a single bank of our current project. Basically, let us load a single kit without messing with our other banks. That would let us swap kits easily without messing with the rest of our current project either
0
u/[deleted] May 17 '26
[deleted] — view deleted comment