I guess Vegas Pro, as a "host" is not officially supported according to iZotopes site.

Many have said it works fine in Vegas Pro. That being said, I must wonder WHY Vegas Pro does not appear in iZotopes list as officially supporting Vegas Pro.

I must wonder WHY Vegas Pro does not appear in iZotopes list as officially supporting Vegas Pro.

I wouldn't be too concerned. The only NLE listed as being a supported host is Premiere Pro. All the other hosts listed are DAWs.

Vegas does not support the VST-3 format. I am not positive but most of iZotope's plug-ins install VST-2 as well or an option to. As was stated before, the VST search folder must be designated. I think the default is "Program files/Steinberg/VstPlugins" and/or "Program files (x86)/Steinberg/VstPlugins". Besides the VST-3 plug-ins, the only other plug-ins I have encountered that do not work in Vegas are a few Direct X plugs) like the iZ Mastering Suite that was included with Sound Forge Pro 9 & 10 and the Ultrafunk R3fx Suite. They do however work in the old 32 bit version of Vegas and Sound Forge (x86).

All my latest and recent version iZotope plugins appear as expected in Vegas Pro 19: RX9 plugins (7 and 8 as well), Ozone 8 and 9, Neutron 3 and Nectar 2. They don't automatically install in Vegas Pro (or Sound Forge Pro for that matter) - they have to be loaded in Vegas Pro via Options/Preferences/VST Effects (tab) by using one of the Alternate VST folders to drill down to the folder where the iZotope vst plugins are stored (usually C:\Program Files (x86)\Steinberg and/or C:\Program Files\Steinberg).

With RX, only the vst plugins will install into Vegas Pro - I cannot recall a time when the full RX program itself was accessible in Vegas Pro, and that's from RX4 onwards.

Why would iZotope install their VST's in a Steinberg folder? Cubase and other Steinberg installations install VST's in the Steinberg folder, the iZotope VST's end up in the 'iZotope' folder on my machine. That being said, NONE of my iZotope VST's are working in Vegas 19, when I point the VST Effects / VST search folder paths to the iZotope folder full of handy VST's (for mastering VO's and music in my video productions etc) like Nectar and Ozone, Vegas 19 simply ignores them and loads the default (very limited) MAGIX VST's. Why? I've been beta testing Vegas since Sony bought it from the Sonic Foundry guys in 1999 or whatever it was, have never had a problem. Any further ideas, like 'hey MAGIX devs' let the VST's be a shared Virtual Studio Technology as they were intended to be!! It's so crazy, I copied all the iZotope VST's across to the MAGIX 'Shared Plug-Ins' folder to try to trick Vegas Pro into thinking that it was okay to load these VST's because they're being 'Shared' etc. and then I watched as Vegas went through and 'loaded' each and every iZotope VST (i just happen to have collected them all, so it takes a while), then at the end of the load, they don't even make it to the VST list like they used to so easily, Vegas simply ignores them and lists the MAGIX eFX ChorusFlanger, eFX Compressor etc etc and other stuff that I hardly ever use, and I can't access my Nectar and Ozone VST's. Why? Could someone please tell me how to fix this, any ideas appreciated. (And yes, I've tried the iZotope VST's as 2's and 3's, makes no difference.)

It's the standard location for VST2s. The VST2 dlls are all working fine for me from C:\Program Files\Steinberg\VstPlugins