I'm using since a long time an old v10 release from r2r that has both VST2 and VST3 versions. I wanted to update to newer versions of the waves bundle but I realised new version doesn't come with vst2 plugins, so a lot of my projects won't load properly.
Is there a way to only install the vst2 version from the old installer (I keep it) and the vst3 version from newer bundles?

 

I haven't tried it yet, so please be aware that the AI sometimes hallucinates.

Spoiler: Source: Grok KI

Yes, it's possible to mix VST2 from your old Waves v10 installer (which supports both formats) with VST3 from newer bundles (v15+), but it requires some manual steps and careful management to avoid conflicts. Waves plugins use a "WaveShell" wrapper system, where individual plugin files (.dll or equivalents) live in a central Waves folder, and the shells (e.g., WaveShell-VST 10.0.dll for VST2) act as gateways in your DAW's plugin folders. The key is installing specific shells and ensuring your DAW scans the right paths without overwriting.

This approach assumes you're on Windows (common for VST2 discussions; if on Mac, paths differ slightly—let me know for adjustments). It also works best if your old v10 installer is an offline .exe (R2R cracks often are). Newer installs use Waves Central, which handles VST3 by default in v15+ (no VST2 option). Note: Upgrading a plugin via Waves Central can delete old shells, so avoid that for v10 plugins you want to keep.

Step 1: Prepare Your System

• Backup everything: Copy your current Waves folders (e.g., C:\Program Files (x86)\Waves\Plug-Ins V10 and shells) and your DAW projects. Also note your DAW's VST2/VST3 scan paths (e.g., in Reaper: Options > Preferences > Plug-ins > VST).
• Uninstall conflicting Waves versions if needed: If you have partial new installs, use Waves Central > Install Products > Uninstall to remove them cleanly. This prevents shell mismatches.
• Disable auto-updates in your DAW: Turn off plugin scanning on launch to avoid crashes during setup.

Step 2: Install Only VST2 from Your Old v10 Installer
Your v10 installer should place VST2 shells by default, but you can control it to avoid VST3 if desired.

1. Run the v10 installer as administrator.
2. During setup:
   • Select only the plugins/bundles you need VST2 for (don't install everything to save space).
   • Choose VST format when prompted (it may ask for VST, VST3, AU, AAX—uncheck VST3 and others if possible; some old installers default to both but allow deselection).
   • Set the install path to the default: C:\Program Files\VSTPlugins (for VST2 shells). This is fixed for v10—don't use a custom path initially.
   • For the plugin files themselves: They'll go to C:\Program Files (x86)\Waves\Plug-Ins V10 (or similar). Keep this separate from new versions.
3. After install:
   • Verify VST2 shells in C:\Program Files\VSTPlugins (look for WaveShell-VST 10.0_x64.dll or similar).
   • If VST3 shells appeared (e.g., in C:\Program Files\Common Files\VST3), delete them manually from that folder to "only VST2."
   • Rescan VST2 plugins in your DAW. Old projects should now load the v10 VST2 versions.

If the installer forces both formats, just delete the VST3 shells post-install as above. This keeps v10 isolated.

Step 3: Install Only VST3 from Newer Bundles
Newer versions (v15+) via Waves Central only install VST3 anyway, so this is straightforward.

1. Download/update Waves Central from waves.com/downloads.
2. Log in and go to Install Products > My Products.
3. Select the newer versions of plugins/bundles you want (e.g., v15+ equivalents of your v10 ones).
4. In the install options (bottom panel):
   • Check VST3 (it's usually pre-checked; uncheck VST if shown, but it won't be in v15+).
   • Uncheck other formats (AAX, AU) if not needed.
   • Install to defaults: VST3 shells go to C:\Program Files\Common Files\VST3 (e.g., WaveShell-VST 15.0.vst3).
   • Plugin files go to C:\Program Files (x86)\Waves\Plug-Ins V15 (separate from v10).
5. After install:
   • Verify in C:\Program Files\Common Files\VST3 (no VST2 here).
   • Rescan VST3 in your DAW.

Step 4: Make It Work Together in Your DAW

• Add both paths: In your DAW (e.g., Reaper, Ableton), add both VST2 (C:\Program Files\VSTPlugins) and VST3 (C:\Program Files\Common Files\VST3) to the scan paths.
• Test loading:
  • Open an old project: It should pull v10 VST2 shells (from the old path).
  • Open a new project: Use v15+ VST3 shells.
  • If a plugin name conflicts (e.g., both v10 and v15 "CLA-2A"), your DAW may prioritize one—rename shells temporarily (e.g., add "_v10" to the filename) or use the DAW's plugin manager to alias them.
• For custom VST folders (if you use one): Waves doesn't support custom paths natively, but you can manually copy shells:
  • VST2: Copy WaveShell-VST 10.0_x64.dll from C:\Program Files\VSTPlugins to your custom VST2 folder.
  • VST3: Copy WaveShell-VST 15.0.vst3 from C:\Program Files\Common Files\VST3 to your custom VST3 folder.
  • Rescan. See Waves' guide for details.

Potential Issues & Fixes


Issue Cause Fix
Old projects won't load DAW can't find VST2 shells Ensure v10 installer completed; manually copy shells to DAW path; rescan VST2 only.
New projects missing features VST3 not scanned Add VST3 path; some DAWs (e.g., older Ableton) need VST3 enabled in prefs.
Shell conflicts/crashes Same plugin name in both versions Install only overlapping plugins in one version; or manually rename shells (e.g., "WaveShell-VST10"). Avoid upgrading shared plugins in Central.
Licensing (if legit) R2R v10 may not activate on new Central This works for cracked installs; if legit, use Central's "Install Legacy Versions" for v10 (select v10 in top-right dropdown).
DAW-specific bugs E.g., Ableton Live 12 may not auto-migrate Open old projects on a secondary machine with full v10, then export stems or manually replace with VST3 equivalents.

Recommendations

• Long-term: Migrate old projects to VST3 manually (open in DAW, replace Waves instances, copy settings via plugin menus). VST2 is deprecated (Steinberg dropped support in 2023), and v15+ drops it entirely for efficiency.
• Alternatives if stuck: Tools like Shell2VST (free utility) can wrap VST3 into VST2 shells for compatibility, but it's hacky and may cause glitches.
• Resources: Check Waves' legacy install guide (waves.com/support/how-to-install-waves-legacy-versions) or forums for your DAW.

This setup has worked for many users mixing versions (e.g., v12 VST2 + v15 VST3). If you hit snags (e.g., specific DAW or error), share details for tweaks!

Concerning the company Waves, since when and since which version do they no longer release VST2 plugins but only VST3 plugins?

Spoiler: Source: Grok KI

Waves Audio's Transition from VST2 to VST3 Plugins
Waves Audio (the Israeli company specializing in audio plugins) discontinued support for the VST2 plugin format with the release of Waves V13 in October 2021. Starting with this version, they no longer release or install VST2 versions of their plugins, providing only VST3 formats for new installations and updates. This change was driven by the industry-wide shift to VST3, which offers better performance, scalability, and features like per-sample automation.

Key Details:

• Pre-V13 (e.g., V12 and earlier): Both VST2 and VST3 formats were released and installed by default.
• V13 onward: VST2 is not included in new releases. Users upgrading to V13 lose access to VST2 unless they maintain a separate installation of an older version (e.g., V12).
• Later Versions (V14, V15, V16): VST2 support was explicitly removed starting with V15, but the full discontinuation began at V13. Waves now recommends migrating old sessions to VST3 and provides tools for preset and automation transfer.

If you're working with legacy projects, Waves Central allows installing older versions (like V12) alongside newer ones for VST2 compatibility, but this requires the Waves Update Plan (WUP) for access to previous versions.

For official confirmation, see Waves' support documentation on custom VST folders, which notes the VST2 deprecation, and user reports from the time of the V13 launch.

 

Last edited: Sep 29, 2025