FR: Add MXXX1 to MXXX/MXXX1?

[jmalge]

MXXX can be nested inside itself, which is quite useful especially for those times I want to use an MXXX preset as a component of another preset. And of course it would be nice to save on resources if some of these presets aren't multiband.

Can we also get MXXX1 as a module, preferably in both MXXX and MXXX1?

[MeldaProduction]

I suppose that would make sense. Though it wouldn't give you much, since ModularEx is pretty much the same thing except for the active presets... What others think?

[vectorwarrior]

There should only be 1, there are already a LOT of modules. So if it's the same as ModularEx, either remove ModularEx and add MXXX1, or leave it as it is, in my opinion

[MeldaProduction]

I agree, let's keep it the way it is.

[jmalge]

Well, the reason I was asking for MXXX1 rather than just use ModularEx was because of the rather low Modulator/Multiparameter count in ModularEx.

I suspect that anyone who actually tries to load MXXX/MXXX1 presets into ModularEx will quickly discover that they keep running out of MPs, among other things. I know I did. Rebuilding the preset to switch over to global Mods/MPs when more than 4 are needed defeats the purpose (i.e. save time/work) of nesting them in the first place. I also thought I'd have better luck asking for MXXX1 as a module rather than asking for ModularEx to be upgraded.

But no biggie - I'll just use MXXX as a module inside MXXX/MXXX1 when I want to nest things. Thanks for considering it.

[DarkStar]

Just for info (I had to look), in v12.03

MXXX: 16 modulators, 128 Multiparameters.
MXXX1:16 modulators, 128 Multiparameters.
Modular: None
ModularEX: 4 modulators, 4 Multiparameters.

[MeldaProduction]

That's correct, but each of these resources requires a significant amount of resources, so it is imperative to use as little as possible. And one rarely needs too many in submodules. All of it is mainly useful for the main instance, so...