[bug] Vegas 20 - RX10 crashes and freezes total GUI

Foo-Bar wrote on 2/28/2023, 3:26 PM

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".

Comments

Musicvid wrote on 2/28/2023, 7:51 PM

Have you reported your issues to iZotope? What do they say?

RogerS wrote on 2/28/2023, 9:10 PM

I'm not sure why you spent any money on hardware to address software issues.

I've also seen functionality issues with Izotope RX9 so mainly stuck with VP 19 for audio which mostly works. RX10 is VST3 only, right, so you have to work in VP20? I haven't yet upgraded for that reason. In VP20 I see hangs as the window draws but if I wait it comes back.

Hopefully you reported details of issues to both Vegas Creative Software and Izotope.

Happy to attempt to replicate issues with RX9 for diagnosis purposes if you specific which plugins and what you are doing with them to trigger problems.

Foo-Bar wrote on 3/1/2023, 2:22 AM

Have you reported your issues to iZotope? What do they say?

I also have (trials) of other NLE / DAW, even freeware solutions.

They all work 100% fine and flawless.

Even embedding a Melda plugin, combined with RX inside iZotope (the editor) works...

Just adding one single Melda or RX DLL does crash complete Vegas since version 20.

So I think, after weeks of debugging, crashlog investigation and testing in multipurpose environments the culprit is Vegas, not the messenger.

_________________________________

Besides that : I am a devver myself and do know how ecosystems of DDL (dynamic link libaries) work.

When Vegas says "it does support VST 2 / 3 extensions", all those extension (within the programming protocol) should work flawlessly, because when not Vegas can't say "it does support the protocol".

I mean, even when my microwave says "we do support VST", it should be able to handle them, because otherwise it doesn't support them.

Things would be different when Vegas should say "we don't support VST, but hey! You can always give it a try, maybe the system crashes, maybe the GUI freezes, but that's because we don't support them."

_________________________________

FYI : Melda plugins are also crashing.

I did contact Melda (and Vegas) about this.

Vegas never answered, Melda did.

Their answer?

"Sorry, but we don't support Vegas because the devs from Vegas never answer our e-mails and are not willing to work with us."

Foo-Bar wrote on 3/1/2023, 2:25 AM

I'm not sure why you spent any money on hardware to address software issues.

I've also seen functionality issues with Izotope RX9 so mainly stuck with VP 19 for audio which mostly works. RX10 is VST3 only, right, so you have to work in VP20? I haven't yet upgraded for that reason. In VP20 I see hangs as the window draws but if I wait it comes back.

Hopefully you reported details of issues to both Vegas Creative Software and Izotope.

Happy to attempt to replicate issues with RX9 for diagnosis purposes if you specific which plugins and what you are doing with them to trigger problems.

Because some other mentioned it a hardware (videodriver) issue "or something else".

Vegas 19 / RX09 is "okayish" : it does crash (what isn't?), but it works when don't leftclick on certain GUI items.

Vegas 20 / RX10 is crap : nothing is reliable.

On a more personal note : I quit my job and started working on a private project for about 5 to 10 years.

I am halfway now.

This project heavily relies on Vegas for the audio-part of the project, so I can not switch back and forth because of legacy reasons (yeah... Vegas 17 can't open Vegas 18, while the fileformat is exactly the same : I did heavenly filediff testing, XML investigation, etc... to see "why" it wasn't backwards compatible).

Bottomline (from my developers point of view) is that all the crashes has something to do with "the state" and "the way" this (mainly visual) state is saved inside the parent Vegas container.

The canvas, redraw of items, etc... are linked with all the freezes.

Even when undoing a split or edit in the main timelime does totally redraw the complete GUI, even when the plugin itself is not altered at all by that undo.

There is something fundamental wrong with the way Vegas handles the pluginchain / canvas and "state / memory" update.

RogerS wrote on 3/1/2023, 2:31 AM

VP 20 has a new audio VST engine. My initial testing of it showed issues with Izotope VST2s (which I reported) and I just continued with 19 / RX9 so I can complete projects in progress.

I also bounce audio to RX9 and use multiple RX plugins there instead of in Vegas.

For projects where I'm not doing much with audio I use 20.

Foo-Bar wrote on 3/2/2023, 7:44 AM

VP 20 has a new audio VST engine. My initial testing of it showed issues with Izotope VST2s (which I reported) and I just continued with 19 / RX9 so I can complete projects in progress.

I also bounce audio to RX9 and use multiple RX plugins there instead of in Vegas.

For projects where I'm not doing much with audio I use 20.

Thanks for confirming.

Now I am not alone in cyberspace with all the issues Vegas gives me.

The new VST2 / VST3 engine is, simply said, pure garbage.

RX10 even refuses to render in Vegas 20 (crash) and freezes when adjusting parameters.

Melda plugin do crash, because of an undo-stack-error in Vegas' side (I already did report it).

Other VST3 plugins can't undo, freeze or crash.

RX09 is "okayish" (yes, Vegas does crash) when you finetune them when not in plain sight (toggling the status, etc...).

But RX09 in Vegas 19 is not workable, when used with envelope-events (adjusting a parameter from 5% tot 5.01% freezes / stutters the complete system).

So now I am stuck with Vegas 20, RX09 and VST2.