Good day,
Firstly, a very, very, very Happy New Year to you all!
Secondly, I recently downloaded both the VST3 versions of SAC and SAW and tested each of the applications with a variety of VST3 plug-ins - 50 in total!
I implemented, the procedures as noted in both the SAC and SAW User Manuals for creating "ini" files - and all 50 plug-in worked as expected!
Thus, from my perspective, I was able to treat VST3 plug-ins in the same, identical manner, as VST2 plug-ins!
For this test, I implemented the default plug-in paths:
For SAC:
Path: C:\SAC64Demo\VST_PlugIns
ini file: C:\SAC64Demo\VST_PlugIns\name.dll
For SAW:
Path: C:\SAWStudio64Demo\VST_PlugIns
ini file: C:\SAWStudio64Demo\VST_PlugIns\name.dll
Note: For my setups, I usually go one step further by creating "plug-in type" folders, for example - employing SAC as an example here:
1) C:\SAC64Demo\VST_PlugIns\AmpSim\name.dll
2) C:\SAC64Demo\VST_PlugIns\Reverbs\name1.dll
3) C:\SAC64Demo\VST_PlugIns\Reverbs\name2.dll
4) C:\SAC64Demo\VST_PlugIns\EQs\name.dll
5) ...and so on...
As can be observed from the above examples, I place ALL of my reverb plug-in in the same folder- creating ini files that point to that location.
The only plug-in that I did NOT test were the Waves plug-ins - but as Bob has already provided that information for you, it did not really make any sense to re-invent the wheel.
As always...I do hope that some will find this information of some practicable use?
Thank you for your time...appreciated!
VST3 and "ini" files
Moderator: Bob L