[bug] Please, fix Vegas so audio-professionals can also use it

Peterson wrote on 3/26/2023, 8:29 AM

The title says it all.

Vegas 20 is so extreme buggy when you are "more into" audio, it's almost unworkable.

I did create bug-reports, set comprehensive lists of errors, showed several screen-recordings, tried to contact the devs... nobody, literally nobody did answer.

The main problem is the absolute terrible support of VST3 plug-ins (just search inside this forum and filter on "audio"), but also the behavior that the plug-in chain gets totally corrupted when toggling / selecting a plug-in (first or third-party, VST2 or VST3).

I did already buy Studio One and Reaper, but am also in the middle of a rather big projects (that takes about 5 to 10 years to finish), so I can't migrate existing edits.

Just check this screen-recording to say how much garbage the plug-in chain is.

Plug-ins move to the left in the chain, just by clicking on them, ruing my complete audio-output.

And besides that, I am not even talking about more than 50 crashes, freezes, etc... a day - all related to audio / VST3 / canvas redraw and memory overflow issues.

Serious, this is pure sh*t for professionals in the industry.

Sorry to say that... since I am a user since Vegas 3 (which was audio only).

At least let someone answer to those bugs, 'cause I am not the only one complaining here.

Show some support, since we also support you by still staying here and using the software.

Back to post

Comments

Peterson wrote on 5/9/2023, 7:59 AM

@Peterson

The new Vegas 403 build does not hang anymore when applying VST3 spectral denoise. I also tried with success Voice de-noise, and spectral denoise + voice denoise in any combination...

From my limited testing on my side there seem to be progress on the audio front.

There is progress, but Melda is now not workable.

When you move a slider (let's say 1dB to 2dB) and that's about 100 pixels movement, every freaking pixel movement triggers hundreds of undo-states in memory.

Resulting in a crash when you "undo" that change, but also it's not possible to adjust the slider, because it is so extreme sluggish in movement.

This is introduced in build 403.

I have contact with the Melda devs and they say their plugin is not shooting those states; it is Vegas that fetches them.

Normally you take the start parameter (1dB) and end parameter (2dB) and when you "undo", it goes from 2 to 1.

But Vegas records all steps inbetween, like 1.01, 1.03, 1.94, 1.96, until it reaches 2.

So the memory is overflown and when you "undo" it, it goes back like 2.00, 1.99, 1.98, etc...

That is not how it should work; the inbetweeners are not important.