Meta VCV list

It would be nice to have a dedicated Meta module plugin list in Vcv Rack. This would allow us to be sure plugins we utilize in our building patches are in the module also.

1 Like

This issue has been discussed previously on a number of occasions on this forum.

TLDR: it’s a VCV rack policy issue, and therefore something that 4ms has no say in implementing.

Agreed it would be nice to have.

do you know what is the easiest way to be sure you are using module plugin, whithout having to remember all. I thought this was the best way..

Some people use the VCV Rack ā€œfavoritesā€ system for this — they mark all the modules that are available for the MM as favorites, and then you can filter the list in VCV to show only favorites.

nice idea!

If VCV allowed the ability to point to other library locations other than just theirs, this would not be a problem. If VCV’s file structure had a place on your computer it stored the library files, you could just replace that folder with one that only had MM ported modules in it. I’m sure if it were that easy, it would have been done already.

not sure if this helps but… vcv you can set a custom path to the user folder/modules:

there’s a way to do that via osx. so one could have separate user folders. one containing MM only modules, and the other containing whatever else, and just create a script to rename to the folder you want to use

what ive found to be easier for me, which allows vcv to maintain/update the modules whenever new versions comes through, is having 2 separate vcv accounts. 1 account has only the MM specific modules ā€˜subscribed’ to, and the 2nd account has all vcv modules subscribed to. i have 2 installations of vcv (windows btw, not sure how this works on osx), one instance is installed in the main program files folder, and the 2nd is installed in a sandbox folder on the same drive (using the free sandboxie app). that way i can run both instances simultaneously if need be. each instance accesses one of my 2 accounts. im finding that im really only using anymore the vcv instance/account that sync’s to only MM specific modules.

I only suspected that this was a possibility and it really opens up a lot of things that could probably be done. The thing that would be perfect is if VCV was ok with another party hosting a collection of MM compatible modules as a bulk dump to ā€œseedā€ new installs with only MM compatible modules. This seed of modules would then continue to be updated by the current VCV mechanism, but new module company additions to the library would have to require a new download of the ā€œseedā€ folder (as to not ā€œpolluteā€ it with non-MM modules). 4ms could maintain the seed files, but it would require full cooperation with VCV.

yeah, this is the approach / variation Ive used since the beginning, and posted in on the first discussion of tag etc.

I also use a slight variation of this for development of modules, where I have a local build of vcv.
as ā€˜debug mode’ in vcv, disables access to the online module library.


as for VCV making changes, a change request was created for vcv 2 years agp (?) for just adding a tag, and they decided not to do this (and its extremely simple to do). but as discussed at the time, theres really no motivation for them to do it , and they wont want to have references to external projects … so not going to happen.

I did raise a request, for a generic change to VCV basically to support multiple module lists, that could be useful in a variety of scenarios (including for the MM), but this appears to have fallen on deaf ears.
though in fairness, frankly, I dont see, a much (github) development on vcv these days, I think its seen as mature - which is fair enough.


given the lack of dev on the vcv side, and so felt it was unlikely this change would happen.
a month or so ago, I took a look at the vcv source code to see if I could implement something similar (within a new module) , and initially impressions were pretty favourable.
the idea was basically, Id the list used by module finder, and basically use this as a seed for finding the vcv modules.
so each MM release, you’d basically just ā€˜import’ the new MM module list, and off you go.

busy on other projects at the moment, but I will revert to this at some point, as Im pretty sure it’d work well :wink:

Andrew Belt has been talking about upcoming VCV Rack 3 features in the VCV discord, latest info last month

1 Like

ah, thats cool.

I mainly go by commits on github, and theres been very few in the last year or so.
But I guess, Andrew is doing stuff on a private branch for now.
Hopefully we will hear more soon!