The V10 (Version 10) bundle was a major release from Waves. If you have the "complete content" for this version, it typically includes over 160 plugins , categorized into several key areas: Signature Series:
: The "WaveShell" acts as a bridge or wrapper.
: The WaveShell then scans a separate internal directory containing the actual Waves plugin data and communicates those processors back to your DAW. vst plugin waveshell1-vst3 10.0-x64 -vst3-
: /Library/Audio/Plug-Ins/Components (for AU) or /Library/Audio/Plug-Ins/VST3 Why the Waveshell System Causes DAW Issues
: Running a mix of Waves V9, V10, and V14 plugins can confuse the DAW scan. The V10 (Version 10) bundle was a major release from Waves
Rather than installing individual Virtual Studio Technology (VST) files for every separate processor—such as the Renaissance Equalizer, CLA-2A, or L2 Limiter—Waves routes its entire ecosystem through a unified master gateway file called a . Understanding this architecture is vital for maintaining project recall, optimizing CPU performance, and troubleshooting DAW scanning failures. 🛠️ What is the WaveShell Architecture?
: C:\Program Data\Waves Audio macOS Systems 🛠️ What is the WaveShell Architecture
After this, you can launch your DAW, and it should automatically find the WaveShell file. However, you might need to do a manual plugin scan.
Go to Finder > Go > Go to Folder , type ~/Library/Preferences/Waves Audio , and delete the Cache folder. Step 3: Run Waves Central Repair