

This MIDI layout was used by every MPC since the MPC60 and was the default for any new DRUM program until the MPC 2.11 update. While keygroup and plugin programs have always used a standard ‘chromatic’ MIDI note layout identical to what you would expect when playing a keyboard, DRUM programs in MPCs had always used a layout that seems based on a General MIDI Drum standard – here’s the legacy MPC layout (I’ve added the GM instruments in green below): The problem stems from the default MIDI note mapping found in ‘legacy’ MPC ‘DRUM’ programs (this is the default type of program used for building drum kits). The Crazy MIDI Layout For Legacy DRUM Programs However, the entire ‘factory library’ within all MPC models (and most third party MPC kits) still all use the old legacy MIDI layout, so it’s still worth understanding the issues at play here. Important: In the recent MPC 2.11 update, Akai has changed the default MIDI note layout for DRuM programs to the ‘Chromatic C1’ layout I recommended in this article. So why is this happening and how can we fix this? One thing they are quickly discovering is that while keyboards work really well for plugins and keygroup programs, they might experience a strange mapping issue when playing MPC ‘DRUM’ program using their keyboard. Updated for MPC 2.11! These days a lot of MPC users are attaching MIDI keyboards to their MPCs, which are perfect for playing expressive, multi-octave instrument parts.
