Please, help me out by confirming that my findings in Vegas 20 / build 403 are correct and not "only me".
The issue is that Vegas 20 / build 403 has (at my 12th gen i9 machine) a very slow performance when you use "certain" VST2 or VST3 plugins.
E.g. when you change an EQ value (by moving a slider inside the plugin) the system becomes very slow.
I think this is caused by the effect that Vegas "records" hundreds of useless steps when you change a parameter from e.g. 1dB to 2dB (or some other parameter change).
In the recordings below you can see what I mean;
- Build 403 : https://i.ibb.co/h2JDmhz/build-403.gif
- Build 370 : https://i.ibb.co/P6xMTPV/build-370.gif
The newest build show very slow mouse movement when you drag a slider or knob or EQ-setting.
Where the previous build is fluid (like normal mouse movement) when you do the exact same.
To make things easier to compare I narrow the issue to one single plugin from Melda - MEqualizer
Let's say you active band nr. 3 and drag it around in the plugin screen, just to "place" it somewhere.
In 403 this is not real time, you have to "fight" with your mouse to get the dot on the right place (and you mis that spot, because the GUI freezes).
In 370 it is okay, it just works as intended.
Those issues are not strictly for Melda, it affects other plugins as wel.
To make things easier, I did upload the free version of this particular plugin;
It's just a simple VST2 (VST3 is around, but I don't use it because of my workflow) of about 166KB in size.
When you download it, place it here;
Than try it out on your timeline (using Vegas 20 / build 403) and check out of it works fluid (when you change a knob, drag a band from left / right and | or adjust the handles around it to set the "q".
In my case : this works extreme slow, because Vegas is "recording" every single millisecond change you make, resulting in unacceptable performance.