Comments by midrun
Hi Frank
Thanks for your question!
From technical side: no there is no advantage, actually a disadvantage, since more CPU is used for the same audio processing.
From UX perspective: yes there is an advantage as you can see the configs of the plugin without the need of opening the plugin, as well quick access to all the parameters.
In the end it’s your individual workflow which determines if it’s useful for your case or not.
I personally like to have my favourite plugins within a wrapper. Therefore, I create from time to time wrappers for the plugins.
As you mentioned you have a programming background, you would probably have no problems with creating the wrappers by your own (as it’s not complicated but of course time-consuming if you have an eye on detail).
If you want to try out the ones I’ve shared, let me know!
I can for sure provide you some access to them and would as well be very happy for feedback and ideas for improvements.
Thanks for your question!
From technical side: no there is no advantage, actually a disadvantage, since more CPU is used for the same audio processing.
From UX perspective: yes there is an advantage as you can see the configs of the plugin without the need of opening the plugin, as well quick access to all the parameters.
In the end it’s your individual workflow which determines if it’s useful for your case or not.
I personally like to have my favourite plugins within a wrapper. Therefore, I create from time to time wrappers for the plugins.
As you mentioned you have a programming background, you would probably have no problems with creating the wrappers by your own (as it’s not complicated but of course time-consuming if you have an eye on detail).
If you want to try out the ones I’ve shared, let me know!
I can for sure provide you some access to them and would as well be very happy for feedback and ideas for improvements.
@avcilardilkursu You’re welcome! By the way, if you have any other audio effect plugins you’d like me to make a wrapper for, just let me know.
@FreddyFingaz You’re welcome! I’m finally creating wrappers for all my most-used VSTs. User-friendliness and workflow are much improved when all parameters can be edited in one place. I’m very happy when I can also make life easier for others.
Hi @jimbeam!
On Gumroad, I have a community chat and a support email address. Please send me a message on one of those channels with details about the Live version you’re using and which plugins/devices you tried to load. I already have a guess about what might be causing the Randomizer initialization issue.
I’m planning to release an improved version of the Parameter Randomizer in the coming days, but additional details from you would still be very helpful.
On Gumroad, I have a community chat and a support email address. Please send me a message on one of those channels with details about the Live version you’re using and which plugins/devices you tried to load. I already have a guess about what might be causing the Randomizer initialization issue.
I’m planning to release an improved version of the Parameter Randomizer in the coming days, but additional details from you would still be very helpful.
Thanks so much for your support, really glad you’re enjoying the device.
The community tab on Gumroad is a bit hidden, but you should find it in the left navigation with a section for Parameter Randomizer. On the product page where you downloaded the patch, you’ll also see my email if you’d like to reach out directly.
About the issue you mentioned: that’s on me. The Randomizer was first designed as a quick “try things out and remove it” tool, but many users (rightfully!) want to keep it in projects and restore their settings. I’m working on a solution. Saving the history is trickier than expected, but I hope to release a second version soon with proper config restore and some performance improvements.
Really happy about the great feedback and ideas from the community. it helps a lot. Thanks again for flagging this!