Yeh, thanks! I guess the easiest way would be to somehow tag modules that work in MM and be able to isolate them with a search string. Probably way more involved that it might seem 
@danngreen noticed that my script no longer works for the 4ms modules, i.e. it no longer sets them as favorites. Did something change in the way you are listing them?
Yes, we changed how the plugin and built-in metadata is cached.
The built_in.yml file is still active, but the format changed a bit: instead of a separate list for MetaModuleIncludedSlugs and MetaModuleIncludedModules, there’s just one list with in slug: module-name form. So it shouldn’t be too much of a change to get the script to use that format.
For plugins, we don’t keep a big list anymore. Instead we keep a list of the url where the .mmplugin file is hosted, and then when there’s an update we scan that for the module names and slugs and generate the plugin page.
Let me talk with the team and see if we can easily export a yaml file while we’re parsing the mmplugin files.
It would be a huge help to just generate a list of modules to favorite when you build your code… like a single list of the canonical module name. Then it doesn’t matter how your internal schema changes, tools can always use that list to set favorites, add tags or whatever. I will update my scripts to work with that schema. I do wish the VCV folks would allow custom tags… that would solve this once and for all.
OK, the yml file is back up! Format changed a bit, but should be easy to adapt:
https://metamodule.info/dl/plugins.yml
1 Like
Thanks @danngreen. I will update the scripts later today and push the update to git.
1 Like
@danngreen looks like Sapphire modules are missing from the yaml file.
The scripts have been updated and now work with the new plugins.yaml file. They can be found on github. Note that these scripts are fragile and will break if there are any changes to either the yaml schema or the VCV config schema. Please let me know if you run into issues. If people actually are using them I can make them more robust and provide options for filtering which modules are made favorites and which versions of the SDK it works for.
1 Like
Thank you for updating them. These scripts are incredibly useful
It’s under “CosineKitty-Sapphire” (which is the VCV brand slug)
1 Like
I submitted a feature request to VCV rack, with full spec doc including some potential implementation details, for user defined tagging in the software. Figured it would be useful for more than just tagging metamodule compatible plugins.
2 Likes
@jgmrequel, this is the way
@thetenofswords Hi! I just ran the import from 4ms script and it seems to have worked (settings is updated). I’m using VCV Rack Free 2.
Even though everything seems to have worked - I don’t see the modules in my local library when I right click in vcv rack. Is there another step I need to complete?
The script does not add the modules to VCV from the library, it just favorites modules that are supported by the MM. If you haven’t previously added them to VCV they will not show up. That you have to do manually. I could modify the script to do that, but it would be more invasive and I wanted to keep it simple. My ongoing hope is that VCV opens up its tagging system, so that we can tag modules ourselves and then have views for those tags. Then it will be real easy to identify MM supported modules and the versions of firmware that they target.
1 Like
@tenofswords ah ok! Is there an easy way to add all the possible meta modules to my library or do I need to click + on each one one by one?
1 Like
you have to ‘subscribe’ to a plugin brand. that way also any time they come out with a new module in their brand, it automatically is added to your account. i actually had to explain this to a coworker who im tutoring on vcv so i made this screenshot for them. hope it helps here:
i wish there was a way to automatically favorite all the plugins that use 10% or less cpu on mm, but for now i just do it by hand
2 Likes
@danngreen has the yaml file format changed again. Just ran my script again after the final 2.1 update and it breaks. Looks like the structure has changed since my last change. Thanks. I will update when you confirm.
Sorry, yeah we moved some fields around and added the CPU and tags info.
@danngreen, cool, will fix it. Any update on when we can expect MM tag support in VCV?
@dangreen, Done! The latest version on Github now works with the most current version of the yaml file.