Not sure if this is the right topic, so excuse me if not.
I just bought Vegas Pro 20 (after working on the same large project for years in Vegas Pro 17 / 18 and 19).
But I discovered that "undoing" any action in a Melda plug-in does freeze Vegas totally.
I use some paid plug-ins from https://www.meldaproduction.com/MFreeFXBundle
For example, I setup the Mequalizer with a simple adjustment, try to "undo" it and Vegas freezes totally.
This happens in all three most recent builds of Vegas Pro 20 and with both the VST2 and VST3 plug-in from Melda.
I have been working on the same project with the same plugins for years now (it's a large and complex project) and Vegas 17 / 18 / 19 did not freeze at all.
So now I have bought Vegas 20, but I can't use it because undoing anything from the Melda plug-ins freeze up the program.
It can be a "Melda problem" but on the other hand everything works fine in Vegas 16 / 19, so it's maybe a "Vegas issue" as well (since it's related to the "undo" option).
Of course I can provide more information, when needed, but it looks like it can't pass the undo queue.
In Vegas 19 sometimes a "Melda action" couldn't be undone and other could be.
So the ones that couldn't be undo, where simply skipped.
Maybe now Vegas 20 is trying to undo an action that can't be undone, because it's outside it's scope?
When I change a simple thing in Melda, let's say adjusting the output from 10 to 11dB the following happens;
- Vegas 19 does not "record" (save / stack) this action, so you can't undo it (besides that, everything works fine)
- Vegas 20 does "record" (save / stack) more than 200 "undo states" for this single action.
It looks like it's not "undoing" 10 to 11, but 10.00 to 10.01 to 10.02 to 10.03, etc... until it reaches 11.00
And when trying to undo this (in Vegas) undoable thing, the whole software freezes.
So it has definitely something to do with the "undo stack" or how it is called.
Besides the undo stack overflowing, another thing is interesting.
When you make a change in a plug-in and than hide the plug-in window (or switch to another plug-in, even a Melda one), you can undo the complete list of undo's without freezing.
But once you make the plug-in you want to undo visual (seeing what happens in the plug-in GUI), the software freezes direct.
So it looks like a software / GPU (driver) / plug-in combination?
When I use the internal undo from Melda itself, everything works fine.
But when Vegas stumbles upon a Melda undo-history-state (and tries to undo it) the whole software freezes.
In Vegas 19 when using an enveloppe to automate an FX from Melda (let's say bringing the EQ from 9.5 to 9.25) it slows down the complete timeline. Stuttering, verrrrrrrrrrrryyyyyyyyyyyy sssssslllllllooooooooowwwwwwww audio, etc... even when the slope is about 1 second, it takes 10 second to pppplllllaaayyyyyyyyy;
In Vegas 20 it's superfluid! So thing did change for good, but also for worse.
I discovered that the RX plugins also overflow / flood the undo history.
When I change one single parameter (let's say from 4 to 3) the history has 25 undo's for it (4.75, 4.73, 4.31, 4.30, etc...).
It doesn't freeze like Melda, but it's something that shouldn't occur;
I've another bug and that's when you click on the plugins in the plugin chain (to turn them off / on or just to see what their parameters are) the order is messed up.
So plugin A - B - C will become A - C - B sometimes (both VST2 and VST3).
This bug does not occur when you right click on a plugin in the tab view and "select" it, only when you left click and "select it direct".
Also sometimes a plugin is not "checked" but the GUI (right click) says "checked / selected".
Hard to say, but this is a complete mess-up for professional use.
The redraw of an plugin is also terrible slow when you jump from plugin A to B.
Sometimes it takes more than a second or two and the whole screen flickers like hell.
In Vegas 19 it's almost instant, but Vegas 20 redraws the canvas sssssssllllloooooooowwwwwwwww.
When I change something using a knob (from Melda or RX plugin) the system almost stops being responsive.
Let's say change a parameter from 1 to 0.
When I check the undo-stack, it has almost 750 undo-states recorded.
Maybe my system is not top-notch (12gen Intel, Samsung PRO ssd's, 64GB ram), but it can not even handle those undo's.
I am a Vegas user since 2008, so I do know something about it.
Up to 2013 you could hit the internal prefs and set "create undos for fx parameter changes" to false.
It's now part of the default prefs and DOES resolve some problems, but under the hood they are still there.
Installed Vegas 17, just to compare things.
17 is so extreme superfluid, compared to 19 and 20.
The GUI of the plugins is instant, changes are very responsive, undo is "like it should be" (one action / one undo).
Knobs, parameters, Bezier curves for the enveloppes... I was totally forgotten how fast, smooth and quick Vegas could be.
What went wrong after 17?
I also checked the data-folder for Vegas 19 and 20, and it's loaded with error reports; thousands of them, for just the last 48 hours of testing from my side?