Okay, to be honest I am complete f*cked up at the moment.
I did discover so many freaking (audio-related) bugs in Vegas 19 that I had to upgrade to version 20.
No problem, but version 20 is even more buggy like hell and sh*t.
Some suggested it was not Vegas' problem, but a videocard(driver) issue.
So I upgraded my freaking system for $ 3.500,- bucks.
Guess what?
The same bugs everywhere, I did post (some of) them here (do you guys even testdrive / bèta-test?).
Now when automating my workflow with iZotope (I did use Melda for this, but Vegas let Melda crash everywhere) I decided to buy RX09, since it's "just" $ 1.000,- bucks for a new license.
Yeah, RX09 crashes inside Vegas as well (again, I did post the bugreport here).
So I upgraded for another $ 1.500,- to RX10, since that's VST3 based where RX09 is VST2 (and 3).
You never know, do you?
Well, bye bye $ 1.500,- because in RX10 it's even worse!
RX09 lets crash Vegas (or the other way around) but RX10 makes Vegas unresponsive, while the GUI of the plugin itself is still working.
I have discovered now more than 5 bugs inside the plugin-chain in Vegas 20 and they all look "visual / canvas / redraw" related.
Simple enable / disable a RX09 / RX10 plugin et voila, crash, freeze, exploding freaking system.
Even the "trick" for RX09 (rightclicking on a plugin tab, not leftclicking) while the plugin GUI is out of sight doesn't work in RX10 : it always freezes the whole system (besides itself).
Since I can't even upload a screencapture here, check it out @ the neighbors;
https://i.ibb.co/pnVSq9G/vegas.gif
When I click on the Vegas canvas, a yellow spot is shown (without interaction, since the GUI is frozen), but the GUI / canvas of the plugin still responds.
Well, at least I bought some upgrades for about $ 6.000,- bucks in order to get a bèta-tester for this piece of cr*p.
My local PC-dealer says "thanks".