In Vegas 20 the use of VST2 / VST3 plugins (of third parties) is almost impossible.
Plugins crash, Vegas freeze, files get corrupted, etc..
I have reported a lot of bugs, related to those issues and am still trying to narrow the problems down.
This report is about my findings.
- Plugins do switch order when enabled / disabled and in view, this does not happen when not in view.
You can also toggle the state from the Mixing Console or by right clicking on the plugin tab (when not in view) and than they don't switch order.
- Plugins do crash (or Vegas) when toggling the enable / disable state and in view.
Again; this doesn't happen when you do so when not in view.
And when crashing, the GUI of the plugin is never drawn completely (it's "stuck" before finishing).
- When a plugin is initialized once (set on, or off) you can also toggle the state when in view, but they has to be initialized once before.
So this does look like an undo / redo / history thing.
- Plugins do Vegas crash when undoing them (it overflows the undo-buffer of Vegas)
- Everytime I "undo" an edit (no matter what edit) in Vegas, the complete (visible) plugin-chain is redrawn (which slows down everything).
- In the first part (before the cursor leaves the screen) I toggle the state when plugin is not in view, this works.
- The second part (after mouse leave and re-enter) I toggle when in view, this does crash.
- And the de-esser plugin was already initialized and does not crash when toggling.
It has "something" to do with the visual state / canvas / redraw of the GUI and the plugin toggle / history / undo / redo system that Vegas uses.
Whatever it is, Vegas is almost unusable as a DAW or for more serious audio-editing.
I debugged on several systems, both with dedicated GPU and iGPU, processors, AMD / Intel / Radeon.
All issues (and more...) remain and do only occur in Vegas 20.