# Newbie MM help needed please **URL:** \ **Category:** General\ **Created:** [November 6, 2024, 3:58pm UTC](https://forum.4ms.info/t/newbie-mm-help-needed-please/700 "2024-11-06T15:58:07Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![danngreen](https://forum.4ms.info/user_avatar/forum.4ms.info/danngreen/32/14_2.png) [@danngreen](https://forum.4ms.info/u/danngreen)\ **Post date:** [November 6, 2024, 10:21pm UTC](https://forum.4ms.info/t/newbie-mm-help-needed-please/700/7 "2024-11-06T22:21:13Z")
> [@glennfin](#): > > Just install **all** the plug-in’s to autoload on startup so I won’t have to think about what patch needs what plug-in. Will that have any effect on memory use when they are all loaded? Well, technically, yes, but there’s tons of memory so it’s not an issue you need to worry about. > [@glennfin](#): > > I see some of those plug-in’s have very many modules inside. So there are modules in a plug-in and modules not in a plug-in… ok… I better jot this all down because if I don’t work with this every day, 2 months from now I’ll be like “huh? what?” 🙄 If it helps, think of it this way: Every module belongs to a plugin. But some of the plugins happen to be “built-in”. Plugins and “built-in” plugins function the same, there’s not anything you need to think about – just use the autoloader and everything will be ready to go when you turn it on. > [@glennfin](#): > > When I tried to play “DualLooperwithverb-DLDx3” From the patch gallery I got = “Audio stopped patch load \> 99%” According to the notes in the thread where that patch was posted: > [@Effect - 3x DLD looper extravaganza](https://forum.4ms.info/t/effect-3x-dld-looper-extravaganza/691/1): > > runs ok for me at a cool 93(% cpu 48/512) with inputs 1-4 plugged in. if you want to run all 6 inputs, you’ll need to most likely set your mm to 32/512. tbh, i can’t really tell the difference in this patch when the mm is set to 32 versus 48. This is saying that the patch runs at 48kHz with 512 block-size, but if you want to use all 6 inputs then you need to run it at 32kHz with 512 block-size. I just tried it and I would recommend running it at 32kHz, for sure. I had good results at a block-size of 64, so you might not even need to change that up to 512. To change the sample rate (48kHz vs 32kHz, etc), go to the main menu, then go to Settings \> Prefs. Change the Sample Rate down to 32000. Then make sure to click “Apply” at the very bottom. Then you can go back to the patch and play it (if it doesn’t start playing automatically). Here’s a thread where sample rate and block size was discussed: > [@\[FIGURED OUT\]Updated to latest MM firmware, single modules are maxing out CPU](https://forum.4ms.info/t/figured-out-updated-to-latest-mm-firmware-single-modules-are-maxing-out-cpu/338): > > This morning I just updated the newest firmware for the MM. Update went fine. I loaded up some newer plugins that have been added, and now I’m seeing the audio stop because of CPU overload. However, I’m only loading in single modules, like the Befaco SpringVerb. My settings are 48/64. Anyone else seeing this? --- _[View the full topic](https://forum.4ms.info/t/newbie-mm-help-needed-please/700)._