WaveLab 12 - Inspector Plugin Bypass buttons

Now that I am using Audiomontage mode for the first time, I am wondering why there are no Bypass buttons in the Inspector. Am I overlooking something? In the master section, I use them all the time for comparisons and other tasks. Is there any plausible reason why people would prefer not to have them at the plugin slots in the inspector? To me, this seems very random.

1 Like

Yay, this button is excactly what I am looking for! But as you can see, it’s not there. Only the Master section has it. Is there a setting to enable it, similar to selecting which track buttons to show in Cubase? Can’t find one.


I gotta ask - you’ve expanded your app window out, correct? In your screenshot the plug-in bars are “cut off” like so:

But if just resize the window, I get this:

Came here to say the same thing. I looks like your master section got too narrow and is hiding the button.

Try to drag the left edge more to the left, or perhaps recalling the Default Layout Preset:

2 Likes

And you can assign a short cut to that bypass as well.

Thank y’all for responding. You’re right - the buttons were just hidden.

I think the underlying problem is an inconsistency in the GUI. I resized the sidebar with the Mastersection open to the minimum possible width (MPW). When using a laptop, screen real estate is precious, so it’s likely that users do this. Unfortunately, MPW behavior differs between Mastersection and Inspector, even though they share the same area and essentially the same structure.

It would avoid unnecessary confusion and improve usability if this wasn’t an issue. When using Audiomontage, I think it’s not uncommon to temporarily expand the Inspector to see all the faders and Clean/Enhance tools that might be hidden to the right. The thing is, when setting the Inspector back to MPW, we should be able to just drag the window border to the right without worrying about basic buttons disappearing into nowhere. Just as it is realised in the Mastersection view.

So from a usability standpoint, I think this is an avoidable bug. Would be great if this could be fixed in the future.