And noticed that the 4ms modules are not in the yaml file, so gotta add those by hand or I can just add a hack to the script that does that.
You mean a “metamodule” tag in VCV Rack? I haven’t heard any news from the VCV Rack team if they plan to do that.
I thought I saw them, we just re-ordered the list so that the builtins are after the external plugins.
I asked the VCV team if there’s any update on the matter.
Will keep you guys updated.
In April they said they would be looking into implementing it.
Let’s wait and see 
Maybe an idea to help out a bit, before a potential vcv tag turns out.
I have used the script initially to fill up my favorites in vcv, although I needed a bit of manual work anyway… not too bad, because I needed to get to know the modules regardless. Pretty fun work.
But every time an update for the modules gets out from you guys, I want to also update the list of favorites in VCV. Because there are so many modules it is hard to know what the new ones are.
So maybe a tag in the module finder that makes it possible to sort out the newest ones? That would help out in updating the favorites list. Also, just a list in this forum could also help, or maybe there is somewhere but I haven’t found it.
Sorting by update/created date… that would solve it.
It’d be great to have an automatic way of handling new modules in the plugins. Our automatic tests we run before a release give us a report with any new or missing modules. So, we have that data but would need to pipe it into the website some place.
For now, I’m just trying to mention the new modules in the release notes (e.g. Plugins 2026-03-30 or Plugins 2026-02-24)
1 Like
this is kind of a minor annoyance in the big picture. I am super satisfied with the product. To be honest, there is too many modules anyway. I seldom use that many, and quite often I get confused by the sheer number of them.
I think that limiting myself to some manufacturer or something else generally produces better results in my patching.
This might be interesting for some of you:
I’ve added a “v2 mod” the my MB module, which replaces the default module browser with a modified one. This module has been around for quite some time, but it only had the very old “v0.6” browser and a modded one from “v1”.
The modded version from v2 has custom tags and I implemented auto-tagging using the YAML file, so you can attach a custom tag “MetaModule” super easy to all supported modules.
This is all in development, but you can download the latest development build (or build it yourself), if you want.
10 Likes
Thank you so much for this! 
1 Like
Ah, very cool, that’s a great idea to use the custom module browser to handle custom tags. Very nice.
1 Like
Nice work!
1 Like
very cool, and very effective too !
1 Like
For some reason I loose the favourites tag when using the MB plug in. Can we marry the 2 some how ?
This is because MB had favorites in VCV Rack v1, but v1 had no built-in function for it. I’ve just added an option which lets you select if you want to handle MB its own favorites or use VCV Rack’s function for this.
3 Likes