VEGAS is being rebuilt with big changes to HEVC decoding in 21 and more video engine improvements to come according to posts here. The audio engine has undergone a rework since VP 20.

My biggest wish is also crashfree editing since years.

Sadly mark-y tips doesn't help much, bugs are bugs, which i try to help find.

(...)
What SAY YOU?

Ok.

@popfizz, I'm sorry to hear you're having troubles.

The support is lame

That's particularly concerning, so I looked into it. All we can find from you is a ticket asking about using hub features with a perpetual version, and when you were told that you need to have a subscription version for those features, your response was essentially a copy of your original post here. You apparantly used a different email address or something on your other contacts with our support. Please post here your other support ticket number or numbers. I will be happy to have the support team look into your history and find out why you are so unhappy with their service and why they weren't able to help you find a solution.

My biggest wish is also crashfree editing since years.

Sadly mark-y tips doesn't help much, bugs are bugs, which i try to help find.

@relaxvideo If you're referring to the link mark-y posted, it's not tips; it's just a request for information so that forum members can help popfizz reduce their crashes. "...a very fast computer/video card/tons of ram..." doesn't really help. There are people here skilled in helping users troubleshoot their issues. popfizz hasn't even told us what media they're using or what they're doing when the crashes occur. So unless we get more info, it's just a rant.

Yes, i know that thread

I'm 99% sure the problem is not there (using Vegas since 3.0), it will be just time spending for popfizz and for us too. As i say, bugs are bugs, which should be fixed. Sooner the better.

"what media they're using"

Doesn't matter much, because i had crash in the past even with simple trimming a fullhd jpg file.
But with the exactly same setup and Vegas version sometimes i can edit 1 hour without crash. Totally random.

And sorry if these sounds rude, i don't want to be that, it's only my experience since many-many years.
But i still hope!

First of all.....the support tickets I've sent recently don't address the crashes because I'm not going to bother doing the usual troubleshooting advice you routinely give. The reason is this...... I've read LITERALLY hundreds of complaints on reddit and elsewhere of users stating that your troubleshooting rarely fixes the issue. I have read many many posts stating that your support CANNOT fix the problem. After reinstalling again and again nothing changes. I am not stating this in a vacume....there are legions of users forced into using another program. Crashing is a known problem with ALL kinds of media. Perhaps not for everyone....but enough for it to be common knowledge. Also going back in the past, I have delt with your email support....waiting four or 5 days for any response. There are numerous videos on youtube of users complaining about the instability of Vegas. Why bother trying to put a square peg in a round hole. Vegas has a big round hole in it. I did a lot of research online to see for myself that the problems with Vegas are numerous and effect a good portion of Vegas users...this is a FACT. Mix that with the FACT that many users believe that the later versions of Vegas are even more prone to crashing. My Dell xps 8950 should be more than capable of running vegas. 12th Gen Intel(R) Core(TM) i7-12700   2.10 GHz
16.0 GB (15.7 GB usable) with a high end Nvidia Graphics card.

Do all programs have crashes from time to time....absolutely. Do all programs crash constantly...not ones that anyone will keep using!

What was I doing when the program crashed? Let me count the ways.... importing PNG a JPG.1080p video. MP4, Not even 4K. Moving the cursor too fast in a zoom, moving the cursor on the timeline too fast...then it turns into another tool and then crashes. There are so many different scenarios that cause a crash it boggles the mind. And if I am doing something wrong or have some settings wrong....why are SO many others having issues with consistent crashes that seem to be totally random. IF the program is that finicky that so many users are complaining and switching, isn't that reason enough to learn a more stable program that is not becoming less stable with new releases. See for yourself on youtube....all the Vegas users that really wished the program could actually finish a project without repeated crashes. Perhaps for the simplest most basic editing you can get by. But there are so many programs to do that. The feature rich versions of Vegas now is like a lot of tech built on a foundation that is basically too flawed to be built upon. That's my take on the situation. Yes, this might be one persons "rant"...but I could show you literally hundreds of posts and videos that support my claim without any question. And to take this all to a subscription based service with track record like this. ??????????

With a program this problematic...no phone support and up to week to get a response from support....It's just not acceptable to me at this point!

@popfizz

Hi

After filtering out the rhetoric and hyperbole - your post amounts to this:

Computer spec:

• Dell xps 8950, Intel(R) Core(TM) i7-12700   2.10 GHz
• 16.0 GB (15.7 GB usable) Ram?
• high end Nvidia Graphics card.

I see no mention of the Nvidia GPU model, Windows version installed, nor the build number of Vegas Pro causing the issue which boils down to:

. . . . Moving the cursor too fast in a zoom, moving the cursor on the timeline too fast...then it turns into another tool and then crashes. . . .

Are the drivers for both the Intel UHD770 and the Nvidia 'highend' GPUs up to date?

Has the version of Windows installed been 'hacked' to remove 'unecessary' features or been modified in any way?

John EB

@popfizz

(...) there are legions

Were they Roman?

of users forced into using another program. (...)

Forced by whom, Asterix & Obelix?

Try poetry, suits you better...

I am running latest Windows 11 video card Geforce RTX306011 latest version of Vegas Pro 19
Moving the cursor is not the only thing that crashes the program. As relaxvideo says and many others say "there are countless reasons when the program crashes" Importing Mp4 Mov 1080P video not even 4K. I think there are issues when you click too soon on an object and countless scenarios. Using effects, Using Text. Glitches in the preview window when using transition and EFX.

Not saying it won't ever crash, but when using Resolve....not one crash yet. I couldn't imagine any program crashing more than Vegas 19. It feels much smoother scrolling through the timeline.

I'm open to suggestions and I would love to be proven wrong....and that Vegas Pro can be a stable program.

Some of the posts about this issue are on this forum like this one from a year or 2 ago

"There is and has been something inherently wrong with Vegas for many years as I believe I started with something like Vegas 8 back in the Sony days. It seems about time that these stability issues are addressed. I would be happy to work with the Vegas team to provide information to finally isolate and kill these bugs.

Having said all this, I am still totally committed to Vegas, and I just tolerate the crashes, surviving with frequent and incessant saves". "A version of Vegas that does not crash would be a miracle at this point"...

He's willing to stick with Vegas though.

I just think I'm tired of "eggshell editing" Walking on Eggshells in the middle of a big project when you know at any moment.........crash!

If it works for you....more power to ya. Wish it worked for me! I would think it was my settings or setup....but I read so so many posts from very savvy editors that know tech inside out. They have top level hardware. Nobody can dispute the sheer amount of negative feedback from editors posting online. I don't see how you can ignore that fact when defending this product. It's not a conspiracy.... these aren't Resolve bots posting....They are or were Vegas Pro Users. And there are many posts and videos as I have wrote repeatedly. This cannot be disputed.

Do consider using the Intel driver assistant tool to update iGPU drivers and find the current studio driver.

Beyond that VEGAS is particular about media. Give it media it likes and there's less chance of a crash. Share MediaInfo and can advise you further.

Gary who posted here is senior staff for the program and offered to personally look into your issues, but you have to document that with a support request.

Ignore Reditt, etc., here you are talking to people actually connected with this program.

For many of us stability is improving since the dark days of VP15 but I understand that little solace to those who still have issues and the points in your last comment are well expressed.

Rodger I appreciate your advice....and I do apricate Gary's offer. I sent a ticket to Magix.

I would just say... Reddit can be hit or miss, but I wouldn't dismiss many posters who complain of Vegas stability. Many edit professionally with robust systems. Not just Reddit but this forum and Youtube. As far as giving Vegas media it can handle.....that's not a good workaround for my needs, and many others. I will bring up Resolve...so far it can handle anything I throw at it. Projects that crash Vegas will work in Resolve, no tweaking hardware....not having to make the settings just right for you to get through a project. I'm not used to the timeline yet....but I can tell that Resolve is a MUCH MUCH more powerful program. So many functions are highly superior to Vegas. I may try to get Vegas to work correctly. But it may already be too late. I'm starting to really enjoy editing on Resolve. Besides all those crashes and as easy an interface Vegas is....I think the same basic tools are getting tired at this point. The Zoom pan and crop. Titles and ability to customize them are nowhere near Resolve.

This post wasn't about switching to Resolve....but the more I learn it the more I am considering abandoning Vegas.
Some people use both. But I think once you get better with Resolve, there's no need for Vegas anymore!

This post wasn't about switching to Resolve....but the more I learn it the more I am considering abandoning Vegas.
Some people use both. But I think once you get better with Resolve, there's no need for Vegas anymore!

BM refuse to update editing window to make it more user friendly and more logical and not have to do multiple actions to perform the same action that Vegas could do in 1. I've been looking at Capcut, powerful software but they are not very ethical , constantly bringing in new features in free version for userbase to beta test then they remove the new features and lock it behind the paid subscription version.

There's also Shotcut which I think is a free editor, although I'm confused as to why I see so many videos with shotcut watermarking on them, this would seem to indicate you have to do something to remove watermark such as pay for it.

I've never had Capcut or Resolve crash (although they do), except when I had 3rd party plugins Resolve did not like, but after the crash Resolve on next load gave me a popup message about the plugin being automatically disabled due to the software identifying the cause of the crash. Vegas crashes unrelated to using 3rd party plugins but maybe it's stability decreases with simply having them installed. It would be good if Vegas could identify problem plugins.

RogerS:

"Give it media it likes and there's less chance of a crash"

You think a simple 1920x1080 jpg file is not what Vegas like?
(yes, sometimes i had crash with simple trimming a jpg on timeline. i'm just saying, bug is somewhere else!)

I've never had an issue with a jpeg. HEVC, yes. Unoptimized screen captures, yes.

I'm also a frequent poster on the VEGAS Pro Reddit. I don't dismiss people's issues but that place stuffers from groupthink and piling on.

Personally I wish VEGAS would just reject media it can't reliably edit or force a reencoding itself.

@popfizz

Maybe I missed it. But what is the footage you edit? Is there a mediainfo about it? Could you be so kind and upload a sample where Vegas crashes?

i would really like to test such a sample on my systems.

Maybe you are right - there are a lot of complains about the stability of Vegas. But there are also systems like mine, where crashes happen in a limited way only. And I would really like to find out why such crashes does not happen here with my two systems (see my signature for details). Is it the type of footage that I edit? What is real camera footage - maybe with some iphone footage. Are it my drivers? My hardware? What is it?

I don't think it's necessarily the footage. I think it's the combination of effects, transitions, titles and animated images. I don't have super extensive EFX but I do have multiple layers of some effects and layers of titles. I just think Vegas can't handle playing back several effects and motion EFX at the same time. The program can't seem to handle multiple layers of media, which is one of the primary functions and it's what's so good about Vegas....except it can't handle the job. I've had it also crash just using a lot of Jpegs and PNG files that have a lot of zooming, panning, titles, and some effects. This in my experience are projects that Vegas cannot seem to handle. All the video is 1080P Vegas can play back the media...it's when that media is in any kind of mildly complex way....its a crap shoot that you can finish a project without multiple crashes.

Interesting. Why do you avoid that we can help a look into your issue?

It is simply wrong that the footage is not important to identify bugs.

And I can tell you: Some month ago I have created a slideshow with Vegas of 20 minutes - with hundreds of pictures both jpegs and png files, and a lot of zooming, panning and effects. And it worked quite well here.

And I did that on my laptop - specs see my signiture.

It's generally the footage x GPU based on posts here. Titles seem to have some strange caching issues with the video engine that can result in corrupt frames though see that less in recent versions.

Other issues exist but are edge cases in comparison. We see very few complaints about stills vs say HEVC with NVIDIA decoding.

Have to agree with OP.

My personal experience over last 10 years is that Vegas Pro constantly (always within 30 minutes) crashes randomly when working with heavily encoded MP4 containers.

That is until I learned to convert all footage to ProRES. Haven't had a single crash since then.

Have to agree with OP.

My personal experience over last 10 years is that Vegas Pro constantly (always within 30 minutes) crashes randomly when working with heavily encoded MP4 containers.

That is until I learned to convert all footage to ProRES. Haven't had a single crash since then.

I, too, used to transcode ALL of my video, but I am beyond that. If an NLE cannot maintain stability working with these [at this point] fairly mature and uber common CODECs, then it is better to find one that does.

Transcoding tens of GBs of footage before editing is a massive time sink when you can otherwise just use the footage as is and get to work.

VEGAS is being heavily marketed towards the Content Creator market. Those CODECs are pretty standard there, and the creators who aren't using them typically are editing on Macs and/or have already moved to stuff like Creative Cloud, Resolve Studio or Final Cut Pro.

YouTube isn't my job - nor do I want it to be - so I'd rather not have to waste a constantly increasing cumulative quantity of hours of my life transcoding footage that I really shouldn't have to transcode at all to edit. I have other things to do in that time... I can spend that hour at the gym, or doing a meal plan... or doing maintenance on my sports equipment, etc.

I have Windows 10 and 11 which crash about once a month without using Vegas., just normal usage. I don't see how any APP cannot crash on Windows. The only Windows that didn't crash was 3.1 and the Bell Labs Unix. I remember working on Western Electric/Bell Labs drop equipment. Install the transistor in normally and it worked fine. Install it in backwards and it was only 6 db down. Their power supplies were designed about 1000% more than needed. I believe that people are looking for NASA quality at bargain prices. Using "Watson" with a few billion dollars might find answers to Vegas crashes. Otherwise a programmer trying to find the cause of a crash involving a trillion code combinations is impossible.

JJK