Yes, I get it. But how long have developers, and users alike, have had to switch to 64bit? There’s a point where you need to move forward, and sometimes that means not supporting old code. It’s been 11 years since the first 64bit DAW came out, which I believe was Sonar 5. I think it’s time to move forward, especially considering that most problems encountered by users is due to unsupported and/or bad behaving 32bit plugins. This is a smart move by Steinber, IMO.
I haven´t used 32bit plugins for 4 years. Best stability upgrade I ever did.
And also to be fair, we knew this was coming. It should have happened already with C7 if you ask me.
And on the other side. Avid broke the 32bit plugin path years ago. Loud cries there as well. But getting rid of the horrendous RTAS architecture was a bliss for PT users in the long run.
i just tried to re activate ozone 5 …it failed…how could that be…???
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.
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.
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
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?
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.
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
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.
UAD1 runs fine under jbridge here on C9 win7 64!
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.
My EastWest Play engine is blacklisted. That seems like a big one.
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.
“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.
Izotope Ozone 5 picked up and running perfectly on 9 here.
I’m afraid that upgrading to Sierra will not help either:
Scroll down to “The Grand 3”
The Grand is apparently incompatible with both Sierra and Cubase 9!