Yeah it’s stuck again
Ok 
Maybe try make sure you only have one set of their DLL files in your various VST folders and also activate/register all your Waves plugins before scanning.
When that’s done remove the “CachedFailedVSTs_x64.db and CachedFailedVST3s_x64.db” in your Renoise preferences folder (In Renoise click help>Show preferences folder) and do another plugin scan.
I’ve tried this a couple times and no luck. When I tried deleting the vst2 dll shells when scanning in other DAWs instruments like bass fingers don’t appear. It isn’t working in studio one either.
Still correct in Bitwig tho.
Waves is just annoying, I’m out of ideas…
Maybe have a look in the log file for clues. Click Help>Show log file
Yeah waves is a nightmare
Thanks for the advice
I use V9, v10, v12 and v13 of their plugins but only have the x64.dll (edit: changed the number) version of the waveshells in my VST folder.
Is that for 32 bit systems?
Hope I can figure something out cuz now I can’t open Renoise.
x64 is 64bit and x86 is 32bit (i wrote it wrong earlier) but I don’t think that matter.
Try have a look at this thread
Can’t you even see the Renoise interface or does it stop at scanning plugins?
Just delete the plugin scan data C:\Users(username)\AppData\Roaming\Renoise\V3.3.2 :
CachedFailedVST3
CachedFailedVSTs
CachedVST3_x64
CachedVSTs_x64
Or any similar files in your directory. Then restart Renoise and it will rescan all the plugins from 0 (Even the failed ones in previous scans)
Crashes while scanning plugins
I’ve done this a few times, still won’t scan
Maybe there’re some clues in the log files, did you check?
https://www.renoise.com/faq/how-do-i-report-bug
I recall posting abhout this issue a few years back… try searching the forums I think it ended up working.
I feel your pain!
Not yet I’m out of the house working a lot last couple days
I’ve looked at a couple it’s just hard to understand waves. I wish they’d just drop the shells BS and install normal .VST3 files like everybody else
1 Like
Go to task manager on your pc or mac and delete\kill the Waves services that launches when scanning waves plugins. Or just try to delete their portal\installation agent after installing the plugins. Check the Brandmauer access limitations\settings and try to give permissions to Waves shell services that answer for the wave plugins debugging process.
So uninstall waves central aka the install portal?
I keep my music PC offline so it’s not an option to let it through the fire wall which is what Google says brandmauer means
So much software require internet access these days, that could be why… maybe you need it online at least the first time activating the plugins and running the plugins in Renoise.
Yes. Because it literally eats the processor and opens some backdoor connections for debugging reporting.
Your brandmauer could keep blocking some functions in waves central.dll, which causes the crashes “even if your pc is offline all the time”. I had the same problems with the waves plugins " which i am not using at the moment" because of the waves install portal and debugging services that start with it. They launch everytime you open your daw, but in the background, Just check your task manager and try to kill those processes first of all. If didnt work - delete the whole install manager. “Waves Central”.
1 Like