
By Tone_y_Touch
Mon May 12, 2025 10:36 pm
Can someone please help me understand what's happening here? Please excuse me if I'm not using the most appropriate language to describe everything, as I'm still an MPC novice in most respects.
I'm using an MPC Touch primarily, but also use a Novation Launchpad X and an Mpk Mini Plus in some situations.
There are certain expansion packs that, when loaded, frustrate the ability of the LPX and the Mpk MP to activate MPC's virtual pads with the corresponding pads on those devices.
I recently discovered the MIDI Monitor though, and identified the problem, if not the reason why it's happening.
When no expansion programs are loaded onto the pads, or if a non-offending expansion program is loaded, the A1 pads on all three devices show up in the MIDI Monitor as a C1 note (Channel 1 for the LPX and Touch, Channel 2 for the Mpk MP).
If I load one of the problematic programs (for example, Hiphop-Kit-DP 600 Degrees Kit from the Dark Parallax expansion) though, and hit the virtual A1 pad, the MIDI Monitor now displays it as C#1, while C1 is now on pad A2 instead. The rest of them are all jumbled up as well. So in that scenario, when I hit A1 on the LPX or Mpk Plus, it's going to activate virtual pad A2 in MPC.
Oddly, none of this effects the Touch. The pads on the Touch always correspond, despite the MIDI signal of the virtual pads having changed.
I can work around it by loading a problematic program, and then just recreating that program in a separate program, manually mapping all of samples and colors. It can be time-consuming though, especially if I'm working with or trying out multiple kits in a project, so I'm hoping someone can help me understand why this is happening and/or if there is a way of preventing it from happening.
Any help would be appreciated.
I'm using an MPC Touch primarily, but also use a Novation Launchpad X and an Mpk Mini Plus in some situations.
There are certain expansion packs that, when loaded, frustrate the ability of the LPX and the Mpk MP to activate MPC's virtual pads with the corresponding pads on those devices.
I recently discovered the MIDI Monitor though, and identified the problem, if not the reason why it's happening.
When no expansion programs are loaded onto the pads, or if a non-offending expansion program is loaded, the A1 pads on all three devices show up in the MIDI Monitor as a C1 note (Channel 1 for the LPX and Touch, Channel 2 for the Mpk MP).
If I load one of the problematic programs (for example, Hiphop-Kit-DP 600 Degrees Kit from the Dark Parallax expansion) though, and hit the virtual A1 pad, the MIDI Monitor now displays it as C#1, while C1 is now on pad A2 instead. The rest of them are all jumbled up as well. So in that scenario, when I hit A1 on the LPX or Mpk Plus, it's going to activate virtual pad A2 in MPC.
Oddly, none of this effects the Touch. The pads on the Touch always correspond, despite the MIDI signal of the virtual pads having changed.
I can work around it by loading a problematic program, and then just recreating that program in a separate program, manually mapping all of samples and colors. It can be time-consuming though, especially if I'm working with or trying out multiple kits in a project, so I'm hoping someone can help me understand why this is happening and/or if there is a way of preventing it from happening.
Any help would be appreciated.



