I have seen this kind of request somewhere but I don’t think there’s such a list. We may take advantage of your thread to organize something so that the users can create this data.
We could discuss a standard method to measure the CPU usage (like putting a plugin alone in an empty pedalboard). And we could create a wiki page with tables for each category of plugins. The header could look like this :
This will be generally useful, but there should be a lot of caveats, as the CPU meter isn’t a complete view of resource usage. For example, several plugins use background processing. If I add a single IR cab sim, I see a 20% jump in CPU usage, but if I add a second IR cab sim, it doesn’t add an additional 20%. I see maybe a 5-10% jump in my setup. I have seen this with some non-IR reverbs (Aether in beta comes to mind) as well.
I’m not trying to discourage the effort, though Do it!
This is super interesting thought. I realise Collision Drive and Super Whammy are both power demanding (not a suprise) but only when turned on.
And because I am don’t really want to run them both at the same time, I am now trying to find a way to have one shut down the other automatically…
ie if the whammy is on, turning on the drive should shut the whammy down…
This is driving me mad
you can do this with the Control to CV plugin. Here’s an example. In this pedalboard, I have the Control to CV flip the enable/bypass state of 2 switches. It’s not exactly what you mention, but it does alternate the state of 2 plugins.
You may also need the Attenuverter Booster (multiplier = -1; mode = linear) to invert the CV signal of the Control to CV. The Control to CV is assigned to a plugin and the Attenuverter is assigned to the other so that they have an opposite behavior.
I want to turn on the distortion, 1 want to press 1 button.
Then from there, I want to turn on the whammy and turn off the distro with 1 button
Then finally I want to go bacl to clean sound with one button.
I cant do that…
I suppose with your solution you flip from one to the other, but have you got a way to turn both off ?
Put it another way:
I want 1 button to turn on off the whammy, another button to turn on off the distortion.
But also, in the background, when I turn one of those on, lets say the whammy, while the distortion is on, I want the distortion to be turned off, without any extra tap dancing.
Yet another way to put it:
I want to put somme effects in an exclusive group, where there can be only one of them at any one time. Turing one on will force any other that might be running to be turned off.
I find this a really cool initiative @funkypou! Please let me know if there’s something from our side that you would need.
I would in advance say that this coming from the community will release some overload from our side and get it out quite faster. Win-win kind of situation, I believe
I have a couple of pedalboards where I had the same need and I do this. Basically, a flick of a switch turns on a couple of effects and off other ones.
And use one of the Dwarf footswitches to swap between that? And a single one?
Thanks @jon. On the wiki side, I will try to handle that on my own. I’ll let you know if I have problems. But any piece of advice in choosing a standard method to measure the CPU usage of a plugin is welcome.
OK, that’s clearer now. I’ll let you know if I find a way.
you can use a 2-to-1 and 1-to-2 switch pair to effectively make a “loop” and a CV control to enable/bypass that loop. Then, use another CV control to swap the enable/bypass of the distortion and whammy. When I get a chance today, I’ll post an example pedalboard. It will be a variation on this pedalboard. The difference will be that the loop being switched will not include the 2nd output of the Dwarf.
What I have in mind for having more than 2 is reasoning, not on turning the effect on, but rather how it can be turned off:
Either with its switch going off, or any other switch from the group being switched on.
That’s easy to do, and then take the inverse of that. That is my idea loosely put.