Hey, i need help because i just bought 2 plugins and i installed and activated them in the waves central app but now FL Studio can not find them anywhere. I already located them in the following folder (C:\Program Files(x86)\Waves) but all plugins seem to be .bundle files and i dont know what to do. I already put the file path into FL Studio for it to scan for the plugins but it does not find anything. Is there a way i can get the plugins as a .vst3 file because i can only find .dll files inside the folders.
How can i make FL Studio find my Plugins, please help!
Thank You!
I already solved the problem thank you
1 Like
Hi @aaron.thomas55,
Welcome to the Waves Forum.
The rescan steps from the next article usually do the trick.
The most common mistake is adding wrong paths for FL to rescan which might lead to even bigger issues.
If you still need any technical assistance please Contact Technical Support directly, they will make sure everything Waves-related works as expected.
1 Like
Could u please help me,im experiencing the same issue
Hi, My plugins say they are installed and activated but i cannot locate them anywhere on my PC or in FL Studio. Please help me before i have to request a refund
Hey @higginsshane11,
Welcome to the Waves Forum.
If the rescan article steps available in this thread did not work, please Contact Technical Support directly to get quick assistance with solving that, they will gladly help out.
Had the same issue but figured out.. if you use FL make shure you enable RESCAN PREVIOUSLY VERIFIED PLUGINS… And i added also the path C:\Program Files (x86)\Waves\Plug-Ins V16 you may want to change it to your version but after that it worked…. Make also shure you have these paths ….C:\Program Files\Common Files\VST3 ; C:\Program Files (x86)\Common Files\VST3
Had this same headache last week! The trick for FL Studio is to go into the Plugin Manager and make sure you check ‘Rescan previously verified plugins’ and ‘Verify plugins.’ Waves uses those ‘WaveShell’ files, and FL needs a deep scan to actually ‘unpack’ them into individual plugins. Usually fixes it right away!