Easier publish flow to "beta in plugin store"?

I am writing here instead of creating a new topic, I want to share the current plans to make it easier for developers to give plugins for others to try.

And please note we still plan to add more plugins to the store, while we want to make it easier for developers to get beta testers and users in general to try their plugins, it would be a shame if this results in no more plugins making it to the store. It is best to let community decide on what plugins they want to see in the store, so we will monitor these forums for that. Giving a chance for users to easily try plugins helps with gathering feedback, so yeah let’s make that a process that does not need anyone from the MOD team to be involved.

As some of you may know, we host a service on http://builder.mod.audio/ that allows MOD users to build plugins based on existing technologies. At the moment it supports faust, puredata/hvcc and max-gen~ (with puredata still being quite limited, work in progress).

The first step here is to allow developers to upload an “mk” file in the same fashion as used for mod-plugin-builder. This way the online builder is able to compile generic code and not just projects from faust, max-gen, etc.
This needs to be done carefully because this “mk” file allows for any arbitrary instructions to be placed in there. We will trust the community to not try to break things on purpose :sweat_smile:

After this is done, the obvious 2nd step is to allow persistent builds, and have them build for Duo, Duo X and Dwarf at the same time. After the build completes for all 3, the developer is presented with a special page link. This will be a dedicated page for that specific build that has the “deploy” button accessible.

This link can then be shared with other people and they will be able to simply press a button to install that particular plugin on their MOD unit.

So in short, from the developer’s perspective:

  1. Push code somewhere accessible online
  2. Create a “mk” file describing how the code is built (just like any other in mod-plugin-builder)
  3. Go to builder.mod.audio, pick “custom build”, upload mk file and press build
  4. After build completes, press the “generate persistent build” button (name TBD)
  5. Get a link after the persistent build finishes (it will build for the other MOD units)
  6. Share this link with any user interested on trying out the plugin
10 Likes