I stumbled across a really interesting update to Waves Studio Rack that released earlier this month. Studio Rack is a plugin host, that can be used within any DAW. Before the recent release Studio Rack could only host Waves plugins, so was useless if you did not have Waves plugins.
This is particularly useful because the plugin itself appears within Acid as a VST2 or VST3 plugin. Although I personally have experienced no problems using this plugin in its VST3 form, others might. Using the VST2 version allows you to operate VST3 plugins in Acid with better compatibility - as an example of that, I have an issue with Kilohearts plugins and automation, but using Waves Studio Rack I no longer see that particular issue.
I looked at that, but it's twice the price of DDMF's metaplugin, or superplugin, so I couldn't justify it.. or really see what the advantages of Bidule was. Still, it's good to hear it's working well.
I've noticed since switching to using Studio Rack and SuperPlugin that acid is waaaay more stable. Since moving plugin chains and buses in to instances of both plugins I've not had a single crash... days of editing.
The ironic thing is, the flow structure diagrams in Metaplugin and Bidule look eerily similar to that in Acid's Morphpad edit patch view to the point where I could swear Morphpads are using either third party tool, licensed, internally. Which is such a shame it's tucked away in a (currently) fairly useless feature.
@sheppo I don't know Metaplugin in detail but Bidule comes with a lot of building blocks (What the developer calls bidules) which you can use to basically create your own instruments like in NI Reaktor. But I don't have the patience to do this. ?
b1e95dc632