Newbie MM help needed please

[glennfin]

Just a warning, this may be a thread with multiple questions. Just received my MM a few days ago. Updated the firmware, watched a few videos, read the quick start guide. After watching the Loopop video, I was able to load a single module (Ensemble Osc), select the automap and was able to input CV, and hear the module working in my rack. Here’s where my confusion starts…

Before creating a patch in VCV rack, I figured I would download some patches from the Patch Gallery and give those a try. I saved several patch gallery files with the file extension .YML to an SD card, was able to load them into MM but could not get any audio out. Is there another step required to make these work in the MM besides just loading them from the SD card?

My next challenge will be attempting to create a simple patch in VCV rack, load that into MM and make it work…

Any help greatly appreciated.

Glenn Fin

[TheTechnobear]

@glennfin

I saved several patch gallery files with the file extension .YML to an SD card, was able to load them into MM but could not get any audio out. Is there another step required to make these work in the MM besides just loading them from the SD card?

as such there is no configuration needed.

two things…

• have you download and loaded all the 3rd party modules?
  (are they showing up in your module browser on mm?)
• could be its using midi or cv , or a clock (cv) as input.

I assume the ‘factory’ patches are working correctly.

[glennfin]

Thank you Bear for the reply.

Some factory patches are working, getting audio out. The multiple braids patch works great and sounds awesome. No, I haven’t downloaded the 3rd party modules as I’m not sure how to do that.
Sorry for my ignorance, just trying to wrap my head around this

[glennfin]

Ok, so some progress here. I downloaded all the plug-ins (14 total?) Placed them in the plug-in folder on the SDcard…Check me on this… It looks like some patches require plug-ins. Maybe that’s why the patches I grabbed from the gallery aren’t working? How will I know when a patch requires a plug-in? and which one? Do all patches require a plug-in?
.
I guess I’m asking what is a plug-in?.. sorry this is very confusing. I wish there was some sort of formal manual

[danngreen]

Sounds like you got it! Yes, plugins work just like how they work on VCV Rack or on many other programs: they are extra modules that you optionally install. So just like if you download someone’s patch they made in VCV Rack, but they use a bunch of modules that you don’t have installed, you will need to install them (from the VCV Library, usually) in order to play the patch.

Explained differently: the MetaModule comes with 160+ modules built-in. These are the modules from 4ms, Befaco, HetrickCV, Eightfold, Nonlinearcircuits, Cloned Instruments, and Valley. Then, if you want to get more modules, you can install a plugin. This is great because to get more modules you don’t have to install a whole new firmware, you can just load a small file that gives you new modules and you can even pick and choose what modules you want installed.

If you go to the main menu and click the + icon, you can browse the list of modules installed, which is all the built-in modules plus plugin-in modules.

Not all patches require plugins, it just depends on what modules the person who made the patch is using. But, from what I’ve seen, almost every patch posted here uses at least one module from a plugin.

At this point, there are (only?) 14 plugins, so it’s easy enough to just keep them all installed all the time and never have to think about it. The way to keep them installed is to put them on the SD Card like you’ve done, and then in the plugin tab in Settings, click each one that’s loaded and set Autoload on. Like this:

Using Plugins - MetaModule Manual

Then just make sure the SD Card is inserted when you power on. The downside to having plugins auto-load is that the startup time takes a little longer. If this is a concern then you can turn some of the plugins to not Autoload anymore, and just load them manually if you want to use them.

[glennfin]

Ok, Thanks for the explain Dan. I’m starting to get it. 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?

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?”

When I tried to play “DualLooperwithverb-DLDx3” From the patch gallery I got = “Audio stopped patch load > 99%”

[danngreen]

@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:

@offthesky

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

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?

[glennfin]

Wow! thanks so much Dan. I’m celebrating right now because I just created my first patch in VCV rack, loaded it into MM and it’s working!. Just a simple DLD into the VCV mixer and I was able to map some control knobs to the DLD. I can’t figure out how to setup trigger out’s from the MM to the DLD trigger in’s like “reverse, hold” and the time switches, …

[offthesky]

@glennfin

I can’t figure out how to setup trigger out’s from the MM to the DLD trigger in’s like “reverse, hold” and the time switches, …

you’ll want to use something like the 4ms “source” module, with it’s outs going into the reverse or hold inputs on the dld, and the physical knobs on the metamodule in vcv mapped to source’s two knobs… should look something a bit like this:

[glennfin]

Thank you for the reply. So adjustment of the knobs on the Source module send a trigger out?

How is the timing toggle switch (+16, =, 1/8th) on the DLD accessed?

[Zymos]

You just assign it to a knob