Bypass
-
@Christoph-Hart Is there a way to implement a bypass button that is passed to the DAW so it's linked (in one way I think) to the DAW plugin bypass button? Some plugins have this ability, but I don't know if it's AAX specific...
I can't help pressing F5 in the forum...
-
Yeah that‘s just asking for trouble. I guarantee it will work on 50% of all hosts, not more not less...
-
@Christoph-Hart Is there a way to implement a bypass button that is passed to the DAW so it's linked (in one way I think) to the DAW plugin bypass button? Some plugins have this ability, but I don't know if it's AAX specific...
You can make this task with router matrix. Route the dry signal to dedicated channels and then just control the wet and dry volume amounts with the "Bypass Button".
When it's Bypass is off:
wet gain: 0 dB
dry gain: -100 dBWhen it's Bypass is on:
wet gain: -100 dB
dry gain: 0 dB -
@orange Thanks orange ;)
But I know how to do that, it was more about "linking" the DAW plugin bypass with the UI bypass -
That would be a nice feature @ustk
I‘m always struggling with the placement of the bypass switch on my GUI. In logic for example there is a big bypass button directly above my desired placement, so my bypass would be obsolete
Tbh I‘m not even sure when I used the plugins bypass instead of the bypass on the DAWs the last time
-
@clumsybear If you want to remove your own bypass, it's not a problem then, because the DAW bypass will work anyway
The only case (for what I see at least) where it's cool to have your own bypassed is on interfaces based on real hardware where you find the on/off or bypass. You can also switch the light of a VU meter for instance. This is the only case scenario (but very common) where having a bypass on the GUI is of importance. And in the scenario, being able to link with the DAW bypass makes sense. For all other cases, the DAW bypass is enough IMHO.
