izotope plug ins

CHRIS HUME

I am posting here as there does not seem to be a forum on Izotope website.

Why does izotope and many other plug in companies insist on installing on your computer C drive. Im sure Im not the only one who`s C drive is maxed out but with izotope in particular there is no other option that to install to C drive . you may say well just move the vst3 file to your custom folder that your DAW scans (ableton live 12 in this instance ) well i do that - and it works 80% of the time . however many plug ins for example the new aurora, plasma, cascadia simply will not function if you move the vst3 file elsewhere , so just scan the C programme files common files vst3 folder - great but your only allowed one custom vst3 folder in ableton , so most of my functioning vst3 files are on an external G drive, but to use cascadia, visual mixer plasma etc i have to rescan the C programme files common files vst folder - its a mess

ozone 11 neutron 5 RX11 all work fine from the G folder why not these select programmes

PoorFellow

The VST3 folder is a system folder so the VST3 install location per definition is not supposed to be customizable.

Quote Steinberg : VST3 Plug-in path

The VST3 format has a dedicated installation path all VST3 plug-ins must comply with. All your VST3 plug-ins should be installed here:

Format	Path	Extension
VST3	C:\Program Files\Common Files\VST3 32-bit VST3 plug-ins on 64-bit Windows: C:\Program Files (x86)\Common Files\VST3	.vst3

Since all VST3 plug-ins must comply with that then you can not expect companies to not comply with what is a standard that must be complied with.

Besides , then even if you can get VST3 to work by copying to a custom made folder as you describe then from time to time we experience that people have problems because of using custom folders.

I am not here to berate you and you are free to make what choice that you will for your plugin installations but fact is that stuff tends to work better when installing the plugins to their default location (at least for VST3) so it is recommended to use the default location for plugin installation.

P.S. : One can also change things by using 'Symbolic Links" in Windows. I have no idea how well it works but you could try to look into that also , Ref. :

Changing-VST3-Folder-Guide

And a more general guide on the topic : The Complete Guide to Creating Symbolic Links (aka Symlinks) on Windows

PoorFellow

The VST3 folder is a system folder so the VST3 install location per definition is not supposed to be customizable.

Quote Steinberg : VST3 Plug-in path

The VST3 format has a dedicated installation path all VST3 plug-ins must comply with. All your VST3 plug-ins should be installed here:

Format	Path	Extension
VST3	C:\Program Files\Common Files\VST3 32-bit VST3 plug-ins on 64-bit Windows: C:\Program Files (x86)\Common Files\VST3	.vst3

Since all VST3 plug-ins must comply with that then you can not expect companies to not comply with what is a standard that must be complied with.

Besides , then even if you can get VST3 to work by copying to a custom made folder as you describe then from time to time we experience that people have problems because of using custom folders.

I am not here to berate you and you are free to make what choice that you will for your plugin installations but fact is that stuff tends to work better when installing the plugins to their default location (at least for VST3) so it is recommended to use the default location for plugin installation.

P.S. : One can also change things by using 'Symbolic Links" in Windows. I have no idea how well it works but you could try to look into that also , Ref. :

Changing-VST3-Folder-Guide

And a more general guide on the topic : The Complete Guide to Creating Symbolic Links (aka Symlinks) on Windows