In use with the metamodule I find myself building patches like I would in VCV rack on the interface itself, however I find I have some common module pairings I am using at times that I would like to repeat where possible inside of other patches. I would love to have an option to turn something like the following patch into a module for use in the metamodule.
not specifically the above patch but as an example
The thought is on the metamodule, users would have an option to interact with a new module that look like the metamodule vcv module, the underlying patch would either be abstracted or if possible editable on the metamodule as well. Like a function or a recursive metamodule, or a metametamodule(mmm).
The metametamodule would be a module representation of a setup of a patch including descriptions, controls and io, making common controls and patching into and out of the metametamodule hopefully clear and intuitive.
I dont know if its possible to do this but I think it would be super helpful to basically abstract a collection of modules behind a metamodule looking module on the metamodule.
This feels like it may not scale appropriately and my usecase might be overly niche.
I didn’t know about vcv selections previously thanks for sharing. My feature request here is not just to have vcvs support in metamodule, but to offer an abstraction layer of a selection of modules through a common virtual metamodule interface
In the example above you I was trying to suggest that users would interact with the virtual metamodule instance on the physical metamodule as an individual module. The virtual metamodule instance would have controls and jacks that could be interacted with the same as any module in a metamodule patch.
The above example would be represented on the physical metamodule as a module with 1 input and 4 outputs with 8 active knobs (note the patch description states 2 gate inputs but only 1 is connected in the screenshot).
The MindMeld PatchMaster collection is similar to this idea in VCV rack, I don’t know how popular that is or how popular this could be.
This request is to do something like the MindMeld but the thought is if it’s an abstraction layer of an underlying set of modules and connections there may be value in it being a native metamodule feature instead of porting the MindMeld modules.
