Cubase Plug-in Sentinel: Blacklisted plug-ins

[Down_Jones]

@JACKnight

I agree with the need for 32bit support.

I use some very cool old organ and percussion vst’s that are obsolute, never be 64 bit, and I have tons of projects with them.

Imagine if your old 1176 hardware would no longer work because, new connectors.

Cheers

Use Cubase 8.5 next to C9. There is no issue. Bitbridging always has been an achilles heel, other DAWs have kicked 32 bit a few versions ago.

[Dharp]

@fgimian

I have two 64-bit plugins that are affected:

Relab’s LX480 Complete (pretty much a Lexicon 480L, amazing verb!!!)
Cableguys ShaperBox (just released)

I’ve emailed both companies.

Do you guys have any other 64-bit plugins disabled?

Cheers
Fotis

My EastWest Play engine is blacklisted. That seems like a big one.

[EricM]

DSarp: you can reactivate the East West Play 5.0.0 Plugin in the Plugin Manager. East West will release very soon an update for Play 5.0.0 that will pass the Scanner without problems.

[EricM]

“DITTO! If a plug-in refuses to be ‘re-activated’, there should be some sort of Reason Code or Log.”
If a plug-in refuses to be re-activated this usually means on Windows that the dll is not a valid plugin dll. IZotope for example installs dlls into the VST Plugin folder that are no valid plugins. The scanner sorts them out.
All iZotope plugins should be available in Cubase on Windows.

[Quietly]

Izotope Ozone 5 picked up and running perfectly on 9 here.

[Svenne]

@gregsimon

On OSX 10.11.6 Pro9 Steinberg’s own "The Grand 3 (3.1.1) is blacklisted despite being a 64bit VST3. Hmm. Should I update to macos sierra then? Seems like that will just add more problems.

I’m afraid that upgrading to Sierra will not help either:
https://www.steinberg.net/nc/en/support/knowledgebase_new/show_details/kb_show/macos-sierra-steinberg-software-compatibility-information.html
Scroll down to “The Grand 3”

The Grand is apparently incompatible with both Sierra and Cubase 9!

[Sonik]

@suntower

1. IMO, there needs to be a way to turn ‘Sentinel’ OFF–like ASIO Guard. At least until you guys have more real-world feedback. Disabling 32 bit support is too huge a leap with no prior warning.

2. Said it before, say it again: you guys need to COMMUNICATE. A big change like this should have been communicated to users MANY MONTHS ahead of time. I’m sure there would’ve been yelling, but so what? At least users like me would’ve had -time- to prepare!

My work is constantly re-using material from many years ago. So almost the biggest thing -I- need is backward compatibility–or at least a way to migrate older work to the newer versions without too much pain.

With no prior warning, I feel stuck… I like the new features of C9, but the unexpected cost of losing a TON of plugs is a real gut punch.

Why not you use 8.5 for old projects?

[Siegfried1974]

Hello,
User of Cubase for a very long time, I rushed on the new version 9 yesterday… In the place, to wait for the first notices…
Thus the big novelty it is a module ‘Sentinel’ (anything that the name frightens) roughly that verifies all your plugins and without explanation that tosses 60 % of plug - in in a blacklist. Roughly, they become unusable… Thus your previous projects died …
The AFTER-SALES SERVICE, after some messages, tells me that I need to contact the editors of the plugin while everything works under Cubase 8.5. “Cubase9 is more stable without third party plugins”
Do not lose 100€ in this update, stay under 8.5.

[Steve1977]

@Svenne

@gregsimon

On OSX 10.11.6 Pro9 Steinberg’s own "The Grand 3 (3.1.1) is blacklisted despite being a 64bit VST3. Hmm. Should I update to macos sierra then? Seems like that will just add more problems.

I’m afraid that upgrading to Sierra will not help either:
https://www.steinberg.net/nc/en/support/knowledgebase_new/show_details/kb_show/macos-sierra-steinberg-software-compatibility-information.html
Scroll down to “The Grand 3”

The Grand is apparently incompatible with both Sierra and Cubase 9!

That sucks. The Grand 3 does works on windows with cubase 9 though.

[Svenne]

@Steve1977

@Svenne

@gregsimon

On OSX 10.11.6 Pro9 Steinberg’s own "The Grand 3 (3.1.1) is blacklisted despite being a 64bit VST3. Hmm. Should I update to macos sierra then? Seems like that will just add more problems.

I’m afraid that upgrading to Sierra will not help either:
https://www.steinberg.net/nc/en/support/knowledgebase_new/show_details/kb_show/macos-sierra-steinberg-software-compatibility-information.html
Scroll down to “The Grand 3”

The Grand is apparently incompatible with both Sierra and Cubase 9!

That sucks. The Grand 3 does works on windows with cubase 9 though.

Are you saying that Cubase 9 does not blacklist it on Windows? That must mean that Cubase 9 is using different blacklist algorithms on Windows and macOS. This only gets worse and worse.

[Mike3345]

If using a project created in 8.5 with Kontakt loaded, most plugins will refuse to load. I’ve reported the bug. (Win10 64 bit)

[Romantique_Tp]

@Svenne

Are you saying that Cubase 9 does not blacklist it on Windows? That must mean that Cubase 9 is using different blacklist algorithms on Windows and macOS. This only gets worse and worse.

The Grand 3 gets blacklisted on Sierra because it’s incompatible with that OS…

[Steve1977]

@Steve1977

@Svenne

That sucks. The Grand 3 does works on windows with cubase 9 though.

Are you saying that Cubase 9 does not blacklist it on Windows? That must mean that Cubase 9 is using different blacklist algorithms on Windows and macOS. This only gets worse and worse.

Yes, my Grand 3 has loaded up in Cubase 9 fine on my Windows PC. Must be a Mac OS incompatibility thing.

[Sunit]

@Siegfried1974

Hello,
User of Cubase for a very long time, I rushed on the new version 9 yesterday… In the place, to wait for the first notices…
Thus the big novelty it is a module ‘Sentinel’ (anything that the name frightens) roughly that verifies all your plugins and without explanation that tosses 60 % of plug - in in a blacklist. Roughly, they become unusable… Thus your previous projects died …
The AFTER-SALES SERVICE, after some messages, tells me that I need to contact the editors of the plugin while everything works under Cubase 8.5. “Cubase9 is more stable without third party plugins”
Do not lose 100€ in this update, stay under 8.5.

Thanks for the warning…. I was just about to upgrade to 9 after watching videos hyping it up.
Will remain on 8.5 for now.
Hopefully we can disable this scary sounding sentinel in the future

[Steve1977]

Just as a counter balance to the above post, when I loaded up Cubase 9, every single 64 bit plug and instrument loaded perfectly. All my UAD, all my Waves, everything.
The only things in the sentinels blacklist were two 32bit plugs (an older multiband and a free melotron plug) that I knew wouldn’t make it through.

[d_archived]

I’m getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.

[Svenne]

@djw

I’m getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.

No they are not, they are complaining that their stable plug-ins are being blacklisted.

It’s impossible to see any pattern or ascertain why a plug-in is blacklisted. As a matter of fact, the same plug-in may be blacklisted on one system, but not on another. It’s obvious that the blacklisting has nothing to do with whether a plug-in is stable or not. What the criteria are, is still a mystery.

@Siegfried1974

The AFTER-SALES SERVICE… “Cubase9 is more stable without third party plugins”

Could this be a first step in making VST a closed Steinberg only format, where no third-party developers are allowed?

[peachy]

Not one single plugin I have blacklisted, that includes Izotope, (apart from the usual .dll’s due to the odd nature of the way Izotope do VST plugins), Arturia, Soundtoys all good Inc. new Echoboy Jr, Cableguys new Shaperbox good, u-he synths all good, Waves and Fabfilter (the ones I have anyway) all good.
Seriously If you have a problem its either very old (look for an update), 32 bit, or just re-enable it in the plugin manager and scan it again.

[Siegfried1974]

Hi,
We can ask together Steinberg to have the option to desactivate the sentinel at our own risk.
I’m really angry to have C9 and can’t work with.

[EricM]

“I’m really angry to have C9 and can’t work with.”
Which plugins are you missing? Are you on Windows or Mac? Have you tried reactivating the 64 Bit plugins on your blacklist?