Opening Fruity Wrapper... 50 seconds later... waves plugin loads up. Same with the next i load up or open, or any and all projects. Was wondering if doing a clean install of all waves products would help or is this just simply how waves works?

Ironically, All my waves plugins work fine, i have everything saved to my SSD, but the loading times atrocious. If anyone has any general advice, or maybe could point me in the direction of a clean install with very fast load times for all waves plugins, it'd be appreciated beyond measure.

I know most here can live without waves plugins.... as I should as well. But I love using mondomod for movement of anything in most tracks, and I use waves R BASS and the compressors. I'd love to hear some alternatives to the plugins aforementioned.

But the primary reason is, most music studios utilize waves... so it's sadly needed. Much like Kontakt with it's godawful ancient UI and convoluted system, its become "industry standard".

 

SOLVED: Waves plugins very slow to load
https://forum.waves.com/t/solved-waves-plugins-very-slow-to-load/3536

SOLVED: Waves plugins very slow to load
https://forum.waves.com/t/solved-waves-plugins-very-slow-to-load/3536?page=2

Waves plug-ins slow to load
Waves uses OpenGL to draw their graphics. I'm no expert in this area, but I do know I used to have some graphics card that only went as high as OpenGL 2.0 and Waves require 2.1. The graphics worked - just - but were slow and laggy and froze sometimes. I replaced the card with one that supported the latest OpenGL version and my Waves plugins have worked perfectly ever since. Strangely, it also fixed problems with SKNote plugins where the meters would just stop working, even though they don't use OpenGL. Anyway, my guess is graphics drivers, especially OpenGL.

The DSP load is also very high if this Waves plugins are opened?
I've reported some of this bugs to Waves in combination with a the on-board GPU of the i7 and Cubase.
IMO they using some OpenGL functions which are not supported by every GPU (or the driver) and so it must be emulated by software. So it needs a lot of processing power and the result is the slow GUI.

www.kvraudio.com/forum/viewtopic.php?t=488802

The bottom line is that OpenGL plugins will always try to run their OpenGL code on your graphics card - BUT - if the plugin requests a feature which isn't supported by your card, OpenGL will bomb out and pass control to your computer's CPU (rather than the card's GPU). This will be very demanding on your CPU. So if you use too many OpenGL plugins (or if the host DAW also needs a lot of CPU time) they'll all be fighting for the CPU's attention and that's why you get poor performance.

I tested several OpenGL plugins and many ran perfectly but many didn't. So this is clearly a workable technology - but it's a long way from being perfect. And for audio plugins, too many manufacturers don't seem to understand that it needs to be used with care

Waves again and again --> https://forum.harrisonconsoles.com/thread-8403-post-47172.html

See the attached photo:
In my testing, Waves plugins were far & away the worst performers - so as Tassy said, it's high time we all rattled Waves's cage and simply embarrass them into finally getting this fixed!!
www.kvraudio.com/forum/viewtopic.php?t=488802&start=30&sid=cbbd837ff44ce4365a76574bd4c98ebd

Waves plugins and opengl
https://audiosex.pro/threads/waves-plugins-and-opengl.22524/

GPU Extensions Viewer for OpenGL, Vulkan, and DirectX
https://www.realtech-vr.com/home/?page_id=142

 

Last edited: Jan 6, 2025

Here’s how to fix OpenGL errors in Windows 10
https://windowsreport.com/opengl-problems-windows-10/#1

Fix OpenGL Not Supported Error in Windows 10 [2021]

Fix Opengl not supported error in windows 10

How To Fix OpenGL Error (For old pc or no graphic card)

Spoiler: Waves --> System Requirements --> Windows

Waves --> System Requirements --> Windows

CPU: X64 compatible Intel or AMD CPU
Memory: Minimum: 8 GB RAM (16 GB recommended) / 16 GB free disk space on the system drive
Operating System: Windows 10 64 bit / Windows 11
Screen Resolution: Minimum: 1024x768 / Recommended: 1280x1024 / 1600x1024


Exceptions & Notes:

• These specs are for software version 15.
• Windows: AMD CPU support is for Ryzen 3000 Gen2 (Zen2) processors and up.
• Windows 10 64 bit (Pre-21H2) is not supported with software version 15.
• Current version licenses will activate older version software (V9 and above), if the product/s in question exists in this software version.
• To check if a plugin exists in an older version, scroll to the bottom of the older version's download page.
• Waves plugins are officially supported on up to two screens in third-party DAWs and host applications.
• Screen Resolution: SSL E-Channel, SSL G-Channel, Element, Codex, Dorrough, Flow Motion, Bass Slapper and Bass Fingers require minimum screen resolution 1280x1024 / 1600x1024. Recommended screen resolution for Flow Motion, Bass Slapper and Bass Fingers: 1920x1080.
• If you experience unusually high CPU consumption from Waves Plugins V15 and above while using a non-Intel CPU on Windows, learn how to enable MKL optimization to improve CPU performance.
• Waves Plugins and applications are supported and tested on operating systems installed on the built-in system hard drive. Operating systems installed on external hard drives are not tested and may not be fully functional with our software.
• Clarity Vx / Pro and Clarity Vx DeReverb / Pro:
  
  Mac: Intel Xeon-E processors are not supported
  Windows:
  • Intel Xeon processors are not supported
  • Supported on Intel processors Gen 6 and above
  • AMD processors lower than Ryzen 9 are not supported
• COSMOS Sample Finder, StudioVerse Audio Effects & Instruments, Key Detector: Intel processors must be Gen 5 or above and support AVX.
• Waves Instruments: Additional disk-space may be required for sample libraries. Specific information available on each instrument’s page.
• RAM: Grand Rhapsody’s & Bass Finger’s minimal RAM required is 16 GB (and not 8GB, as generally described for all plugins). [Mac & Windows].

https://www.waves.com/support/tech-specs/system-requirements#plugins|version-15

 

Last edited: Jan 6, 2025

After reading some on the links @Radio supplied, this seems it might be of particular interest:
====================
https://forum.waves.com/t/solved-waves-plugins-very-slow-to-load/3536/6
Rev
Dec 2021
Hi - I posted this in another forum - this seems to work so far though ideally it’s not a complete solution:
11-28-21 An interim solution has been found with Waves loading slowly.
I spoke with Waves Support and we isolated the issue:
it was “The Waves Local Server”.
Here’s the solution: Close out of all applications using Waves (likely your DAW).
In Windows 10, open Task Manager. Under the Performance tab locate the Waves Server. Right Click and choose End Task
Next, on your C drive (or D if you installed Windows there), locate the folder
C:\ProgramData\Waves Audio\WavesLocalServer
Once you’re at this folder, delete the folder titled: WavesLocalServer.Bundle.
Now re-open your DAW and it should be quite fast (mine went from 30 second load time to under 3 seconds) as well as any plugin by Waves - all instantaneous.
If you need to purchase other plugins via Waves Central, go ahead and do so and activate and install, then simply repeat the process above until they (Waves) develop a solution.
=====================
It seems a good amount of other people found it a fix.
-----
Another possibility is having an improper drive detected by the system.
That is, a network drive mapped to nothing ... or a drive identified but missing, etc.
Looking in Device Manager for that, and any other hardware flags...
-------
And one other thing I read about doing a "Repair":
"... I then did the simple answer of going to Waves “Repair” under the settings bar to the left in waves central. clicked repair and after 2 times opening it was extremely fast went from 2-3 minutes Literally down to 5 seconds. "
----------------------
If none of that helps, at least this bumps this thread...

 

Last edited: Jan 17, 2025

^ I'm not sure how such conclusions can be jumped to with so little information from the OP. It's Windows, FL, and Waves. No version numbers, no details about the machine, at all.

The first thing I would try to rule out would be the DAW. I would check out the load times for some of the problematic Waves plugins using the standalone version of Blue Cat Audio's Patchwork. Or I would try using the same plugins in REAPER. You could even use a Wave Editor like Audacity or any other host software application. Patchwork is great for this kind of thing.

Keep in mind, the more current a version of Waves you install, always either stays the same or becomes more bloated. They never get more optimized by a new version. Consider using an earlier release that still contains all the plugins you actually need. Firewall them all to block internet access. Block Waves.com in your hosts file. Block Waves Central the same way, or delete it if you can.

If you figure out that Waves plugins are actually working fine in other host software, then you need to drill down into your FL install and its settings, too. You are loading them inside a wrapper. Also, check to see if you have multiple plugin formats installed of Waves; like VST2 and VST3, etc.

"Lots of studios use them" is no reason to have them if they work this slowly. Otherwise, we'd all be running Protools.

 

Last edited: Jan 17, 2025