Vegas Creative Software has a team of people testing their software on a wide range of hardware, but when you have thousands upon thousands of different hardware, OS, and software configurations, everything from driver issues to antivirus to OS updates trying to throw a wrench in your spokes, it can be difficult to track every bug down.

Six of one, half dozen of the other, or as the saying goes. A look at the PP forum shows its users experience much the same problems as Vegas users!

Whether it is possible to cure the crash of VEGAS Pro radically in the future build?

Does VEGAS team test every build in all kinds of computer OS which may be installed all kinds of softwares?

Or they just test every build in pure, clean computer OS?

One of my subscribed VEGAS tutorial channels switch to other NLEs again:

That is identical to the freezups that were cured 100% for me by disabling GPU Accelerstion of Video Processing. That former user obviously has a lot of tech experience, having come from Windows Movie Maker.

Hasta luego!

I am having problem not able to make Vegas crash in every single project ranging from 30 minutes to 2 hrs long project. My VP17 eats and spit out everything I throw at it. Seriously, I have not had a single crash while editing or rendering the project. When VP17 first early released. I had 2-3 crash per project. Now I have zero. The only 3rd party plugins I have with Vegas is Prodad Mercalli and Neat Video. Lucky me . Note. I don't disable anything in Vegas settings. I also don't pick my own GPU driver. I let Windows do all my updates. No complaint here.

I am having problem not able to make Vegas crash in every single project ranging from 30 minutes to 2 hrs long project. My VP17 eats and spit out everything I throw at it. Seriously, I have not had a single crash while editing or rendering the project. When VP17 first early released. I had 2-3 crash per project. Now I have zero. The only 3rd party plugins I have with Vegas is Prodad Mercalli and Neat Video. Lucky me . Note. I don't disable anything in Vegas settings. I also don't pick my own GPU driver. I let Windows do all my updates. No complaint here.

It is not complaint and It just cause some disscusions about this problem. Maybe Vegas Pro is probably one of the most buggy NLEs according all users in defferent social medias. It is possible because you almostly don't use third-party plugins so yours seldom crash but not all man's demand is as little or low as yours. They may need many different plugins to accomplish their work.

Gosh, what if it's the plugins? Seems to be a common thread in these complaints going back to 2016.

Maybe there should be a list of certified third party plugins from Magix so that playful people know what to stay away from.

One thing I've never bought into is the convoluted confab, "My expensive plugin always crashes Vegas, so it's Magix' fault."

As @BruceUSA I'm also lucky — I have zero crashes in VP17 during my normal workflow (last few days I'm trying to finish my project and working in VP 6+ hours a day with no crashes). I only use a few 3rd party plugins: Mercalli (many times in almost every project), NeatVideo (for my evening indoor footage), SeMV Auto Levels (while processing films scan), AAV ColorLab and FFmn White Balance (the last one very rarely).

Windows 10 Pro (1909), updating drivers regularly. GPU enabled in VP preferences.

P.S. I know two ways how can I crash my VP: use outdaded NewBlue Titler or trim during playback. Also I know some non-crashing issues in VP, but I have workarounds or they are not critical for me.

lan-mLMC, what possible achievement you really hope to acquire making such a post at this point mmmmm? and with your response the more futile things comes across. Just stop!.... All NLE's has its share of problems.

lan-mLMC, what possible achievement you really hope to acquire making such a post at this point mmmmm? and with your response the more futile things comes across. Just stop!.... All NLE's has its share of problems.

No, No, No, Maybe my shoddy English can't express my real intention accurately. I mean I hope this problem can be paid attention to by VEGAS team. There assuredly at least 3 old users of Vegas Pro around me switching to other NLE because of crash when doing big project. I hope VEGAS team can pay more attention to the robustness of VEGAS Pro.

Of course, there are many new users switching to VEGAS Pro but it seems that they are almost making small project. I mean that sometiomes the stable robustness of a NLE is more important than new features just like Edius. Edius is less feature than VGEAS Pro, but the stability make it as popular as VEGAS Pro.

Of course, there are many new users switching to VEGAS Pro but it seems that they are almost making small project.

Altough I'm by far not a new user, I never make big projects exept my end project that is the sum of all my "nested" small projects. That is already a very old option suited to make not too big projects with the chance of making faults and causing all kind of other problems.
 

... I can relate.... :)

Step 1: disable so4compound.dll

I have been plagued with crashes for a long time. video projects 6 to 10 minutes. Most the old timers here know of me. The only thing that has seemed to mitigate (and I stress Mitigate) is doing what VP calls Proxy prior to editing and turning the high DPI for the interface off (on by default). I have tried everything and beat the bushes at nausea for fixes with no improvement. I just hope that the people that develop this NLE focus on robustness as you call it rather than the whistles and bells they seem so focused on. Tech support has been mostly non-reponsive with a few exceptions. I remain with the platform because I like the simplicity of the interface and in general I just don't give up at anything easily in live, sometimes to my detriment. and of course I do not want to become vested in another crash ridden NLE as it takes a long time to learn any software. Almost all help has come from this forum. I guess my next call will be to decide if I am going to pay for version 18 when it comes out or wait to the end of the development cycle before putting my toes back in the water.

I'm so much faster editing in Vegas vs. Adobe, etc. that I am willing to be patient with new release bugs... I 've been using Vegas since 3.0.... For paid work I always start the project in the last version of Vegas & don't use the latest release until after several updates. I also keep my editing workstations clean from unnecessary apps, prevent auto updates, & back them up regularly.

However, I did buy a new $1000 (us) 17" 6-core laptop w/internal GTX 2060 recently & completed about an hour's worth of shorter videos in V17 for work. The sources were a mix of various video formats & all went well. The (Walmart Evoo brand) was faster than my old desktop Xeons, has room for (2) M.2 & (1) SSD, and allows me to edit lighter projects without being confined to my studio w/desktop 9900K.

I have to agree with this. My only suggestion to Magix is to stop making new version of VEGAS Pro, but fully remake the whole system to be more stable & reliable like other NLE.

when VEGAS Pro 17 is being promoted with the new screen capture, it doesnt work till today.

when VEGAS Pro 17 is being promoted with the new screen capture, it doesnt work till today

Screen Capture still doesn't work for most either.

Where is Gandolf when you need him, so many trolls:)

Sorry, but posting one video of a guy saying he's switching to another very buggy editing app is not evidence that "more and more" users are switching away from Vegas... Where's the evidence that there aren't just as many users switching to Vegas for similar reasons? I know I would get crashes all the time when I (used to, recently canceled my subscription) use Adobe's apps. Resolve wouldn't work right unless I had more modern hardware (it laughed at my old GTX 970 that ran Vegas just fine), and had many other limitations as well...

Vegas definitely crashes more often than most software does, and it's something Magix does need to get under control, but this thread is preaching to the choir. You aren't telling us anything we don't already know.

Other than the occasional crash when I click "render as", Vegas works absolutely perfectly for me right now. Screen capture works, GPU acceleration works, GPU rendering works, everything works beautifully and I have been running my business off of Vegas exclusively for nearly 20 years. For such supposedly buggy software, that's a great track record. I've had my headaches with it, and during those times it is easy to forget to look at the big picture and think "this software sucks for EVERYONE", but it isn't long before I realize it's usually just a limited number of people having the issue, and it usually isn't long before the issue gets patched out.

Also, "they need to stop making new versions and rewrite Vegas from the ground up" is the same as saying "they need to cut off all cash flow and then try to figure out how to pay a team of programmers to be able to spend an entire year or more rewriting software from the ground up while simultaneously providing support for their 5 existing apps (VP, VMS, DVDA, VE, and VI), and that simply isn't a viable solution, especially for a smaller company. That would be hard for any company of any size to do.