Cubase Plug-in Sentinel: Blacklisted plug-ins

[djw]

@suntower

How did you know this? How was it communicated?

This news article from June: https://www.steinberg.net/en/newsandevents/news/newsdetail/article/future-proof-os-relying-on-64-bit-3778.html

The support of 32-bit technology in our applications will be discontinued.

[c2d]

I have a few plugs that I don’t want (or can’t) replace. I’ve been trying to put all 32bit plugs under jbridge. Perhaps I was foreseeing the day like this would come some day .

It’s a little too early to tell, but so far jbridge seems to be working fine with C9.

[geko]

well I have the same problem with my UAD-1 but I think i will open a new post for this so maybe i will get more direct answer, but its very disappointing

[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

[fgimian]

P.S.: Is there any further information I can gather to send to devs? I can’t see some sort of validation log or diagnostic report as to why these failed that I can send them.

[suntower]

@fgimian

P.S.: Is there any further information I can gather to send to devs? I can’t see some sort of validation log or diagnostic report as to why these failed that I can send them.

DITTO! If a plug-in refuses to be ‘re-activated’, there should be some sort of Reason Code or Log.

[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.

[musicbeat]

@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.

Clearly, you didn’t read this thread/article: https://helpcenter.steinberg.de/hc/en-u … r-Cubase-9

[Steinberg]

Hi all,

dropping 32-bit has been announced in June, right.

The new VST Scanner have been announced to developers in advance as well of course (in August), providing a tool to check if their plug-ins crash on scanning (here is part of the communication, obviously omitting code / tools / download / contacts: https://www.steinberg.net/forums/viewtopic.php?f=250&t=107322#p588614).
So, VST developers didn’t wake up to a surprise yesterday. Many of those affected by issues / blacklisting, have contacted directly by our developers, some actually have fixes ready.

For those who still rely on a few 32-bit only plug-ins, jBridge still works fine.

If you have VST2 / VST3 64-bit plug-ins getting blacklisted, please let the developer know, they usually know where to get in touch for VST SDK related info, if not, they can contact Steinberg Support, we’ll forward the info to the proper people.

[vinark]

@geko

well I have the same problem with my UAD-1 but I think i will open a new post for this so maybe i will get more direct answer, but its very disappointing

UAD1 runs fine under jbridge here on C9 win7 64!

[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.