[Edit: originally noticed with Reason 11 but it’s apparent for other VST3 plugins also]
Description:
I’ve just installed Renoise 3.3 and several VST3 instruments/effects (including: Reason 11, Dexed, and Ozone9 Elements) aren’t appearing in VST instruments nor effects.
Steps to reproduce:
Go to plugin view (or DSP pane)
Open list of instruments (or DSP effects)
Search for Reason/Dexed/Ozone
Expected results:
Listed VST3 plugins appear.
Actual results:
Listed VST3 plugins VST3 plugins do not appear.
Extras:
Due diligence:
confirmed VSTs in correct directory
rescanned VST directory
removed/re-added VST directory
ensured that Enable VST3 plugins is ticked
tested that instruments/effects work in another DAW (Reaper)
definitely in Renoise 3.3 (just in case)
Possibly useful:
after re-scanning, status bar indicates “Found ‘1’ VST3 effects and ‘0’ VST instruments”
You can try hard linking your vst3 folders instead of copying the plug-ins. This should work in most cases. Use the cmd command (running as admin)
and the mklink /J or /D command like explained here.
The policy thing is however rather related to match the requirements of MS.
They want all developers to use the systems given standard architecture for their apps. This is nasty, especially when you`re dealing with a small SSD for your OS . Theres a complex tutorial on YT how to customize your Windows for your use case via regedit. I don’t link it here, because one error in typing will force you to reinstall Windows from the first scratch.
Fyi; besides not setting the correct path for vst3, in windows 10 I had an issue with vst3 not appearing after scanning because of missing Microsoft visual C++ runtime packages.
This got me really confused as well, no clue why Steinberg this was a good idea, but nevermind. Thankfully I don’t have lots of folders and VSTs to move.