Ever lasting beta plugins?

I can see a lot of beta plugins but only little progress with them. As a user it is nice to test out new and experimental stuff but it feels weird if it stays experimental forever.

Should I rely on it or not? Why is it beta at all? Are there any known issues? Does it just need someone who makes a GUI for it?

It would be cool if there would be more transparency about this.

3 Likes

Full agreement.
And: There are some beta plugins which do not even have inputs/outputs. So I wonder about the sense.

Some of those will stay in beta forever until someone steps up to take care of them.

We are moving full speed with the “Labs” side of the plugin store, that will allow developers to manage and push plugins to the store without having to deal with the someone from the MOD team manually approving things.

In my own case, I hope to start maintaining zynaddsubfx in Labs. Making a full modgui would be too complicated, but it is possible to expose the OSC port on the modgui, so that one can connect with the desktop application to it. Since v1.10 will support the lv2 state extension, this means whatever changes are made via desktop zyn->mod plugin will be saved and persistent. :slight_smile:

3 Likes

Is there an overview page like https://pedalboards.moddevices.com/beta-plugins or on github/… where you can also see how active the development of a $plugin is?

2 Likes

Why are plugins still listed in the beta area if they are no longer - maybe since years - developed to get into the official plugin store?
In this case a beta plugins overview homepage would be useful for the user to make his own assessment.

because someone might have a use for them.
also the “beta” is not officially supported anyway. sometimes we have plugins there because they just come from a bigger collection of plugins. it is quite some work to try all plugins in a big collection to see which ones are okay and which are not… so uploading the whole thing it is, because out of 6 bad ones there might be a gem.
this is just my opinion though. and again, the “beta” plugins are not officially supported.

another thing to consider (this is just an example) is that it gives us a nice overview of what is possible. there might be a beta plugin that is very good, but crashes if we do X or Y. while not usable, it already tells us there is a great plugin available if we fix the crashes.

back when we published all these plugins to the store, we could not predict which ones would be good and which ones “bad”. so we uploaded them all behind an advanced-user-mode-only filter. then slowly moved plugins out of “beta” into “stable”.

4 Likes