I installed the Waves plugin, which I've used countless times before. I've never had this problem before. I'm using the "Waves.Complete.v2022.09.12.Incl.Emulator-R2R" v14 version. The plugins appear, but there's no sound. I've cleared the registry entries and reinstalled them several times, and I've looked at various forums for issues people have experienced, but the problem persists.

Additionally, when I use the script "R2R_Kill_Waves_Background_Process" I get a "Not Found" error.

edit: I solved it. Okay, now I'm going to tell you about a method I've tried that's funny but works. After deleting and reinstalling the program several times, I installed it in a different folder instead of the one I installed it in. And it worked. So, I installed it in the c/vst plugin folder instead of the c/vst plugin/waves folder, and it worked.

 

Last edited: Jul 28, 2025 at 12:19 AM

Hey, first back up your files, then you should completely delete Waves, follow the attached instructions, restart your PC, and reinstall R2R according to the instructions in the enclosed NFO. (P.S.: It's usually old file remnants that cause problems.)

Waves Complete - R2R

Uninstall / Clean Up
----------------------------------------------------------------------------------------------------
Run included "R2R_Kill_Waves_Background_Process.cmd".
Uninstall previous release.
Uninstall Waves Central.

Clean Paths:
Your VST2, VST3, AAX plugins dir
C:\Program Files (x86)\Waves\
%PROGRAMFILES%\Waves Central\
%PROGRAMDATA%\Waves Audio\
%APPDATA%\Waves Audio\
%LOCALAPPDATA%\Waves Audio\
%PUBLIC%\Waves Audio\

=> If you think you are not experienced, search "WaveShell*" in your C drive, then delete all.
=> We always see people having problem with old shells which should be uninstalled before.

Clean Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Waves\

Install Runtimes
----------------------------------------------------------------------------------------------------
If you use SoundGrid, install/update SoundGrid drivers.
Google "Microsoft Visual C++ Redistributable", download from Microsoft and install/update :
Microsoft Visual C++ Redistributable 2012 x86 and x64
Microsoft Visual C++ Redistributable 2013 x64
Microsoft Visual C++ Redistributable 2015-2022 x64

Install Waves
----------------------------------------------------------------------------------------------------
Run our setup and install.

Scan or rescan plugins from your DAW.
If you use sample based instruments, locate the instruments path from application start up or GUI.
Sample Libraries Releases (currently, most can be also downloaded from Waves official) :

Waves.Bass.Fingers.Library.HD.v1.0-R2R
Waves.Bass.Fingers.Library.SD.v1.0-R2R
Waves.Bass.Slapper.Library.HAPPY.NEW.YEAR-R2R
Waves.Clavinet.Library-R2R
Waves.Electric.88.Library-R2R
Waves.Electric.200.Library-R2R
Waves.Electric.G80.Library-R2R
Waves.Grand.Rhapsody.Library.HD.v1.0-R2R
Waves.Grand.Rhapsody.Library.SD.v1.0-R2R
Waves.Sample.Libraries.Factory.Pack.v1.0.3.5-R2R (CR8 Sampler asks for this)
Restarting Background Waves Servers
----------------------------------------------------------------------------------------------------
This is useful when background process are doing something wrong.
When background servers are not working correctly, following issue happens.

* Plugin scan fails (WaveShell return 0 plugins)
* Preset Browser does not works
* COSMOS (also in CR8 Sampler browser) does not launch, or exits with no license error

Run included "R2R_Kill_Waves_Background_Process.cmd".
Run these EXE manually.

"%PROGRAMDATA%\Waves Audio\WavesLocalServer\WavesLocalServer.bundle\Contents\Win64\WavesLocalServer.exe"
"%PROGRAMDATA%\Waves Audio\WavesPluginServer\WavesPluginServerV13.1.bundle\Contents\Win64\WavesPluginServer.exe"

=> Basically, those EXE will be started when it is neeeded.
=> However, our testers found that COSMOS fails starting them on some computers.
=> It leads COSMOS getting stuck at startup.
----------------------------------------------------------------------------------------------------
TEAM R2R

 

I already did this several times, too. still now working.

Ableton sees the waves plugins but converts them to midi channels no matter which Waves plugin I open

 

Hello @jointhelargestx, I don't know, so I entered your question/problem into the AI, I hope the AI can help you solve the problem.

Spoiler: Source: Grok KI

It sounds like you're experiencing an issue where Ableton Live is unexpectedly converting audio tracks with Waves plugins to MIDI channels, or there's a misunderstanding about how Waves plugins are interacting with MIDI in your setup. This could stem from several possible causes, including plugin compatibility, routing issues, or user error in the workflow. Below, I’ll outline potential reasons and solutions based on the context and available information.

Understanding the Issue
From your description, it seems that when you load a Waves plugin on an audio track in Ableton Live, the track or the plugin's output is being interpreted as MIDI data, or a MIDI track is being created/used in a way you didn’t intend. This is unusual because most Waves plugins (e.g., EQs, compressors, reverbs) are audio processors and don’t inherently generate or interact with MIDI unless specifically designed to do so (e.g., Waves Tune Real-Time or OVox). The search results suggest some known issues with Waves plugins in Ableton, particularly with MIDI routing or plugin detection, which we can use to troubleshoot.

Potential Causes and Solutions

1. Waves Plugin MIDI Output Behavior
   • Cause: Some Waves plugins, like Waves Tune Real-Time or OVox, can generate MIDI output. For example, Waves OVox can convert vocal input to MIDI notes if its MIDI Out feature is enabled. If you’re using such a plugin and have MIDI routing set up, Ableton might be creating or routing to a MIDI track to capture this output.
   • Solution:
     • Check the plugin settings. For instance, in OVox, go to the “Synth Settings” tab and ensure “MIDI OUT” is turned off unless you intentionally want MIDI output.
     • If using Waves Tune Real-Time, verify that the “Target Pitch” button is not enabled unless you’re deliberately routing MIDI to another track.
     • If you don’t want MIDI, ensure the plugin is processing audio only and that no MIDI routing is set up in Ableton’s I/O section.
2. Incorrect Track Type or Routing
   • Cause: You might be accidentally loading Waves plugins onto a MIDI track instead of an audio track, or the track’s input/output settings could be misconfigured to route to a MIDI channel. Ableton’s MIDI tracks are designed to handle MIDI data, and some plugins might appear to “convert” to MIDI if placed incorrectly.
   • Solution:
     • Confirm you’re loading the Waves plugin on an audio track, not a MIDI track. Audio tracks process audio signals, while MIDI tracks expect MIDI data and instruments.
     • Check the track’s I/O settings:
       • In the “MIDI From” or “Audio From” chooser, ensure the track isn’t inadvertently receiving MIDI input from another track or plugin.
       • Set the “Monitor” to “Off” or “Auto” unless you’re specifically monitoring an external input.
     • If a MIDI track is involved, verify that it’s not set to receive MIDI from the audio track with the Waves plugin. You can check this in the MIDI track’s “MIDI From” dropdown.
3. Waves Plugin Compatibility Issues
   • Cause: Waves plugins, especially older versions (e.g., V9, V10, or V12), have known compatibility issues with certain versions of Ableton Live (e.g., Live 11 or 12). This can cause unexpected behavior, such as plugins not loading correctly or interfering with track functionality.
   • Solution:
     • Ensure your Waves plugins are updated to the latest version compatible with your Ableton Live version. Use Waves Central to update plugins to V14 or V15, as older versions (e.g., V12) may not work properly with newer Ableton builds.
     • Verify that you’re using the correct plugin format (VST2 or VST3, not AU on macOS, as Waves AU plugins are not supported in Ableton).
     • If you see multiple WaveShell files in your VST folder (e.g., WaveShell1-VST3 12.7_x64.vst3), remove duplicates and rescan plugins in Ableton (hold Alt while clicking “Rescan” in Preferences > Plugins).
4. Ableton’s Audio-to-MIDI Conversion
   • Cause: If you’re using Ableton’s “Convert to MIDI” feature (e.g., Convert Melody to New MIDI Track) on an audio track with a Waves plugin, this could explain why MIDI tracks are appearing. This feature analyzes audio and generates MIDI notes, which might be triggered accidentally.
   • Solution:
     • Ensure you’re not right-clicking the audio track and selecting “Convert Melody to New MIDI Track” or similar options unless intended.
     • If you want to process audio without MIDI conversion, work directly in the audio track and avoid using Ableton’s audio-to-MIDI tools.
5. Waves Plugin Licensing or Installation Issues
   • Cause: If Waves plugins are not properly licensed or installed, they might not function correctly, leading to unexpected behavior like incorrect track interactions. The Waves Central app can sometimes update plugins to incompatible versions.
   • Solution:
     • Open Waves Central and verify that all plugins are licensed and installed correctly.
     • If using a custom VST folder, ensure the WaveShell file is correctly placed in that folder (e.g., C:\Program Files\VSTPlugins on Windows). Do not move individual .dll files like CLA-2A.dll; only the WaveShell file should be in the custom folder.
     • Uninstall and reinstall Waves plugins via Waves Central, ensuring you select VST3 (or VST2 if needed) and the correct bit version (64-bit for modern Ableton versions).
6. Ableton MIDI Track Defaults or Automation
   • Cause: If a MIDI track is automatically loading a plugin or behaving unexpectedly, you might have a default MIDI track setting that’s causing issues. For example, a saved MIDI track default could be loading a plugin or routing MIDI incorrectly.
   • Solution:
     • Check for default MIDI track settings: Go to User Library > Defaults > Creating Tracks > MIDI Track and delete any custom defaults.
     • Reset Ableton’s preferences to default by deleting the Preferences.cfg file (back it up first) or resetting via the Options menu.
7. MIDI Routing Limitations in Ableton
   • Cause: Ableton Live has a known limitation where MIDI output from a VST plugin (like Waves Tune or OVox) is merged to MIDI channel 1 when routed internally to another track. This could cause confusion if you’re expecting multi-channel MIDI output.
   • Solution:
     • If you’re intentionally using a Waves plugin that outputs MIDI (e.g., OVox or Tune Real-Time), create a separate MIDI track to receive the MIDI output:
       • Set the MIDI track’s “MIDI From” to the audio track containing the Waves plugin.
       • Select the specific plugin in the “Input Channel” chooser.
       • Set the MIDI track’s “Monitor” to “In” to capture the MIDI.
     • Note that Ableton cannot separate multi-channel MIDI output (e.g., MIDI channels 1, 2, 3) into different tracks; all MIDI is merged to channel 1 internally. If you need multi-channel MIDI, consider using a third-party plugin like Blue Cat’s Patchwork or Bidule as a workaround.

Step-by-Step Troubleshooting
To systematically address the issue, follow these steps:

1. Identify the Plugin: Confirm which Waves plugin(s) you’re using (e.g., Waves Tune, OVox, or standard audio plugins like CLA-76). If it’s a plugin designed for MIDI output, check its MIDI settings (e.g., disable “MIDI OUT” in OVox).
2. Check Track Type: Ensure you’re loading the plugin on an audio track, not a MIDI track. Create a new audio track (Ctrl+T on Windows, Cmd+T on Mac) and drag the Waves plugin from the Plugins section in Ableton’s Browser.
3. Verify I/O Settings:
   • In the audio track’s I/O section, ensure “MIDI To” is not set to another track or plugin unless intended.
   • Check any MIDI tracks for incorrect routing from the audio track.
4. Update Plugins: Use Waves Central to update to the latest plugin version (V15 as of 2025). Ensure you’re using VST3 (or VST2 if required) and that the WaveShell file is in your custom VST folder.
5. Rescan Plugins: In Ableton’s Preferences > Plugins, hold Alt and click “Rescan” to force a full plugin scan.
6. Test with a New Project: Create a new Ableton project with a single audio track and a Waves plugin to isolate the issue. If it works correctly, the issue might be project-specific.
7. Check for MIDI Conversion: Ensure you’re not accidentally using Ableton’s “Convert to MIDI” feature on the audio track.
8. Contact Support: If the issue persists, contact Waves support (via Waves Central or their website) or Ableton support ([email protected]) with details about your setup (Ableton version, Waves plugin version, OS, plugin format).

Additional Notes

• Waves Plugin Management: Waves plugins use a “WaveShell” system, where individual plugins are housed under a single WaveShell file in Ableton’s Browser. When you load the WaveShell, you should see a list of available plugins (e.g., CLA-76, H-Delay). If you only see the WaveShell without plugins, it indicates a detection issue. Ensure the WaveShell file is in the correct VST folder and rescan.
• Ableton Version: Ensure you’re using a compatible version of Ableton Live (e.g., Live 11 or 12). Live 10 and earlier may have issues with newer Waves plugins.
• System Specs: Provide your OS (Windows/Mac), Ableton version, and Waves plugin version for more tailored advice if needed.
• Workaround for MIDI Output: If you’re intentionally using MIDI-generating plugins, consider using a dedicated MIDI track for each plugin instance to avoid channel merging, or explore third-party solutions like Blue Cat’s Patchwork for multi-channel MIDI routing.

If the Issue Persists
If none of the above resolves the issue, please clarify:

• Which specific Waves plugins are you using?
• What version of Ableton Live and Waves plugins are you running?
• Are you seeing MIDI tracks created automatically, or is the audio track behaving like a MIDI track?
• What is your OS (Windows/macOS) and plugin format (VST2/VST3)?

This will help narrow down the issue further. You can also check the Ableton and Waves forums for similar reports or post your issue there for community input.

 

Thanks, but I've already talked to the AI, and it made similar comments. However, I've been using the same version the same way for years. But this is the first time I've received such an error.

 

It's not installed correctly or it would not say "not found". Waves Mac installers usually have a direct command something like "kill server" and it is a step at the very end, right before rebooting. R2R did not create a script like that for fun. If it does not work, it's because files that should be there, are not there; or that script would not exist.

 

Afterwards, I placed the script in the C:\installation folder and tried that. I no longer get the "Not Found" error, but the problem still persists.

 

Do other plugins from other manufacturers work? Have you checked the plug connections?

 

Other plugins work. Only a few Waves plugins convert the audio channel to MIDI, and there is no sound. Even if I open it on the MIDI channel, there is no sound. I've been trying for hours to fix this.

 

Just close everything down and start a new project, then drag in a VST3 plugin synth! Like Codex or Elements. www.waves.com/plugins/synths#sort:path~type~order=.default-order~number~asc|views:view=grid-view|paging:currentPage=0|paging:number=18

Spoiler: Source: Grok KI

1. Waves Plugin MIDI Output Behavior
   • Cause: Some Waves plugins, like Waves Tune Real-Time or OVox, can generate MIDI output. For example, Waves OVox can convert vocal input to MIDI notes if its MIDI Out feature is enabled. If you’re using such a plugin and have MIDI routing set up, Ableton might be creating or routing to a MIDI track to capture this output.
   • Solution:
     • Check the plugin settings. For instance, in OVox, go to the “Synth Settings” tab and ensure “MIDI OUT” is turned off unless you intentionally want MIDI output.
     • If using Waves Tune Real-Time, verify that the “Target Pitch” button is not enabled unless you’re deliberately routing MIDI to another track.
     • If you don’t want MIDI, ensure the plugin is processing audio only and that no MIDI routing is set up in Ableton’s I/O section.
2. Incorrect Track Type or Routing
   • Cause: You might be accidentally loading Waves plugins onto a MIDI track instead of an audio track, or the track’s input/output settings could be misconfigured to route to a MIDI channel. Ableton’s MIDI tracks are designed to handle MIDI data, and some plugins might appear to “convert” to MIDI if placed incorrectly.
   • Solution:
     • Confirm you’re loading the Waves plugin on an audio track, not a MIDI track. Audio tracks process audio signals, while MIDI tracks expect MIDI data and instruments.
     • Check the track’s I/O settings:
       • In the “MIDI From” or “Audio From” chooser, ensure the track isn’t inadvertently receiving MIDI input from another track or plugin.
       • Set the “Monitor” to “Off” or “Auto” unless you’re specifically monitoring an external input.
     • If a MIDI track is involved, verify that it’s not set to receive MIDI from the audio track with the Waves plugin. You can check this in the MIDI track’s “MIDI From” dropdown.

 

At a certain point I would remove, clean up, reboot, and then reinstall; but with all the waves files moved to the C: drive first. At some point in the install process, usually you have to copy all of the Waves content and data into the folder R2R's instructions tell you to. It won't really take any longer to move them to C: first, before beginning the install process; because it will be very fast when you move them from one location on the C: drive to the place you actually have to put them. The install process will even work faster with the Waves data all on the local system disk.

It should not take hours to install them. Also, Waves take up a very decent sized chunk of your installed plugins. You really do not want a sketchy half-baked install of them.

 

I solved it.

 

How? You should write a quick note about what you did in case someone else looks for a fix for the same issue. And mark your thread solved when you know whatever you did worked.

 

I edited the post again. Also, how do I mark it as solved?

 

oh, I think you just edit the thread title to say (Solved) or something like that.