[size=100]Tomy,

Personally, I see not truly recognizable differences and/or advantages between VST2 and VST3!
[/size]

I still believe VST2 is better performance... but you would have to test between the two for your particular system.

Bob L

@Bob: Thanks for the new release.
Do you suggest switching to VST3 even for plugins also available as VST2?

[size=100]Ruben,

Sadly, "NO"...these updates do not fix the JUCE issues!

JUCE is a "platform" or a "framework". Thus s the framework has issues - everything else is "downstream".

VST2/3, on the other hand, are what I tend to refer to as "protocols", such as "TCP/IP" and so on.
[/size]

[quote="cgrafx"]Bob announced the availability of SAC 64 v2 with VST3 support a couple of days ago.

[url]https://www.sawstudiouser.com/forums/showthread.php?20184-New-SAC64-Version-2-Released[/url][/QUOTE]

Thanks for the information. I'm eager to update my Sac64 to see how all the new features work.

Bob announced the availability of SAC 64 v2 with VST3 support a couple of days ago.

[url]https://www.sawstudiouser.com/forums/showthread.php?20184-New-SAC64-Version-2-Released[/url]

Since when have we had VST3 support in SAC?

On the other hand, does this solve the problems with the Juce Plugins or does that problem persist?

[size=100]Good day,

[B]Firstly, a very, very, very Happy New Year to you all![/B]

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 - [B]50 in total![/B]

I implemented, the procedures as noted in both the SAC and SAW User Manuals for creating "ini" files - [B]and all 50 plug-in worked as expected![/B]

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!
[/size]