It appears that the TB_DeEsser_v3 plugin is causing the crash.

It appears that the TB_DeEsser_v3 plugin is causing the crash.

Even when you don't have the plugin installed?

Why are build 122 not crashing then?

Here's another - newer - project made with b122 - and it works PERFECTLY in build v122

... but b250 crashes :(

https://www.dropbox.com/scl/fi/0e53a822624xlfcfhlmxb/instant_crash_new.veg?rlkey=ty5mwmcwzgpaimxktu3et8f6m&st=hcsnsu8i&dl=0

Please make the next Vegas build as robust as build 122

Unlike the previous .veg project, the new .veg project opens without a problem in VP22b250 on both my desktop and laptop.

@David  ... It would be helpful if you could update your forum profile to include your computer specs etc (see mine as an example in the 'SIGNATURE' link at the bottom of my comments). That information does help to better understand your circumstances.

No crash here on the laptop in my signature and 22.250 but I do get this error message. Do I need to associate some media with files or is it okay to leave it all as media not found?

Thanks a lot @Dexcon and @RogerS - I'm glad the project doesn't crash for you. Perhaps I can make it work here without downgrading to b122 - or at least find out what's causing the crash.

It can't just be the TB_DeEsser_v3.dll ( like @VEGASDerek mentioned) since the first project also crashed for @Dexcon even though I'm guessing he does not have that plugin - also in a later project I've renamed the TB_DeEsser-file and I still get the crash on that v122 project.

Perhaps there're more than one issue/one bug causing these instant crashes.

@David  ... It would be helpful if you could update your forum profile to include your computer specs etc (see mine as an example in the 'SIGNATURE' link at the bottom of my comments). That information does help to better understand your circumstances.

Good idea - I don't see any specs or signatures in your posts? - I'll check my profile.

Here's a later project from b122 that instantly crashes b250 - even without the TB_DeEsser_v3

https://www.dropbox.com/scl/fi/vcze9hkw7w1vbzl2bewc2/instant_crash_3.veg?rlkey=89f9dwalwym9uqw753gfv1n5y&dl=0

Does this one crash for you guys too?

Click here for the signature with specs.

Does this one crash for you guys too?

Unfortunately, yes. The crash occurs the moment "Ignore all missing files ..." is selected ... BUT ... using the "Ignore ..." individual files option, the crash doesn't occur until the 15th,16th or 17th file is selected (seems to differ each time), but those files are .mp3.

... even though I'm guessing he does not have that plugin

Quite right. I've not ever had any ToneBoosters plugins installed.

Also, from the missing plugin window that RogerS uploaded, there is a VST3 plugin listed named MCharmverb. Has that plugin been applied to any audio event on the timeline? If yes, try deleting it/moving it on your computer (so that VP doesn't see it) and then see if the project opens. From that plugins website, Vegas Pro is not specifically listed as a supported host.

Thanks again, guys!

I'll try to remove MCharmVerb - perhaps v122 uses that plugin in a way that b250 can't handle.

Downgrading to b122 makes all the projects load nicely, though - no crashes in b122.

From the update log for VP22b239:

No longer crashing while loading incompatible VST plugins 

https://www.vegascreativesoftware.info/us/forum/update-vegas-pro-22-build-239--148287/

... I wonder if that could be the change in VST behaviour between b122 and b250 - which of course is the opposite of the intended outcome of that update item.

I also get the instant crash with 22.250. Do you have the same exception? Crash report sent.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 250)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
   Fault Address:       0x00007FF63E514A84
   Fault Offset:        0x00000000005F4A84

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
   Process Version:     Version 22.0 (Build 250)
   Process Description: VEGAS Pro
   Process Image Date:  2025-04-29 (Tue Apr 29) 08:59:48

When I use b122 and remove TB_DeEsser_v3 and MCharmVerb from the latest project it works in b250.

So ... b250 has a flaw that makes it crash when loading b122 projects which use certain plugins.

If you use those plugins in b250 they work nicely but as soon as the project is loaded and saved using b122 then b250 crashes.

@VEGASDerek

New update - b250 crashes for ANY audio plugin added ...

this way:

• New project
• Add an audio bus
• Add an assignable audio effect

@David Does a reset of VEGAS help anything? It seems strange to me you are crashing VEGAS so easily.

I added a video, added an audio bus (a), routed the audio track with the video to a, added an Fx (volume) to Bus A and no crash. I then tried two other Fx (distortion and Clarity Vx). Am i missing a step?

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Am i missing a step?

Hmm - please try this (far less steps):

• Open Vegas - an empty project - don't add any media files or tracks
• Add an audio bus - leave it empty
• Insert Audio Assignable FX - e.g. Pan (that's a Vegas plugin)

Didn't it crash?