Akai Pro MPC Series | Low Memory

This article serves as a guide to educate on the MPC's RAM and how to manage your MPC's resources in a project regarding 'Low Memory'.

Note: If you are receiving 'Disk Space Low - Warning Low on Temporary Space' or 'Please check temporary path in preferences and memory use' - refer to this dedicated article instead: MPC 3 | Disk Space Low - Warning Low on Temporary Space

MPC RAM Explained
Controller Mode
Plugin Usage & Limits
Bounce to Sample / Bounce To Audio Track
Deleting Unused Samples
Auditioning Kit Samples Rather Than Loading Multiple Kits/Samples

MPC RAM Explained

All MPC’s are built with a fixed amount of RAM:

Gen 1:

2 GB: MPC Live, Live II, MPC X, Key 37, MPC One, One+

4 GB: MPC Key 61, MPC X SE

Gen 2:

8 GB: MPC Live III

16 GB: MPC XL

RAM is the dynamic memory used by the MPC to physically hold your currently active project. In simpler terms, the larger the RAM - the greater the performance/handling.

RAM is in charge of handling things like:

Plugin instruments - Each plugin instrument loads its entire sound library into the MPC's RAM
Audio samples loaded into drum programs - Each drum program loads all its assigned samples into RAM at once - even if they are not being triggered
FX processing data - Adding insert effects, automation and long audio tracks also consumes RAM, as this must be buffered in real time for playback.

If you receive a 'Low Memory' message whilst working on your projects - this typically indicates that your project is overloaded with active elements, such as plugins, insert FX and drum programs. If your project contains a high usage of these elements, this will be put a strain on the MPC's RAM and processing.

To help alleviate this, we recommend the following steps:

Controller Mode

If you are working with a heavy project, we recommend using the MPC in controller mode along with the MPC desktop software. In this set up, the MPC will not use its own processor and RAM - it will use your computer's resources instead.

If you wish to remain in Standalone mode, we recommend optimizing your project load in controller mode first using the steps below:

Plugin Usage & Limits

It is important to note that the MPC (Gen 1) can load up to 8 plugin tracks per project in Standalone mode. In contrast to Gen 2 MPC's (Live III and XL) which can support 32 plugin track instances.

With this in mind, each plugin instrument also loads its entire sound library into the MPC's RAM. Some are ‘heavier’ than others – i.e Studio Strings & Fabric.

So if by chance you are nearing this number, or you are using multiple plugin instances of 'heavier' plugins - this will affect the processing on the RAM and result in 'Low Memory' and potentially 'Project is Missing Plug-in Files'.

To alleviate this, we recommend:

Deleting multiple instances of the same plugin
Bouncing the plugins to audio tracks as described in the chapter below

Bounce to Sample / Bounce To Audio Track

The Bounce to Sample function renders the current track in the arrangement as an audio sample and places it in the project’s sample pool. By default, it will be named Bounce and appended with the track name. Use the Audio Tail field to set the amount, in seconds, of extra time added to the end of the resulting audio files.

The Bounce to Audio Track function renders the current track in the arrangement and adds it as a new audio track in the project. The Main Mode will automatically switch to the Audio tab. By default, it will be named Bounce and appended with the track name. This function does not work for MIDI tracks or CV tracks. Use the Audio Tail field to set the amount, in seconds, of extra time added to the end of the resulting audio files.

Main Mode: Tap the pencil icon in the 'Arrangement' tab

Arranger View: Tap and hold the plugin track

After this, you can delete the plugin tracks by tapping the pencil icon besides your plugin track and tap Delete Track.

Deleting Unused Samples

Delete: In the screen that appears, tap any unused samples to delete all unused samples from the project
All Samples: Tap All Samples to delete all samples from the project (from all tracks, sequences, and audio or MIDI tracks), or tap Cancel to return to the previous screen.
Purge: To delete samples from the project (to create more free RAM space for sampling time, audio recording, etc.), tap Purge.

Auditioning Kit Samples Rather Than Loading Multiple Kits/Samples

As mentioned earlier - each drum program loads all its assigned samples into RAM at once - even if they are not being triggered. If you have loaded multiple drum program, this can also be tasking on the MPC's RAM.

To alleviate this, we recommend auditioning drum program before loading them into your project:

1. Enter Sounds Mode, and select a location - either Factory Expansions or User Expansions

2. Select your expansion and the relevant expansion folder (Drums or Keygroup)

3. Tap the headphone icon (top right corner)

4. Once enabled, tap and hold on a cell’s play icon to audition the selected sound.

You can also audition demo projects, samples, drum or keygroup programs types via Menu > Browser. Ensure that Auto is enabled via the Audition tab:

Use the six filter buttons to show only specific types of files in the list below. Folders will still be shown in the list.

Tap the P/page icon to show project files only.

Tap the bars icon to show pattern files only.

Tap the four-squares icon to show kit files only. Tap the plug icon to show plugin preset files only.

Tap the waveform icon to show sample files only.

Tap the three-pages icon to show all file types.

Further guidance on auditioning sounds can be found in this article: Akai Pro MPC Series | How to Audition Expansions