![pro tools extremely slow after installing waves plugins pro tools extremely slow after installing waves plugins](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/24069030957/original/tO296PfCJWc4_OKOosy0RKm-bDygft5EeQ.png)
- Pro tools extremely slow after installing waves plugins upgrade#
- Pro tools extremely slow after installing waves plugins pro#
- Pro tools extremely slow after installing waves plugins software#
- Pro tools extremely slow after installing waves plugins license#
- Pro tools extremely slow after installing waves plugins windows#
Pro tools extremely slow after installing waves plugins pro#
Pro Tools has to pull all this audio from the drive, load it into RAM (of which you have very little), and play it back based on where you have your audio set to play back. And within those tracks, you could be pulling audio from hundreds of different files. You could have 32 tracks of audio set up in pro tools. The problem lies with the next point.ģ) If you're running a session off the same drive, you're dealing with pulling X number of audio files off that drive. Running Pro Tools on your C drive is perfectly fine.
Pro tools extremely slow after installing waves plugins software#
You know Pro Tools, you know that it's complicated software (especially when bundled with multiple plugins). Which means that, your computers processes (such as screen redraws, background processes and general housekeeping) are running off this drive.Ģ) Your Pro Tools software is running off the same drive. If you, like most people, have Pro Tools installed on the same drive as your operating system (the C drive), then think about it:ġ) Your operating system is running off the C drive. Running audio off the same session as your software is a bad idea.
![pro tools extremely slow after installing waves plugins pro tools extremely slow after installing waves plugins](https://cdn2.shopify.com/s/files/1/0993/3800/files/LoAir_grande.png)
Set Pro Tools to use about 80% of all four, or 99% of two like so:
Pro tools extremely slow after installing waves plugins upgrade#
If I was you, I'd upgrade to at least 2GB of RAM, or better yet, 3 or 4 (RAM is very cheap). 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.1GB of RAM - that's one major problem. 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. Once you’re at this folder, delete the folder titled: WavesLocalServer.Bundle.
Pro tools extremely slow after installing waves plugins windows#
Next, on your C drive (or D if you installed Windows there), locate the folderĬ:\ProgramData\Waves Audio\WavesLocalServer Under the Performance tab locate the Waves Server. Here’s the solution: Close out of all applications using Waves (likely your DAW). I spoke with Waves Support and we isolated the issue: Hi - I posted this in another forum - this seems to work so far though ideally it’s not a complete solution:ġ1-28-21 An interim solution has been found with Waves loading slowly. I should also note that if you are having the slow loading plugins issue, because of the hardware inventory process, it could be another piece of USB or other hardware and if it is not the SD reader you should systematically remove/add other hardware to see if that is the issue. These were associated with two “Generic MassStorageClass USB Device” under “Disk drives” in Device Manager. One clue was I had two phantom disk drives (and drive letters) that never disappeared even though no USB drives/sticks were connected. I guess this is the first time I’ve had an SD card sitting in the reader while using Studio One. Weird thing is I’ve had this SD carder for over a year and never had a problem. Unplugging the SD card reader fixed everything. Also disk manager took forever to load getting stuck at “connecting to virtual disk service”. Windows Explorer was very slow and my computer in general seemed to get stuck every once in a while. Other symptoms of this issue were my computer was taking an extra long time to start/restart. This is not an issue with the DAW so this issue/solution is not unique to Studio One and should work on other DAWs. My guess is this SD card reader issue was causing that hardware inventory process to fail.
Pro tools extremely slow after installing waves plugins license#
Every time you use the plugin they take a hardware inventory to makes sure the license is on the right computer. Simplified explanation: Waves and other plugin manufactures use your hardware configuration to build a unique key for your computer to keep track of the license. Google - “TechNet disk-id collisions with empty card-reader” Long story short is was my SD card reader! I had inserted an SD card (which I don’t use very often) and it was causing this issue:
![pro tools extremely slow after installing waves plugins pro tools extremely slow after installing waves plugins](https://img.wavescdn.com/1lib/images/products/plugins/full/scheps-omni-channel.jpg)
After two days I’ve finally figured this out. I tried uninstalling and reinstalling all my plugins and the DAW and different versions of the DAW. Waves plugins seemed to be the worst but Plugin Alliance was also slow. Loading projects that normally took seconds to load started taking 20+ minutes always getting stuck at loading the plugins. Everything was working great and then one day it all stops. Mainly use Waves, SoundToys, Plugin Alliance, and Fab Filter EQ. I run Studio One 5.x with 100+ plugins on Windows 10. Posting this to several threads because lots of people seem to have different forms of this issue and I want to spread the word on what worked for me.