It shouldn’t really matter what shell you are running as everything Waves should be backwards compatible. It should work as long as you have identical plugins.
So perhaps the problem is FL Studio. I now its been experiencing quite few issues lately, largely because of the Visual C Redistributable file issue. Not really a Mac issue to my understanding.
It might be a problem with the plugin cache if FL Studio uses one. You could try deleting that. You could also try uninstalling and reinstalling the Waves plugins too, if you haven’t already.
My problem was that Studio One couldn’t find WaveShell1-InternalSynth-VST 12.7_x64.dll, so when I tried to open a vst presumably associated with this waveshell, I got the black gui and the error msg that there was a problem with the wave shell. I searched for the location of the wave shell on my computer and relocated to common files/VST3. Studio One was able to find (or more like read/see) the wave shell and now the plugins work. Certain file types apparently can only be read in certain folders. In this case, I put it in with the other .dlls.
I’ve found with the Waves ecosystem that its better to leave their elements where they lie as moving them tends to break any dependency links they have.
It sounds to me, though I’m no expert at this, that somehow the WavesShell1 got moved about or placed into the wrong location. If that is the case it would certainly go along way to explain why things weren’t working for you and why placing it back gets it working again.
Whenever I have to do anything with my Waves plugins related to updates, upgrades, whether with the plugins themselves or with my DAW (upgrade or update version(s) on that), I feel like I have an abusive narcissistic boyfriend who kicks my ■■■ but I stay with him because he’s handsome and I like the ■■■.
For the love of whatever ■■■ you believe in, nothing else related to audio production on my computer is so fragile like this, why must you be this way?
“I was going to record today, yeah, upgraded yesterday, let’s see what the new plugins can do… oh, well, I guess I’m going to spend hours trying to get them to work again. So much for flow.”
Under Scan options , verify that ‘Scan previously scanned plug-ins’ and ‘Re-Scan Plug-Ins with Errors’ are highlighted, if they are not, highlight them
At the top left of the window, make sure Verify Plugins is check-marked, and click on Start scan
So this managed to keep your Waves romance alive?!?
There are plugins that dont scan correctly the first time when Logic scans them. I often find I have to open up the Plugin Manager to do some sense of rescanning. I’m just not entirely sure whether this is a Waves issue or a Logic AU scan issue.
After things work again, you forget the pain and frustration, and rationalize that nothing can replace Magma BB Tubes, NLS Channel, H-Delay and H-Comp, and of course Butch Vig Vocals (Three of my tracks relied on it so much that I can’t imagine getting that sound without hours (days?) of dinking around with a stack of individual VSTs.)
Lots of Waves basket of plugins, I never, ever use. But those five pretty much are required. Yeah, I could do those five things with other plugins, but why?
“Nothing can replace you, baby, please just let’s not fight!”
Waves 4eva