This only happened once while scanning for plugins for the first time - all following scans worked fine?
When loading and unloading a waves plugins - does it seem to leak memory as well then?
I don’t have that many waves plugins to test, so this will be hard to replicate here, but I’ll try to make sure that it’s not a general problem and check back with Waves if this maybe is a known problem on there side.
WaveShell1-VST3 9.92.vst3 is also problematic here, the system get laggy and have to reboot, it looks like it’s spawning multiple AudioPluginServer32, is the normal to have two running at the same time?
RemoteAudioPlugin: Instantiating 'C:\Program Files (x86)\Common Files\VST3\WaveShell1-VST3 9.92.vst3'...
RemoteAudioPlugin: Creating pipes...
RemoteAudioPlugin: Launching plugin server process...
System: Launching Process: "C:/Program Files/Renoise 3.3.0/Resources/AudioPluginServer32.exe" 7596 C:/Users/Thomas/AppData/Local/Temp/Renoise-0-7596/PipeMemory-2 RNS_PipeTrigger-7596-2 RNS_PipeWait-7596-2 C:/Users/Thomas/AppData/Local/Temp/Renoise-0-7596/PipeMemory-3 RNS_PipeTrigger-7596-3 RNS_PipeWait-7596-3 --dpiawareness 1
RemoteAudioPlugin: Connecting to the server...
RemoteAudioPlugin: Creating server thread...
RemoteAudioPlugin: Creating plugin instance in the server...
RemoteAudioPlugin: Initializing plugin instance...
RemoteAudioPlugin: Instantiating 'C:\Program Files (x86)\Common Files\VST3\WaveShell1-VST3 9.92.vst3:5653544331434D633120636F6D702D73'...
RemoteAudioPlugin: Creating pipes...
RemoteAudioPlugin: Launching plugin server process...
System: Launching Process: "C:/Program Files/Renoise 3.3.0/Resources/AudioPluginServer32.exe" 7596 C:/Users/Thomas/AppData/Local/Temp/Renoise-0-7596/PipeMemory-4 RNS_PipeTrigger-7596-4 RNS_PipeWait-7596-4 C:/Users/Thomas/AppData/Local/Temp/Renoise-0-7596/PipeMemory-5 RNS_PipeTrigger-7596-5 RNS_PipeWait-7596-5 --dpiawareness 1
RemoteAudioPlugin: Connecting to the server...
RemoteAudioPlugin: Creating server thread...
RemoteAudioPlugin: Creating plugin instance in the server...
RemoteAudioPlugin: Initializing plugin instance...
RemoteAudioPlugin: Successfully initialized
This is the 32bit version of Waves, so Renoise needs to spawn a 32bit process to open it. So that’s just as expected.
And yes a new plugin server instance is launched for each plugin that gets loaded in Renoise. The plugin server is pretty lightweight, so this usually isn’t a problem. The leak must be caused by something else.
The WaveShell1-VST3 9.92.vst3 contains more than one plugin. It contains all plugins that you’ve installed via the “Waves Central” application - thus the name shell.
If you don’t need the 32bit versions of the Waves Plugins you could for now simply deleted it, or better temporarily rename it to something like WaveShell1-VST3 9.92.vst3.disabled. This should prevent it from being scanned at all.
Does this 32bit version of the VST3 Waveshell work in other hosts which support 32bit plugins? I’ve never seen a 32bit WavesShell in newer installations of Waves. Probably it simply is broken, and Waves Central no longer updated it?
I should mention that the first thing I tried was make sure there were no rogue 32 bit versions of the Waves shells present on my machine. Same behaviour.
The x64 version works just fine in Reaper.
I just deleted the 32 bit waveshell but same thing is now happening with the x64 waveshell… a new thing happened though, I had 25GB free harddrive space before opening Renoise, a few minutes later I ran out of harddrive space.
I also have trouble with Waves. I’ve told Renoise to specifically NOT scan the folder the waves .dll is in (by editing the roaming config.xml) and only scan another vst plugin folder, but it keeps trying to rescan Waves every time anyway!
I am not using waves much inside renoise and i can live without it, but i am using it in Audition so uninstalling it completely is not an option (neither is updating it for the same reason as others have mentioned).
I’ve also tried deleting all the roaming/cached plugin files and messed around with different settings combinations and nothing seems to be working, it keeps trying to scan the waveshell files.
I know! I have neither of those active. I don’t know what’s causing it it to crash, but I managed to make it stop by disabling the option “scan on startup” and then deleting the cache files. Then it only auto-scans my specified folder once after deleting, which is outside of Program Files.
Nothing in the log helps here. It doesn’t scan Program Files when I disabled “scan on startup”. I think the fact that it auto-scans specified folders anyway had me confused. Didn’t realize that I’d still get my other plugins.
So, when is this going to be fixed? I can’t even run Renoise since 3.3 because it “hangs” on indexing Waves plugins. Do I really have to remove them from my computer for it to run?
Is there some way I could tell Renoise to NOT scan plugins at startup?
