@Roger Bansemer Yep, & on here you'll get the usual reply - What media are you using? Is your GPU driver up to date? What are your settings in Preferences?... If you argue then those replies will turn passive aggressive pointing the faults at you & you're use of the software.

There was a post on here not long ago titled something like 'What can be done to make Vegas better', performance & reliability was mentioned a couple of times.

It's every version of Vegas since I began using it back 12 years ago and continues with V20 Subscription. My computer is windows 10, 64 bit with an RTX700, i9 Core, and 64 gigs of ram which should be enough.

@Roger Bansemer Yep, & on here you'll get the usual reply - What media are you using? Is your GPU driver up to date? What are your settings in Preferences?... If you argue then those replies will turn passive aggressive pointing the faults at you & you're use of the software.

There was a post on here not long ago titled something like 'What can be done to make Vegas better', performance & reliability was mentioned a couple of times.

You may wish to read this thread and it's conclusion.

https://www.vegascreativesoftware.info/us/forum/vegas-16-keeps-crashing--137562/

@andyrpsmith I read almost every post on here & have done for a couple of yrs, my GPU drivers are always up to date, my system is more than powerful enough to do the job yet I get a few crashes every night when I use Vegas + effects,

The last few wks I've been learning & playing with Adobe AE + Boris effects, I've crashed it maybe 6 times, that's using it 6-8hrs every night, pressing the wrong buttons, messing with it's head & mine yet no crashes,

I've used Magix Edit Pro what's now Movie Studio since 2004, that's solid as a rock,

I've got Mocha Pro Standalone, Boris's Silhouette, & some CAD software, + other stuff.

As @Roger Bansemer says Vegas is the only program on my PC that constantly crashes, 🤔

@andyrpsmith 

The last few wks I've been learning & playing with Adobe AE + Boris effects, I've crashed it maybe 6 times, that's using it 6-8hrs every night, pressing the wrong buttons, messing with it's head & mine yet no crashes,

As @Roger Bansemer says Vegas is the only program on my PC that constantly crashes, 🤔

@Former user The thing I notice with boris and Resolve (that use the same OFX version) is that Resolve always recovers when I get a 'stopped responding message' . You just have to wait, could take as long as 6 seconds, and sometimes that's true with Vegas, but often it never recovers, and if you dare touch a key or click a mouse button it's 100% crashed. I am guessing Boris is semi to blame, but Vegas handles the problem much worse than other NLE's. The not responding situation I mention is directly related to interaction with the boris menu. I don't get 'not responding' with Boris and Resolve otherwise (temping fate saying that)

@Roger Bansemer, I have seen the same thing. Hasn't stopped any edits but did force me to save more frequently and work just a little slower which seemed to help. I found when my timeline locked up, playback was still happening and I could still press CTRL-S to save the project before stopping the playback and then getting the "gray out" screen. Waiting for the first update for VEGAS Pro 20 as I know stability is a big push right now.

Is this similar to what you see?

That is one instance that happens to me but more often it just locks up with the "not responding" indication. I'm a huge fan of Vegas and love editing but this not responding things is really getting frustrating after spending thousands of dollars over the years for upgrades. Come on Vegas, please try and resolve this. I've watched youtube tutorials on how to improve performance, etc but it still crashes. I'm not kidding when I say I spend 10 minutes out of every hour restarting Vegas.

I wish I could say, "I have no idea what you are talking about", however, I know exactly what you're talking about. Hit that "save" button often... I have two versions of Vegas loaded V20-139 and V19-550. The latter was fairly stable and v643 was pretty good.

Since you may have followed the advice on YouTube how to stop crashes, the first thing I recommend is doing a control-shift reset at startup and never watching those videos again...

@Former user I asked Peter on the Boris forum about something, can't remember what, he asked 'how long does Vegas hang for'. My reply was 'Vegas doesn't hang, if it freezes that's it, end of game, touch the screen & it's the white screen of death',

Like you say other software might freeze/hang for a moment but then it sorts itself out,

@Roger Bansemer I turned on Tools - Advanced save - Live Save, it saves after every edit so you don't loose those last few steps you took & forgot to save, but the problem is it overwrites your saved project, not always what you want & you have to give Vegas a moment after each edit for it to do that auto save,

I've found advanced backup (not live save)very useful as it creates incremental saves every few minutes but doesn't save everything I do like live save which I don't want as I experiment when editing.

@RogerS Yeah I turned on Live Save for when it crashes, you can get a lot done in a few minutes so saving after each edit is good but when doing as you say experimental, I found it had written over my project, doh! so now it gets turned on as n when it's appropriate,

I do save all the time. I'm constantly hitting ctrl-S but we really shouldn't have to be doing that all the time.

Just use advanced backup and pick a short interval.

@Roger Bansemer No you shouldn't have to keep saving,

PS. I just noticed a post titled something like 'Why you wouldn't recommend Vegas?' , crashing was the reason in that post, but that post has disappeared, I doubt the OP deleted it so I think the higher authorities have.

Turning a blind eye or Ignorance is bliss, it portrays in posts like this one where there's a severe lack of regular members commenting on this issue, ,

I'm always saving, but doing incremental saves, not saving over the project itself (Ctrl s). I've been doing this forever, not matter what software I've used to edit. And when I am finished editing and have the final project, I go back in and delete all the previous "Save as" projects.

It's a habit that I don't want to break. I do something I don't want to replicate, it gets an incremental save. And yes, there might be something in my edit that will cause the dreaded "white screen of death", so I go back to the previous save and take my steps slowly to see what caused it, saving along the way.

I'm still on VP19 and did reach a frustration point where doing simple editing would cause the white screen. I'd exit, restart, pick up where I left off, and it might happen again. But after that, Vegas for would stable until I would get up for my break. But when I get the crash, body temps rise and I wonder "why" am I bothering with this. But then I look at other editors, read about their issues, and then having to learn something new (at my age, it's tough), I plod along with Vegas. Most of the time, quite happily....except for that memory leaking/stealing issue.

Using build 214 of VEGAS Pro 20, I have no longer seen this issue happen on my projects.

@Roger Bansemer Hey Roger, i remember and is fully aware of your crashing issues with Vegas over the years, from on the Creative Cow forum as far back using Vegas 12..... Its often a puzzle figuring out why Vegas runs smoothly on some machines and crash riddled on others, there is always so much variables also.

Personally for me, to avoid the pitfalls i just go with absolutely no GPU anywhere in my editing system, and its editing bliss doing that.... But, this cant be a recommendation for others..... Vegas is a very different breed of NLE, and so i think that something in its architecture / coding is often conflicting with some systems config, causing this issue to be languishing on over the years for some users.

Try this newest build (214), run it through its paces for a couple hours etc and get back to us if the crashes persists. https://rdir.magix.net/?page=3E2ILX0PGVFJ

I just updated this morning and will see how it goes. I'm curious... you say you use not GPU. I have an RTX 3070. Are you suggesting that I set it to none and why would that help?

Thanks

@Roger Bansemer I have an RX 6800XT but with hardware decoding enabled it crashes constantly, unusable, but when I Enable legacy AVC decoding, which greys out the Hardware Decoder, I never get a crash, honestly, never. I just make use of Dynamic RAM Preview across intensive effects, having it set at 40%. Sure, it now seems a waste of money to have upgraded to the RX 6800XT but at least as @Steve_Rhoden says, I have "editing bliss", happily using Vegas frustration free, and hopefully, it may be utilised more in the future 😊

That's really interesting. I'll change my preferences now and give it a try. Once question though. Would that slow down rendering time? Thanks for the information.

No, not for me. I did multiple renders of the Vegas 4K Benchmarking Project with Legacy enabled and disabled and the fastest time by a second was with legacy AVC decoder enabled. I put both times on the Benchmarking results as suggested by Roger for others info. I hope you get it sorted.

I just updated this morning and will see how it goes. I'm curious... you say you use not GPU. I have an RTX 3070. Are you suggesting that I set it to none and why would that help?

Thanks

Changing to legacy AVC forces Vegas to use compoundplug.dll to decode (CPU only) rather than the so4compoundplug.dll which uses the GPU and can decode other formats the legacy one does not.