+1 for a tag
for now, what Ive done is create a second ‘user folder’ , that I can use for meta module. you can then use -u option for vcv to launch it.
then as above, remain logged out of vcv library, and copy specific MM plugins into the new plugin folder.
as Im on macOS I then use an AppleScript as follows.
do shell script "/Applications/VCV\\ Rack\\ 2\\ Pro.app/Contents/MacOS/Rack -u ~/Library/Application\\ Support/MetaModule"save as an application, so I can now launch MetaModuleVCV app for developing MM patches.
you can do very similar in windows/linux…
advantages of this approach.
- dont need to move folders around.
- your MM patches will be stored separately from other desktop ones
- you can have different selections and also template patch
tag would still be better though… as you still need to copy plugins around, and also remember to update them
another approach would be to create a second vcv account for MM.
but that’d not work if you want to use Pro.
though arguably… that leads to another workaround for Pro users.
create a new account, and use VCV Free for MM, and VCV Pro for desktop.
… as there isn’t really much advantage having a Pro account with the MM.?
this has the advantage that you have subscriptions to the VCV Rack library (on a separate account), so you’ll get updates etc.