Cubase 9's Plug-in Manager going wrong

[noiseboyuk]

As a Cubase 7 user, I am SOOOO glad I don't EVER have to worry about upgrading to Cubase 9.

What an abomination and abuse of power. Who the #$#% are they to tell me what plugins I can and can't use?

Un freaking believable.

I can't tell if this is satire or not. Getting that a lot lately.

[wagtunes]

As a Cubase 7 user, I am SOOOO glad I don't EVER have to worry about upgrading to Cubase 9.

What an abomination and abuse of power. Who the #$#% are they to tell me what plugins I can and can't use?

Un freaking believable.

I can't tell if this is satire or not. Getting that a lot lately.

Trust me. I am DEAD serious. I have enough problems with Cubase 7 as it is without having to worry about some plugin police crashing my system.

[noiseboyuk]

Ummm.... that's literally the exact opposite of what VST Sentinal does.

Anyway, said my piece several posts ago, no need to repeat. Jury is still out about the practice, but in theory at the very least this is a very good move.

[wagtunes]

Ummm.... that's literally the exact opposite of what VST Sentinal does.

Anyway, said my piece several posts ago, no need to repeat. Jury is still out about the practice, but in theory at the very least this is a very good move.

Except if you activate plugins that Sentinel deactivates, from what I am reading, it trashes your system. Aside from that, I don't need to go through the hassle of activating every plugin that Sentinel doesn't like. It's just a PITA.

[noiseboyuk]

Except if you activate plugins that Sentinel deactivates, from what I am reading, it trashes your system. Aside from that, I don't need to go through the hassle of activating every plugin that Sentinel doesn't like. It's just a PITA.

I haven't found it trashing anything, and I have re-instated a couple of blacklisted plugs with no apparent trouble. Personally I highly doubt there's any difference between 8 and 9 when it comes to it under the hood, it's just that sentinel keeps the potential trouble makers away. Steinberg have already said that the iZotope plugs blacklisted on OSX will be equally unstable on earlier versions of Cubase, it's just in 9 you are told about it.

There's no real way of avoiding this - if it is plugins that are the biggest cause of system instability, better tools in dealing with that are essential - doubly so when it isn't obvious which plugs are at fault. Once again, Sentinel 1.0 might not be 100% right, but has to be a step in the right direction. When you rely on these tools for your income, the Wild West isn't all that appealing, and a move to stability is a Good Thing. You still have total control over what gets used, anyway.

[zvenx]

[.............Steinberg have already said that the iZotope plugs blacklisted on OSX will be equally unstable on earlier versions of Cubase, it's just in 9 you are told about it.....

And i believe izotope is aware of it and working on a fix. I assume this is on mac not PC. There should be no issue on PC for izotope plugins (except some things may appear in the plugin blacklist but aren't actual plugins.
I believe noiseboyuk was the one who may have pointed out that the ones name iz and not izotope are really not plugins...... (if it is him, thanks, if it isn't sorry for 'blaming' you )

Although I quoted you, I was making a more general point, hope no offence was taken ..
And yes I know you were speaking about MacOSX, mine was more general
rsp

[ShawnG]

Ummm.... that's literally the exact opposite of what VST Sentinal does.

Anyway, said my piece several posts ago, no need to repeat. Jury is still out about the practice, but in theory at the very least this is a very good move.

Except if you activate plugins that Sentinel deactivates, from what I am reading, it trashes your system. Aside from that, I don't need to go through the hassle of activating every plugin that Sentinel doesn't like. It's just a PITA.

No,it simply allows an unstable plugin to crash your daw SESSION. (unless you have any proof at all that anyone's SYSTEM has been trashed.) just like it does to your cubase 7 now.

Either way, at least it allows you to unblacklist it. Try using any plugin that Logic's AU validator doesn't like. That neverending nightmare is why im back on windows and Cubase to begin with.

[Orbit-50]

Who the #$#% are they to tell me what plugins I can and can't use?

MOTU has done this for centuries already.

[arne]

Just to let you know, Steinberg did release the vst scanner to all developers on their developer support forum back in early august.

[Jakob / Cableguys]

Just to let you know, Steinberg did release the vst scanner to all developers on their developer support forum back in early august.

So as a developer I am asked to check all forums of all DAWs regularly to look for any announcements that might have an impact of plugins that have been released years ago?

[Gamma-UT]

In my experience, blacklisting Rewire plugins/bundles would probably work wonders on Cubase's overall stability. More so than VSTs (particularly as Rewire-induced crashes often point the finger at VSTs almost entirely at random).

[fmr]

Just to let you know, Steinberg did release the vst scanner to all developers on their developer support forum back in early august.

So as a developer I am asked to check all forums of all DAWs regularly to look for any announcements that might have an impact of plugins that have been released years ago?

No, but you should test your plug-ins with at least the most important DAW software (I think Cubase qualifies) and have a hand of testers that collaborate with you and use DAWs regularly, and these should report to you when any compatibility issues arise in any DAW.

This is a matter of compatibility. Sure, your plug-in may be totaly safe. In that case, user just have to go to the Plug-In Manager and hit the "Reactivate" button. Of course, if things go wrong, Steinberg will wash their hands out of it, because the plug-in was blacklisted before.

I already wrote that in another thread: I had Play (East West) blacklisted. Of course, I absolutely need Play, so I took the risk and hit the button, since it was working OK in other hosts. It was validated, and is working flawlessly, yet it failed scanning.

Apparently, the scanning tests now are more rigorous. If a plug-in takes too long to validate, we immedately get a warmning asking if we want it to be blacklisted. If we choose to wait a little longer, the majority of them will get validated nevertheless, however, if we hit Cancel, the validation routine blackjlist them and proceeds to the next.

All in all, besides the validation tests becoming more rigorous, I think the Plug-In Manager was a great addition to Cubase 9. At least, we can check and validate the blacklisted plug-ins one by one, instead of forcing a blind rescan as we had to do before. Digital Performer had this feature since years, for example, and also Logic, as has been mentioned, and plug-ins get out of list all the time (all it takes is an update of the AUVAL routine, or of the OS, which happens yearly now), yet I saw noone come here complaining.

[Rommelaar]

I have the same plugins as the first poster mentions, the Grand 3 and ALL cableguys plugins and those are not blacklisted on my Win 10 computer and work fine .

[zvenx]

Jakob, I think at the very least if you make VST plugins it may be in your interest to check whats going on with Steinberg, same with AU and Apple and AAX WITH Avid.

rsp

[swatwork]

So as a developer I am asked to check all forums of all DAWs regularly to look for any announcements that might have an impact of plugins that have been released years ago?

Maybe you could at least look at this once in a while: https://sdk.steinberg.net/.