Exactly

 

Something strange with Cubase then?
Plugins are not blacklisted, they function normally for me, except the bypass button.
I will re-install with the same user name to see if things change.

Funny thing is, i did once buy a BOZ plugin but for some reason it was very difficult to get it registered so i just installed R2R.

 

There are more plugins that DO NOT have the typical bypass button. D-pole, stuff from 2B and more.

 

Well, it might be considered clickbait to post with such a lack of information in the subject, even if not intended as clickbait.
I thought it had something to do with marketing.
With no other information, it could be ANYTHING to do with Boz Digital, so perhaps many will look, only to find it is about some problem.
I find it interesting, so I would not think to consider it clickbait, but i see how others might.

 

This was not the intention. On the other hand the more BOZ users see this thread the faster we can solve this.

 

As I said, it might be considered clickbait even if it was not intended.
If i step on someone's foot, I stepped on their foot, even if i did not intend to.
Whether it is technically clickbait is not something I considered deeply, as I think it lacks a certain element of deceit.
Perhaps it is, perhaps not.
But as your reply mentions simply trying to attract as many BOZ users as possible regardless of their potential interest, it makes me consider it more deeply.

 

I thought about it and changed the title.

 

And that will make it easier to find now and in the future if this is cropping up for more people, too.

 

Ctrl Alt+Click on the bypass button in Cubase causes a hard host-side bypass (the true bypass you expect). The normal bypass doesn't actually bypass, the plugin still receives audio and can do whatever the f it wants. Technical explanation

 

Last edited: Dec 27, 2021

Came here to post this pretty much.

So the Official VST Standard(tm) doesn't mandate bypassing but leaves it to the plug-in. To make matters worse, VST2 and VST3 behave differently. VST3 is better/worse in this regard because it has bypass and deactivation for different inputs leaving quite a lot for the plug-in to do. So as far as I can tell, only Steinberg assumes that the plugin knows what it is doing.

Most hosts, like Ableton, just ignore what a plugin is doing and then does a true bypass for plug and don't feed it further data until unbypassed.

 

CTRL+Click did not work, but Alt+ Click works, windows/cubase.

What is also strange is, that when you load the plugin, the bypass button right from activate effect button is missing on all BOZ plugins.

 

This is weird really, if a plugin says "I can't do bypass" then it's the host's responsibility to handle the bypass. Source: the API documentation.

So BOZ is doing something wrong here, that's my take. Are you using a VST2 or VST3 version by the way?

Glad you found a workaround though!

 

Great, happy that it's sorted now!

An aside, this kind of shit is why I still install both VST2 and VST3 versions, just in case.

 

Yes. Thank you @phumb-reh and @demberto especially!

 

20 is better!

 

How can you check the registered name on previously installed plugins?
I forgot which name I did input in the keygen and the plugin only lets me see the version but not the registered name.

I want to install Panipulator 3 but I don't want to mess up the others plugins.

 

Last edited: Feb 12, 2022

->