Beautiful VCV lineup, surprised I haven’t heard of them before.
v2.0.0-dev12.2 needed.
Beautiful VCV lineup, surprised I haven’t heard of them before.
v2.0.0-dev12.2 needed.
these are really awesome, loving the resonator and grain verb, ty much!!
Hey Thank you! That was fast!
Just out of curiosity, once the 2.0 firmware becomes official does that mean that these along with the other ported modules on this forum would be part of or available on the main downloads page or will ported plugins always be found in their respective githubs?
Great question. I have been very lazy about my mm-plugin metadata setup, not sure if @danngreen can answer how I can best keep that tidy for future release (or potentially get them listed on the 4ms plugins site?)
We’ve been thinking about this, too. I’m typing up a README for publishing releases right now.
The way our website works is we give it a list of github repos and a list of plugin names to search for in those repos. The .mmplugin file needs to be in a Github Release. Our script scans the Releases for the latest version. Versions like vX.X-dev-12
will go into the dev plugins zip file, and versions without the current dev version string will get listed on the main plugin site (unless they are version v0.x or contain dev
in the version name).
Also, the plugin-mm.json file will need to contain the list of modules.
I wrote up a bit about what’s needed for a plugin to be scanned by our scripts and hosted. There’s a fair bit of complexity since there could be multiple versions, and certain versions work with v1.x firmware vs v2.x latest firmware vs. older v2.x firmware… But I think we have it figured out now.
I tried to put all the info in this document, including an example github workflow script (which is not necessary but is nice because it builds it for you). You also can manually create releases on github and upload the file you built.
Let me know if you need help getting any of that set up.
Thank you so much for porting