How to choose between VST2 and VST3 installation of NI Product plugins? (or have both)

CT Blaze

It seems nowadays, by default, VST3 plugins of NI products are pushed to Windows VST folders (actually, I have given NI Access a sepcific custom VST folder), when a NI product is installed via NI Access.

How can I control for each product, WHICH version of VST is being copied where,

OR where can get manually get to the VST2 and VST3 versions of the NI product plugins respectively, to use them somewhere else (in another software).

I really do not appreciate if the user does not have control over these things (any longer).

Context: I am installing Maschine and Komplete 12, and just realized that other software, that requires VST2 still, does not handle the NI procudt plugins well.

Thank you and kind regards,

Carsten

Blindeddie

Native Access installs all versions of Plugins by default and cannot be altered. VST2 plugin installation location is modifiable in Native Access preferences, but note it is global and will install all VST2 to the same location unless you change that location for each individual install. I would recommend not doing that as having VSTs in one location makes troubleshoot and registering in a DAW much easier (you only need one scan path) for VST3 the location is hardcoded and cannot be modified as it appears to be an industry standard. (Program Files\Common Files\VST3). Cannot comment on VST2 not working well in other Software as I have never had an issue with them!

CT Blaze

uhm, seems it's still the DLLs of VST2 version copied to the custom folder specified in NI Access config.

BUT I have found a bug ,since the VST3 version are still copied and registered to \Program Files\Common Files\VST3 which is NOT desired outcome when one spcifies a custom folder for VST in NI Access.

Blindeddie

Native Access installs all versions of Plugins by default and cannot be altered. VST2 plugin installation location is modifiable in Native Access preferences, but note it is global and will install all VST2 to the same location unless you change that location for each individual install. I would recommend not doing that as having VSTs in one location makes troubleshoot and registering in a DAW much easier (you only need one scan path) for VST3 the location is hardcoded and cannot be modified as it appears to be an industry standard. (Program Files\Common Files\VST3). Cannot comment on VST2 not working well in other Software as I have never had an issue with them!

CT Blaze

OK thanks for enlightening me on this. Hardcoded is never good - I use custom locations to keep OS and apps and data seprarated, mainly for backup purposes ;)

BigG

How do I get Komplete Kontrol to reappear in VST2 plugin folder in Ableton? I have not now have VST and VST3 options and no VST2ootion and all my VST2 Komplete Kontrol sounds don’t load in my existing Ableton projects! Help?…