Hi, I’ve been using Waves SSL 4000 Collection plugin since december 2022 and it worked fine. Knowing it is not yet compatible with Cubase 13, I’m now using Cubase 12. But once the plugin is activated /selected (insert), somehow the popup pannel of the plugin is white.
The technicians from Wave thought there was an issue with the driver of the graphic card, but today I tried it out in Cubase 11 and it all works fine.
Has anybody experienced this too and found a solution? (Using Cubase 11 is one of them, but I’d prefer to use Cubase 12 at least.
Thank you for your insight! Marielene
Which plugin specifically? Or is it all of them?
What version of the plugin(s)?
Waves doesn’t officially support Cubase 13 yet, but all the plugins I’ve used with Cubase 13 (currently on 13.040) have worked as expected. I just tried loading each of the plugins in that collection, both mono and stereo, in my current project, and each one did initially flash a white UI content before painting the channel (or compressor) screen.
FWIW, my system is Windows 10, and graphics card is NVidia GeForce GT 640 (a fairly old one).
1 Like
Thanks for your reaction. In my case the panel of each plugin of the collection shows fine in Cubase 11. In Version 12 & 13 they stay white. I have a NVIDIA GeForce GT 230
The SSL 4000 collection, all have the same issue. The latest version V14.0.0.
Just looked up the GT 230 graphics card, and I notice it only has 512 MB of RAM on it, compared to my GT 640, which has 2 GB. I wonder if that’s the issue? While the plugins would be the same, it may be that Cubase 12 and 13 are somehow adding to the requirements in this area compared to 11?
The GT 640 apparently came out in 2012 – so 12 years ago – and the GT 230 in 2009 – so 15 years ago. I do know mine can be a limitation in some areas (e.g. current Photoshop complains about its not supporting a high enough DirectX level, though it does work okay – I think some features either don’t or have to be configured not to use hardware acceleration). Might be worth considering replacing your graphics card if you can afford it. (Unfortunately, I can’t, or I already would have.)
1 Like
Hi
What puzzles me is that I’ve been using these plugins in Cubase 12 without any issue… Does this version of SSL4000 Collection maybe need more resources?
In the worst case I’ll buy another graphic card, but I really want to be sure there no other solution.
Maybe I misunderstood something above. I thought you indicated the plugin interfaces stayed white in Cubase 12, too, but had worked in Cubase 11.
As I indicated above, I’ve been using these plugins (fully updated all along) with no issue on Cubase 12 and 13 (probably earlier versions, too – I don’t recall when the EV2 version came out, but I’d been using the rest of the collection prior to adding that, but started using the channel strips a bit more with EV2). But, if they are working for you on Cubase 11, but not Cubase 12 or 13, or using them fine on Cubase 12 but not 13, that would suggest there is something in the newer version(s) of Cubase that is doing something that affects this, and perhaps that something does put more demand on the graphics card?
Just looking at the system requirements for Cubase 13, I see it says the minimum is a graphics card with native Windows 10 support. I’m not sure what the “native” implies – maybe just a driver that works with Windows 10? – but Windows 10 wasn’t around when either of our graphics cards came out (I think I bought mine when the latest was Windows 8.1). I also see the recommendation is AMD R or RX series and later or NVIDIA Series 700 and later, which neither of ours meets. Unfortunately, I’m not finding equivalent requirements for Cubase 11 or 12 for comparison.
1 Like
As wasn’t sure, I hadn’t specified it had worked under Cubase 12. So I looked it up at what moment I upgraded from 11 to 12 and and I know now I’ve been using the SSL 4000 in Cubase 11 & 12.
And you’re right, I haven’t been able to find the requirements for the versions 11 and 12 either on the Steinberg site.
Anyway, after your post I’ve been looking into graphic cards and the multimedia cards like the NVIDIA 700 series (under 100 €) are not that expensive, so I ordered one and hopefully all will work normally.
Good luck. Please let us know if that ends up making the difference.
I’d also be curious if it makes a difference in other areas of Cubase performance as I have noticed some areas of decidedly more pronounced issues in Cubase 13 versus Cubase 12, especially as regards sample buffers/latency settings when regarding tracking audio (vocals only for me as most of my tracks are VST instruments), but possibly having to freeze or render earlier than I used to, as well. (The latter is tough to be sure on as every project is different, but tracking vocals is one consistent thing in my workflow.) My son has been talking about giving me his old NVidia GTX 1050, which would definitely address Photoshop’s one complaint about DirectX versions, since he replaced his video card with a significantly higher end one (he’s a gamer). But last time I saw him he couldn’t figure out where he put the old card, so who knows if/when that will happen. I’m eager to see if it makes a difference on the Cubase front if it eventually arrives, though.
1 Like
I will keep you updated. I’m a Photoshop, Capture One user too 
On the whole I was quite frustrated with Cubase 13, maybe things will be smoother with another, more recent graphic card.
On the other hand a technician from Waves is still continuing trying to figure out the issues with the plugins, so maybe something interesting will come up from his side.
A good few years ago (maybe 9 or 10) I also had graphic issues with Waves (after a certain number of instances all the interfaces were plain white. Remove one, and all was well again). An upgraded GPU solved the issue. I think the GPU, for some plugins, does make a difference. Trouble is, figuring out which.
1 Like
I hope that upgrading the GPU will bring the solution. The excellent technician from Waves indicated me from the start it could come from the graphic card or the driver but he checked all the other possibilities anyway.
So let’s hope this one will do the trick : Gigabyte GT 1030 Low Profile D4 2G
Hi,
I’m using Cubase 13 Pro and yesterday I had the same issue with Waves SSLG-Master Buss Compressor (the only Waves plugin I have).
Popup pannel of the plugin was white and I had to restart Cubase (reloading the plugin only didn’t work) for a return to normal…
Very annoying !
I had already had this problem with older versions of Cubase 13 but I thought it had been resolved… Apparently not.
My CPU is a Intel I5 12500 and I use the integrated GPU (drivers updated).
1 Like
In the current configuration of my PC with an old NVIDIA graphic card, Waves plugins works smoothly in Cubase 11, but not in V.12 & V.13.
It works with all versions when deactivating the NVIDIA card and use the intergrated Windows GPU, but it doesn’t allow two screens.
So I’m waiting to test out a more recent GPU this week.
With another GUI installed ( Nividia GeForce Gigabyte GT 1030 Low Profile D4 2G) the display of the SSL 4000 plugins is fine now.
There’s just the pannel Media (on the right) under FX VST , that doesn’t display the the “preview” of the waves plugins at all.
I still can’t explain why I was able to use these plugins without any problem in Cubase 12 last year .
Here is a copy of different things the Waves technicians suggested me to do:
What I recommend to verify is:
- Make sure the latest drivers for the card are installed - GeForce 342.01 Driver | 342.01 | Windows 10 64-bit | NVIDIA (these were released in 2016 so I am not sure if they are available for your system)
- Disable HiDPI for Cubase -
- Right-click on the DAW’s exe file
- Go to Properties > Compatibility > Change settings for all users > Change high DPI settings > Uncheck both checkboxes.
- If already unchecked, check them and see if the issue persists.
- try changing the settings below on Nvidia’s Control Panel (if haven’t done so yet).
1. Under 3D Settings > Manage 3D Settings:
- Threaded Optimization – off.
-
- Vertical sync – off.
-
- Power Management – set to Prefer Maximum Performance
Furthermore, you can try rolling back to V13, following the article below, and see if that helps:
How to Roll Back to Waves V13
2 Likes
You have to use the little camera button in the top part of the plugin window to capture the thumbnail graphics for the VST panel in Cubase’s Media Bay. That is the same for any third party plugins where you haven’t already captured those.
1 Like
Hm… could you send me a screen shot, I don’t see a camera icon, but I’m sure I’m looking in the wrong place
Thanks!