Feature request: User-assigned module names

Feature Requests
1

Here’s one of the biggest pain points about patching on the MetaModule: I often have several of the same module — often a utility like the MIDI>CV module or the Atvert 2. The MetaModule interface only identifies them by the module name, so I have to keep track of which Atvert 2 is which using their position in the patch, or follow the connections.

It would be great if, instead, I could assign each module a custom name.

A simple way to implement this would be to use the Stoermelder Glue module, which lets me assign custom labels to modules in VCV Rack. The Meta Hub could look for a Glue module in the VCV patch and, if it finds one, pull those labels into the .yml patch file. (Ideally it would also be possible to set and edit those labels within the MetaModule, but you could use a firmware interface for that; you wouldn’t need to port Glue to the MetaModule.)

2 Likes
2

Ok, user-assigned names is a good idea, it goes along with naming Knob sets and mappings.
I’ll have to look at Glue and see how the info is stored in the patch.

I had started to address this, never implemented it fully, but there is some code in there that numbers each module which has more than one of the same type in the patch. So if there is one EnOsc, then it’s just called “EnOsc”. But if you add another then they are called “EnOsc 1” and “EnOsc 2”. This way might not be very intuitive especially if EnOsc 1 pairs with VCF 3 and EnOsc 3 pairs with VCF, etc… so the idea of naming it yourself is nice.

1 Like
3

It attaches a label to the module id and stores the x/y position relative to the module coordinates. I guess it will be quite difficult to port it this way to the MetaModule.
If you need any infos please let me know.