Hello Dear Friends,

I have an issue with Cubase 9.5
Many Plug-ins does't show up in Cubase pro 9.5, they are Blank!

All wave Plug-ins
Eiosis AirEQ & E2Deesser
All FabFilter plug-ins; show up BUT the knob's doesn't move!
Auto-Align
VPS Avanger
even Loop Mash Fx (which is stock plugin) is blank!

iZotop Vst-3 all are in Blacklist!

i know many users has the same issue & also i know that people never give up at audiosex
Any suggestion?

Thanks in advance,

 

iZotope VSTs allways show as blacklisted as they use a wrapper. Which is not blacklisted...

As for your missing GUI problems, update your graphics driver, do a system file check, (command promt as admin, sfc /scannow) maybe reinstall waves as you may be missing or have a corrupt a VB pack.

Your version of 9.5 has a dongle, yes?

 

Thank you for replay techdevil

I'm windows user and i own legit Cubase pro 8
Recently i install CB pro 9.5 trial version,
When i tried to open Cubase 9.5 at the first time i had problem and that was about NVIDIA,
that problem is solved now,
Graphic driver is update, i tried Ge-Force 8600GT and WDDM v1.1 both,

Before i install CB 9.5 everything was OK on my Cubase 8,
But after installation v 9.5 i got the same issue in Cubase 8!

i tried uninstall & reinstall FabFilter plugins and still the same issue,


My system info:
Win 7 64 - CPU i7 - 16G Memory - GP Ge-force 8600 gt

 

windows updated just few hours ago,
but i'll try again,
Let's see

 

& Yes!
Updates solved the problems,
actually that was NET framework!

Thank you Legotron

 

No problem, glad that I could help

 

what do you mean by blacklisted?

 

Cubase holds a list of plugins that fail to load or crash, this is your blacklist. If you want to try reloading the plugin you simply remove it from the blacklist. If it fails again back it goes in the blacklist. Companies like Korg and iZotope use .dlls in the vstplugins folder that do not necessarily conform to vst standards, these are by design and are blacklisted should you feel the need to choose them in the plugin selector thus causing a crash.


Good call on the .Net Logotron.

 

man. why so complicated scheme? I just want write music, I don't want to fuckaround with dat shit=)
Cubase is only DAW that practicing that shit?

Looks suspiciously and stupid. 2 in 1. One question: why they using that design? But main question: Why the fuck cubase can't fix dat??
And why you'ra talking about "plugins that fail to load or crash" and then talkink about "Korg and iZotope use .dlls in the vstplugins folder that do not necessarily conform to vst standards, these are by design" - how that related each other?

I can't understand what you're talking about dude. So I can't use Korg and Iz plugs in Cubase cuz they blacklisted, even if I'll choose them in the plugin selector they will crash?

What do you mean?

 

Dear ia,

it seems you are too angry from Cubase and techdevil also!
Relax plz!

 

Hi Hooman.Leys Could you tell me which NET framework version you installed to solve the problem? Thanks

 

Hello dear Elso

Microsoft .NET Framework 4.6.1 for Windows 7 for x64 (KB3102433)

The Microsoft .NET Framework 4.6.1 is a highly compatible, in-place update for the .NET Framework 4.5.2. After you install this update, you may have to restart your computer.

More information: (Download it here)
http://support.microsoft.com/kb/3102433

Help and Support:
http://support.microsoft.com


If you use Windows i suggest you full update,

Hope it help you

 

Last edited: Dec 11, 2017

You seem to have very little knowledge softwares and OSes, and how they work or how different they work. So just keep making music, so you won´t loose your nightsleeps. Bashing idiotic comments won´t lead anywhere. There´s probably thread for DAW wars

 

Why they just don't put all these new things on the cubase 5 design, witch is the fastest and solid version.
Also obrigate people using the windows Aero is a shame, the only thing that make windows faster than mac is that you can use that skin like win 98. Is becomes so clucky with Aero and all this new shit cubase did with this daw man. Please steinberg, fire this graphic designer and hide a new one with good taste, and also hire people that uses the daw for producing and not this bunch of hypsters that only care to appereance. This is a market for professionals.

 

I actually agree with you, Legotron, but on the other hand it's hard to blame people like that. I encounter people like that almost daily and I can quite sympathise with their "I just want to make music" and angriness, which has more of desperate tone to it.

It really is complicated to do music with a computer and thankfully, since I'm knowledgeable enough, I have no problems of this kind, but maaan it can really make me angry, too, especially when you're being creative and just want to lay down that fucking tune and something unpredictable happens...

More people should know more about computers and OSes... that's how I feel, but it is not possible and it's not always their laziness for learning to blame. [Although I always think they're just lazy to learn, but it's not always true]

Oh well, the main thing is that the issue is resolved and hopefully it will help someone else, too!

 

Thanks to Audiosex and you guys,
Alway i learn new things here and thats amazing,
Now let's Compose the Music

 

First of all, Aero is GPU-accelerated, if that affects your CPU, you´re system is seriously f´d up, maybe upgrade graphic card.
Second, Aesthetics are personal tastes, I would love to see something(art, music, design, etc.) that pleases everyone.. Funny comment anyway, since no one even talked about the looks

 

yeah in theory but not in a pratical way. I say this because the Aero is responsable for the most bugs of the new cubase. Just open cubase and take of the Aero, it will become mutch more faster and more responsable, less bugs with blank vst.
AERO is the end of cubase era

 

Honestly if you're gonna blame anyone for izotope being blacklisted you should probably blame Izotope.

They've known about it this whole time, said they were working on a fix just a day or two after Cubase 9 came out. Alas, nothing but crickets now.

I don't sweat it too much though. The VST3 versions work for me in Cubase 9/9.5 and I don't know of any good reason to use VST2 instead of VST3 in a DAW developed by the creators of VST3 who actively push that format.