Thanks so much Taktik + the Renoise team! This is the feature I needed the most!
The only issue I encountered, like others here, was Renoise hanging when scanning Waves plugins for the first time. My workaround was to just move them out of the VST3 folder (I don’t use sidechaining in waves, so for me it’s no loss).
Now I’m running sidechaining into Melda mmorph in Renoise… just in time to work on a sound design/horror soundtrack project. This is great. 
1 Like
Big thanks from me as well! This is a cool birthday gift for me tomorrow. 
Now my only remaining wish for Renoise would be hardware-accellerated UI rendering for Mac users, since any meters or analyzers and the general framerate can’t keep up with the high screen resolution of a 5k iMac. The UI is usable, but currently rather unpleasant on the eyes with the inconsistent framerate.
To be future-proof, native Apple M1 support would be cool as well.
If I read it correctly, you are still using Waves v9 plugins - I am not sure if that would fix your issue, but maybe you want to get the latest versions of them? I hate their business model, but it is what it is.
I have the latest version of the ones I want to keep using and uninstalled the rest I bought. Renoise scans the plugins just fine for me here on a Mac.
Sadly no Waves v9 for me.
I took the (yes annoying) plunge and updated in 2018, so it froze when scanning the waves shell for v10. Also, Windows machine here. Are you on V11?
I have upgraded the two plugins I want to keep to V12, they’re the only ones I have installed. Works just fine for me.
My Waves plugins are all either V11 or V12, and far as I can tell, every single VST3 I have (and tested) seems be loading and working just fine 
1 Like
Thank you so much Taktik! Jan 3rd was actually my birthday but I only found out now.
Thank YOU @taktik ! VST3 support and sidechaining are sending Renoise to another level. Renoise is very complex! 
BTW the sidechain tutorial video is very useful and professional!
1 Like
Many thanks!!
Waves shell v10 Win 10 64bit crashes for me (locks up scanning) - I just deleted the Waves Shell VST3 for now (hardly ever use my waves plugs nowadays anyway)
1 Like
Ive had nothin but probs with waves shell for some time now, so much so I stopped using waves stuff.
2 posts were split to a new topic: Windows: Roland Cloud VST3 plugins crash when instantiated multiple times
I’ve used 3.3 for a few days now and I’m experiencing several plugins crashing every now and then (not often, but several times a day and way more often than on the previous version) they don’t even have to be VST3 plugins, especially Best Service Engine 2.7 is very unstable, I might hear a loud pop and then that instrument doesn’t work anymore, If I clear the instrument slot and load Engine 2, Renoise might crash by just suddenly disappearing. I’ve had also plugins crash after a render, especially NI Kontakt and EastWest Play and some Waves VST3 plugins.
Report the problem in the help, support & bugs forum with used OS and steps to replicate if possible. A copy of the contents of the log file also helps. Access the folder where the log file is in through the help tab in Renoise.
1 Like
i love renoise! great update ! thx so much
I just installed 3.3 and VST3s weren’t showing up, which I thought was weird since VST3s are a big feature for this update…
Went to settings… Noticed VST3 box was unchecked… Checked VST3 box… Great success. 
2 Likes
I watched the sidechain video by achenar on youtube yesterday and needed far too long to realize, that he is talking about a new renoise version 
I don’t even use vsts that much but I already had plenty of fun playing with the new sidechaining device.
happy new year to the devs and everyone else 
1 Like
Holy shit check the backstage!
Thank you.
3 Likes
So how much less resources do the VST 3 plugins use or is it not that much lower?
I think I’ve got the same Waves & VST3 problem here, on WaveShell1-VST3 10.0.vst3 - which I notice it was trying to access as 32-bit? I kept waiting, and Windows Explorer crashed (!), but it did finally move on to WaveShell1-VST3 10.0_x64.vst3. I can see it doing something, memory use climbs about 3MB at a time to over 2500MB memory used. I’ve got Horizon, so I do have a ton of plugins, but that does look like a memory leak. Reaper 6 handles it ok though.
EDIT: Yup, let it run again, it ignored WaveShell1-VST3 10.0_x64.vst3 this time due to me clicking End Task… but when Renoise tried to load WaveShell3-VST3 10.0.vst3 (->32-bit) on the next launch, this time it did the thing where Renoise displays the critical bug error and crashes out. Now that I’ve gone through that scan process multiple times, it looks like VST3 v12 Waves plugins are loading. Trying to run a v10 VST3 32-bit plugin though (like CLA Vocals) causes a Renoise Crash when I launch the About screen in the plugin.