Could Multiparameters remember other nested Multiparameters when moving them around? (They dont yet)

[andrewernick]

Well, this sounds like an odd request, but hear me out.

If you work with a nested approach, like having a MXXX module inside an MXXX, you can map the Multiparameters from the "host" MXXX to the multiparameters of the nested MXXX module. We all do that here and there I guess.. but what if you want to re-order multiparameters of that nested MXXX module?

The host MXXX's multiparameters continue to just target that original Multiparameter's number, it will not track where you put it. This means reordering multiparameters will scramble up all the targets the host MXXX multiparameters originally had.

The funny thing is, if you work only inside one MXXX, and you reorder your Multiparameters, it remembers the original targets.

So I would kindly ask, if its possible that multiple nested MXXX / MSoundfactories can be easily re-ordered without me having to open each multiparameter and re-target to the right destination after I re-ordered a nested MXX/MSoundfactory.

For clarification on why thats important, look at the current state of my "LoopGen" device in the attachement. If I change the most inner structure of the multiparameters, I have to basically start all over again. For the moment, it looks like that will be the case, except a future update would make it possible

Screenshot 2025-06-23 152739.jpg

[al808]

So I would kindly ask, if its possible that multiple nested MXXX / MSoundfactories can be easily re-ordered without me having to open each multiparameter and re-target to the right destination after I re-ordered a nested MXX/MSoundfactory.

Hi, not sure if this is of any help, you mention having to "open each multiparameter". I make my life a "little" easier by copying/pasting from the multiparameter's manager into a text editor where I can access tools like search/replace for example. Just checking you're aware of this option.
cheers Al

[Held]

It would be nice if multi-parameter/modulation assignments could get more robust in general. If you rename a module, for example, all assignments are lost too at the moment. I feel like the name should just be for display purposes while a unique ID is used to handle the real assignment.

Ideally, it would be possible to move a module in or out of an container without losing assignments as well.

[vanerio]

I encountered something related too:
When a multiparameter is moved to another position, module banks does not update 'MPs to update' automatically, so all linked multiparameters will be wrong in most cases.

[andrewernick]

So I would kindly ask, if its possible that multiple nested MXXX / MSoundfactories can be easily re-ordered without me having to open each multiparameter and re-target to the right destination after I re-ordered a nested MXX/MSoundfactory.

Hi, not sure if this is of any help, you mention having to "open each multiparameter". I make my life a "little" easier by copying/pasting from the multiparameter's manager into a text editor where I can access tools like search/replace for example. Just checking you're aware of this option.
cheers Al

I was not aware of this, so thank you!

Seems like the multiparameter system could use one or two "quality of life" updates.

But maybe it is a lot more complicated to change the behaviour at this point than I can imagine.

best