Hello, randomly when i load a plugin or i recall one previously loaded they get black and make cubase 10 crash.
Anyone else having that issue?
not sure what you mean.
i encountered by loading 9.5 project that the insert slots show the plugin, but are grey/inactive. they can not be activated or removed. often combined with not being able to use any other insert on that track. have to create new track and move manually everything on that new track and restore all settings for that track.
Same problem here. The program crashes when loading several plugins or VST instruments.
All 64 bit.
Same thing (crash) when I load Cubase 9.5 projects containing any of those “problematic” plugins or VSTs.
Any ideas? It is really annoying, still working with 9.5 cause most of my chain presets include one of the previously mentioned plugins.
Same problem here. The program crashes when oppening a loaded Waves plugin in 64 bit. they get black and make cubase 10 crash.
Get it with all wave V9 plugins on my Macs. Im only using VST3 64bit but none will remain stable they open OK and are usable when first inserted but if you close and reopen you get a black plugin GUI and any subsequent plugin clicks instantly crashes Cubase 10 with no crash log written.
This appears to not happen to V9 wave plug users if their Waveshell.vst file is above v9.2.
All work fine in C9.5 so something in the new plugin code in C10 is causing this.
Cheers
David
+++1 yes Dave! same problem!
Same here!
Possibly a duplicate of the following issue: Computer für Audioanwendungen - WaveLab - Steinberg Forums
+1 Happens to me too! C10 is completely unusable for now… 
for what it’s worth, I was having the exact same issues in C 10, around half of the time that I would open up a waves plugin, it would be black, and next move was a cubase crash. I’ve just updated to the latest C 10.0.15, and i’ve been trying to replicate the issue, and waves is working completely as it should. I know it wasn’t listed specifically as one of the bug fixes, but something that they’ve done has resolved the issue, at least on my machine.
Same here, C10 - Yosemite 10.10.2
Same problem for me! Cubase 10 is still unusable!
Even just upgraded to 10.0.15 - no improvement for me
No words from Steinberg regarding this issue yet?
Anyone found a solution?
Just paid up for my first ever full version of Cubase and I’m disappointed, to say the least.
+2 Dave - same issue here. Here is what Waves had to say about it:
"Thank you for contacting Waves Tech Support.
We are currently working on making StudioRack compatible with Cubase 10. However, there’s no ETA at the moment.
Let me know if I can help with anything else.
Best Regards,
ZIV SHOR
Tech Support Representative"
I confirm this problem.
In my case it appears on the computer with the latest Windows 10 with two screens. When you open a plug-in (for example, Waves) in one screen it works fine, but when you move plug-in to another screen the next time you open it plug-in becomes black and crashes Cubase. This actual for both Cubase Pro 10 and Cubase Pro 9. I always start Cubase as administrator.
There is no such problem on another my computer with Windows 7 and two monitors. But today Windows 10 must be installed on new computers and Cubase must run correctly. Please fix this bug!
Same issue here. As Serge123 said it seems to be a problem with multiple monitors. I have the mixer on the 2nd monitor, the arrangement on the main monitor. When I open a Waves plugin on the main monitor, everything is fine, but when I open it on the 2nd (mixer) it gets black and Cubase crashes. I have this issue since many Cubase versions. I just try to avoid moving Waves-Plugin windows to my 2nd monitor. If it happens anyway I just restart Cubase with only one monitor…
I just don’t understand why it is so hard to make it work… I talked to Waves, they’ve sent me a list of supported monitors (mine is on the list) and as always Steinberg does not really care… whatever… For me this only happens with Waves plugins. I’m on Win10 64 with Cubase 10.0.30. Just tested… still crashes, haha.
Hi there, just got cubase 10, and having the same problem with the Waves pluf crashing Cubase everytime.
Do you guys know if its a waves V9 problem? same with the V10?
Still no solution i guess?
cheers
Neil
Hi everyone,
I’d be happy if this could be a kind of solution:
in the top left corner of a Waves plugin there is a Functions Menu. Just click on it and select the last line - Switch To Generic Editor.
Works in Mojave 10.14.5. + Cubase Pro 10.0.30. + Waves 9 plugins
If you can’t live without Waves Plugins - this is the temporary “solution” until Steinberg really fix it.
Of course this is not the right way to buy that expensive software and do that kind of tricks, it’s neither comfortable nor nice looking but it works somehow without killing your work… at least maybe this is the hint for Steinberg people to find the reason of the crash.
P.S. I’ve read PDF Cubase Manual page by page (as well as YouTube). It’s pretty difficult to find any mention of Generic Editor, as well as the detailed description of Functions Menu. Seems no one doesn’t use that Functions Menu?..
P.P.S. Waves are working in my Cubase Elements 7 without crashing - Mojave 10.14.5. + Cubase Elements 7 + Waves 9 plugins. So does it in Reaper.
Wanna to check have this issues been solves in Cubase 10.5 the latest versionn just release ?
I have this issue now since updating to 10.5. All Waves plugins GUI’s are blacked out. (They’re not crashing though). I have to switch to the generic editor view in order to keep working
Had no such problems in 10