Ram-memory already full

Having issues with ram-memory full.

Is this normal when only having 5 plugin - tracks and 1 drum-track with 1 single sample on it?

The manual says the Force should be able to handle 126 tracks right? It barely handles 6. I have not even started recording my vocals yet and its already giving me problems. I use an SD card for almost everything except the expansions inside. My plugins and everything exist in the SD - card among with the samples and projects, mixdowns and so on.

Is this normal and how do I go about freeing up RAM?

Very grateful for help,,

Thank you!

/Yonis

Depends on the plugins you are using, many of the premium plugins are memory hogs and arguably not particularly suitable for anything other than an MPC Key (which has an extra 2GB ram).

A single instance of Studio Strings uses up 31% of RAM on a Force (roughly the equivalent of loading a 300MB 24bit wav keygroup program). The Stage plugins are around 20% each. Fabric is around 7%, Fabric XL is often double that. You can see how using multiple instances of these plugins is going to quickly tank your RAM.

The original 'free' plugins are generally very low on ram, even 0% for basic synth stuff (e.g. bassline etc).

Options: Swap plugins for lower ram versions. Bounce plugin track to audio track (and disk stream it), or convert to a keygroup with autosampler (assuming you use optimised multisampling techniques - or set the samples to be streamed from disk) .

Thanks for your reply!

OK, that was sorry to hear about the plugins using up much RAM-memory. On the other hand thanks for the tips about bouncing to audio tracks! I will definitely try that. It also feels good to know that this is normal.

By the way, is 57% RAM usage a lot or OK? Because that is what I have on this project right now.

Thank so much!

When I see people asking about memory issues I feel like they are not sampling their Audio as intended. More memory is always useful so I can’t knock the hustle…but I will say that any DAW can have the same issue. The solution is to record the plugin audio as samples, arrange it with midi, then apply the mix after that.

or akai could just build their DAWs-in-a-box with more CPU power and usable memory than a smartphone. what might have been sufficient for the first generation firmware in 2017 is clearly not adequate to run 2.14 in standalone in 2022 without all these workarounds and gymnastics. just refresh the damn product line already

Can Force disk streaming solve the the lack of memory for plugins problem?

ravmitterhoff wrote:Can Force disk streaming solve the the lack of memory for plugins problem?

Plugins themselves do not support disk streaming, but you can of course use disk streaming to reduce overall project RAM usage via its use in audio tracks and sample programs, hence making more RAM available for the plugins.

Just be aware that disk streaming in sample programs has to be manually activated 'per sample', there's no way to just automatically turn this on for all samples. THis setting is saved in the project, so if you load that same program in a different project you'll have to individually re-enable the disk streaming for all the samples again.

Also there is likely performance issues when disk streaming so many indivudal samples from within sample programs, which is likely why it's so convoluted to enable it.

Ultimately the problem with the plugins is not so much the RAM in the Force, more the poor memory management within of some of Akai's plugins.

Can you please name those plugins? Will help planning ahead.