@karma17 Can you write more about what hardware and media you are using?

I agree with you that Vegas came back from the dead and caught up with a lot of important features in recent versions.

@iEmby please check the currently unrelated link in your comment.

@iEmby please check the currently unrelated link in your comment.

sorry for that.. updated now.

 Still very much what it was, but with so much more improved under the hood, and now, at least in its current version, very stable.

That reflects my impressions as well. They've finally gotten to the bottom of the bugs with Intel GPU drivers, and the improvement was apparent right away to me. The developers' stated focus has shifted away from more bling and gee-whiz effects to more solidity and function, and they have stated there will be more improvements to come in this area. As newer hardware technology is also beginning to stabilize, I think we can expect even more improvements in both stability and speed.

@karma17 So very true....

Same here, very stable at the moment once it is up and running successfully. I do have a "kill vegas process" .vbs handy at he desktop for when it will not start (race condition bug the Vegas team found recently).

@iEmby sorry to hear that, try to eliminate step by step any hardware issues. I see that you have a micro ATX motherboard, so I presume the PC enclosure is not spacious, this may be not optimal cooling wise; so how is your cooling? You are in India, heat may be an issue for stability? 12the gen Intel is producing a lot of heat. If heat is an issue, try to underclock your CPU.

Another avenue of thought, disable your external GPU completely in Windows devices or BIOS (and restart).

Maybe update BIOS version to a newer one if available.

A final idea, if it crashes regularly like clockwork, maybe there is an issue in automatic saving; disable saving.

Also editing with Vegas 20 pro for some hours every day.

Have noticed that Vegas is rock stable - as were many earlier versions too, btw.

Only things that sometimes can disturb here could be:

1) Bought third party plug-ins - especially when using these plug-ins in parallel - i.e. in overlapping transitions - and if these plug-ins use the GPU. The problems are easy to identify - and the solution is just to render these areas in separate sessions.

2) Too many concurrent Vegas sessions - Using Win 10 I have only 32 GB Ram and 8 GB GPU - and that seems to be too little for more that 2-3 heavy Vegas sessions at the same time. Absolutely no problem, however, just have to remember it.

3) "Inedible" media - i.e. from old cameras or cellphones - or i.e. from Topaz AI (264) which can be quite pesky when used together with other media on a normal Vegas timeline - for some strange reason (sometimes) I can't even get aound the problem re-rendering that output to mp4 (AVC) - but mostly it works when rendering the Topaz output to some .mts. I have not tried all Topaz output possibilities btw. - but do not care as long as I can get on with the editing 😀

Agree on this. It is performing really well in my day to day work, even on my low-end hardware.

Same here... And I am usually tossing in something from NBFX or BorisFX in the videos.

VP19 had some hiccups, but VP20 has been pretty much smooth sailing for me.

We've been working hard behind the scenes, and the developers have been working even harder.

VEGAS has most of the new features it needs to be a solid competitor, so there's a focus on stability now, and upgrading the code base so it is easier to work on, troubleshoot, and upgrade... so if things seem a bit quieter for a bit, don't think that they aren't working hard on making VEGAS better. They're back there doing the hard work to make VEGAS even more solid. A lot of that work will go on unnoticed, except for fewer crashes, don't expect big announcements over it, just expect your product to work properly more and more as time goes on.

Once that solid foundation is poured, and we're ALL editing mostly crash-free (almost there! the comments here are evidence of that), then they start with the performance improvements. Don't want to put the horse ahead of the carriage by trying to grease the "VEGAS is too slow" squeaky wheels, only for it to lead to more "VEGAS is too buggy!" complaints, so they have to get the bugs out first.

VEGAS has a very solid, exciting future ahead of it. A day will come before too long where "VEGAS has the worst stability, rendering and playback performance of the major NLEs" will no longer be a phrase you hear.

I get the feeling that once that happens, with VEGAS being so much faster than everyone else as far as workflow goes, it will rocket to the top.

We've been working hard behind the scenes, and the developers have been working even harder.

VEGAS has a very solid, exciting future ahead of it.

Thanks for the heads-up.

Personally I use Vegas 100% as an advanced audio-editor / DAW (since version 3) and do have three serious bugs in Vegas 20.

Please don't only focus on video, also keep in mind audio is important.

I've bought a brand new system for almost $ 3.500,- to get rid of those bugs and there are still there (i9 Intel, 12th generation, 128GB ram, Samsung 990 PRO ssd's, top notch audio connected).

1. Today I had to restore at least 10 times a single project because the order of the VST2 / 3 | 32 / 64 bits audio-plugins were corrupted;

https://www.vegascreativesoftware.info/us/forum/bug-vegas-20-plugin-order-corrupted--139874/

2. On top of that the timeline shows complete garbage / garble visual artefacts (did buy both NVIDA + AMD GPU cards to solve it (by driver) and the navite iGPU on my main systemboard : none of it did work).

https://www.vegascreativesoftware.info/us/forum/bug-selection-cursor-artefacts-on-the-timeline--138798/

3. And last, but not least for sure, is the 100% freeze / crash when altering some parameters from third party plugins like RX (iZotope) or Melda - due to a ridiculous "undo error" which is overflowing the internal buffers;

https://www.vegascreativesoftware.info/us/forum/bugs-vegas-20-freezes-when-undoing-melda-plug-in-and-more--139751/

It takes me more time to buy / test new hardware and re-opening projects than I can work on them without any trouble.

I do have a "kill vegas process" .vbs handy at he desktop for when it will not start

No need for obscure .VBS as one can do it by .BAT

taskkill /F /im vegas200.exe

I even made some special .bat files with icons for it and stored it in my app-menu for quick access (need it dozens of times when Forge is not starting due to a link-library-bug, when fired from Vegas).

@Foo-Bar There is nothing obscure on my .vbs, as I write it myself, not taken from the net!

Code inside "Kill Vegas.vbs" (pretty similar to .BAT):

Set oShell = CreateObject("WScript.Shell")

oShell.Run "taskkill /f /im vegas200.exe /t", 0, True

@Foo-Bar There is nothing obscure on my .vbs, as I write it myself, not taken from the net!

Code inside "Kill Vegas.vbs" (pretty similar to .BAT):

Set oShell = CreateObject("WScript.Shell")

oShell.Run "taskkill /f /im vegas200.exe /t", 0, True

Well, that's the same script I use in the .bat file :-)

I like low-level programming, so using a plain text-file is (sometimes) more fun than wrapping it inside a scripting development.

Glad to see it works for you!

"pro" tip : create a shortcut for the .vbs / .bat and assign a nice name / icon to it.
 

When a crash occurs, at least you have a funny icon to look at... (and the distinctive look will assure you won't accidentally click the "app" if you want to launch, and not kill it).

SOUND FORGE

VEGAS

ICON ENVIROMENT

Speaking of graphical assets, did you know how professional Vegas is upgraded from 17 to 18?
 

Just kiddin'... found this asset inside the executable of Vegas while extracting the icons.

But it's inside every ones copy, I guess... a hidden gem.

@fr0sty NDA!