No such animal in editing. I do a lot of incremental saving just in case. There is no editor that does not crash. As for hanging, you have to give more information and be specific. Read THIS, specifically section B.

@DMT3 Not once in all the time of use? To be honest, after reading the forum, it's hard to believe...

@ser-z everything crashes. Everything is constantly being updated. But if Vegas crashed and stalled a lot, I would not be using it and move on. Or... post the required information to see if it's a "me" thing, or a "global" issue with everyone. Without you providing information, there is no way of knowing, especially considering your user profile is blank.

Are you conducting an opinion survey, or would you like peer support with a specific problem?

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

I stand corrected, it has crashed on me recently when using screen capture. Under normal editing situations it has not. My system is way below specs, I edit primarily AVCHD files from my Vixia camera and more recently
Blackmagic MJPEG files from my capture card and Nikon created mov files. It does not crash.

@Reyfox I'm not here to find out the "cause" of crashes. After reading a large number of topics on the forum, where people presented all the necessary information, I didn't see anything better than "convert your files to Avc Constant Frame rate", so I doubt that crashes and crashes can be "cured" at all. All the software is crashing, I agree, but not like Vegas. Arguing with this is stupid.

I can truthfully say that VEGAS Pro 19 build 636 is the most stable build of VEGAS I have used in recent years. Has it crashed on me? Yes - but only a couple of times out of many hours of usage.

@jetdv can you share the specifications of your PC and do you use third-party plugins?

@Reyfox I'm not here to find out the "cause" of crashes. After reading a large number of topics on the forum, where people presented all the necessary information, I didn't see anything better than "convert your files to Avc Constant Frame rate", so I doubt that crashes and crashes can be "cured" at all. All the software is crashing, I agree, but not like Vegas. Arguing with this is stupid.

Then you haven't read much if all you have come up with is "I didn't see anything better than "convert your files to Avc Constant Frame rate". As @Musicvid posted, are you looking for opinions or something specific.

Are you looking for help or something else? And yes, arguing this is stupid... so why even bring it up in the first place.

I'm not here to find out the "cause" of crashes. After reading a large number of topics on the forum, where people presented all the necessary information, I didn't see anything better than "convert your files to Avc Constant Frame rate", so I doubt that crashes and crashes can be "cured" at all. All the software is crashing, I agree, but not like Vegas. Arguing with this is stupid.

Vegas crashes rarely for me. Media is the most important factor and I use constant framerate AVC (Sony X-AVC S) for most projects. My hardware is in my signature- nothing fancy but also new enough to be supported by Vegas 19. It has an Intel iGPU which seems to work best for decoding in Vegas (I have more issues with NVDEC and Vegas but perhaps it's better on desktop GPUs).

@jetdv can you share the specifications of your PC and do you use third-party plugins?

@ser-z, I only install NewBlue plugins. I have an old system:

Processor    Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz   2.59 GHz
Installed RAM    12.0 GB (11.9 GB usable)

Edition    Windows 10 Home
Version    21H2
Installed on    ‎8/‎17/‎2020
OS build    19044.1706
Experience    Windows Feature Experience Pack 120.2212.4170.0

It's slow but it will run VEGAS Pro 19 636.

And my new system is:

Processor    12th Gen Intel(R) Core(TM) i7-12700H   2.30 GHz
Installed RAM    64.0 GB (63.7 GB usable)

Edition    Windows 11 Home
Version    21H2
Installed on    ‎4/‎26/‎2022
OS build    22000.675
Experience    Windows Feature Experience Pack 1000.22000.675.0

nVidia GeForce RTX 3060 driver 512.96

After my recent tests, I became convinced that the reason for frequent crashes and Vegas freezes are third-party plugins with GPU acceleration enabled. This is especially true for plugins from Boris Fx - Sapphire and BCC Continuum. I decided to experiment and DISABLED the GPU ACCELERATION of the Sapphire plugin in its config file, leaving the general GPU acceleration of Vegas enabled. In such a situation, Vegas has not flown out once in 3 hours of work (this is very rare). Of course, further tests are needed, but this is something. I also wanted to note that in this case Vegas consumes 90-100% of my i7 8700k and for some reason consumed about 20 GB of Ram. Although the Dynamic Ram Preview was set at 5% of my 32 GB.
I think developers should pay attention to this. I will continue the tests and continue this topic or create a new one. Can I ask someone close to the developers to inform them about this problem @RogerS @Reyfox ? I think the problem is in CUDA acceleration, because familiar Vegas users with Radeon graphics cards do not experience strong problems.

You have some heavyweight plugins loaded, and the Vegas developers are probably less involved than you think, since they have no sway either over third-party fx development, nor over the variety of systems they get used on.

This leads to the notion that solving your expectations is a process of evolution, and probably not remedial. Although your CPU meets the requirements, there is a suggestion that the newest ninth generation processors may give more stability with GPU-intensive effects in Vegas.

@ser-z I have Continuum Complete 2022.5, a couple of Sapphire plugins, NBFX TotalFX7, Graide, Ignite Pro 5, and some ancillary additional plugins like HOS and Vegasaur. Not one issue with my computer setup.

And if you are having with specific plugins, it's always best to go to the developers of that plugin. Boris has a user forum and people from the company are always there answering questions and taking suggestions. Me? I'm just another user like the rest here.

Also, it would be great if you added your computer specs to your user profile. Most of us have it listed in our Signature.

After my recent tests, I became convinced that the reason for frequent crashes and Vegas freezes are third-party plugins with GPU acceleration enabled. This is especially true for plugins from Boris Fx - Sapphire and BCC Continuum. I decided to experiment and DISABLED the GPU ACCELERATION of the Sapphire plugin in its config file, leaving the general GPU acceleration of Vegas enabled. In such a situation, Vegas has not flown out once in 3 hours of work (this is very rare). Of course, further tests are needed, but this is something. I also wanted to note that in this case Vegas consumes 90-100% of my i7 8700k and for some reason consumed about 20 GB of Ram. Although the Dynamic Ram Preview was set at 5% of my 32 GB.
I think developers should pay attention to this. I will continue the tests and continue this topic or create a new one. Can I ask someone close to the developers to inform them about this problem I think the problem is in CUDA acceleration, because familiar Vegas users with Radeon graphics cards do not experience strong problems.
 

That may well be the case- I don't have these plugins so can't verify myself. You can file a support request directly (top of this page under support. Don't click "ask the community"). Consider notifying Boris as well.

Take a look at when memory usage spikes- is it with a particular plugin? There may be a memory leak somewhere. If you can help narrow down where it is that would make fixing it easier.

Dynamic ram preview is not the same as ram, it's just a preview buffer Vegas uses. Vegas and plugins need additional ram to do other things.

I recently worked with legacy compoundplug reader and I can say that the problem was definitely not GPU Acceleration. With So4 Reader disabled, I have not had freezes or crashes for a long time. Yes, it's not as productive as So4 with GPU Decoding, but it's STABLE! And if so, I tried to disable GPU Decoding and enable and disable Dynamic Ram Preview, and tried a lot of other things. In any case, when working with So4 Reader Vegas crashes. The problem is precisely in him. How to fix it, any ideas?

In any case, when working with So4 Reader Vegas crashes. The problem is precisely in him. How to fix it, any ideas?

You can't fix it if you've already tried the usual fixes with recommended hardware, including using Intel IGPU for decoder if you have an intel, but also keep in mind that Vegas 13 crashed too, and it was due to to GPU processing, not decoding, so if you remove the SO4 decoder that was introduced in VP15, you'll still have GPU processing bugs from time to time.

If you have enough CPU you could tick Legacy AVC decoding as you have done, but also put GPU decoding to OFF, that way when Vegas forces SO4 decode(example 10bit files) it will use the Magix decoder but it won't use GPU decoding. Problem may be that some files require SO4 + GPU decode ON. I seem to recall cases like that, may have been HEVC files in VP18 though.

Also I like the idea about selectively being able to turn ofx on and off. It's like that in other NLE's

In any case, when working with So4 Reader Vegas crashes. The problem is precisely in him. How to fix it, any ideas?

You can't fix it if you've already tried the usual fixes with recommended hardware, including using Intel IGPU for decoder if you have an intel, but also keep in mind that Vegas 13 crashed too, and it was due to to GPU processing, not decoding, so if you remove the SO4 decoder that was introduced in VP15, you'll still have GPU processing bugs from time to time.

If you have enough CPU you could tick Legacy AVC decoding as you have done, but also put GPU decoding to OFF, that way when Vegas forces SO4 decode(example 10bit files) it will use the Magix decoder but it won't use GPU decoding. Problem may be that some files require SO4 + GPU decode ON. I seem to recall cases like that, may have been HEVC files in VP18 though.

Also I like the idea about selectively being able to turn ofx on and off. It's like that in other NLE's

"keep in mind that Vegas 13 crashed too, and it was due to to GPU processing"

But I tried to work with So4 enabled and GPU acceleration disabled. The result is the same - the program freezes and terminates through the task manager...

@ser-z I agree with you, turning GPU decode off does wonders for stability, but crashes still do occur due to GPU processing, but there's no way i'm turning GPU processing off for maximum stability, as performance suffers so much not to mention breaking many FX. I think our configuration of Vegas is the best compromise but the problem is for people with lower powered CPU's - 2-6core CPU and no GPU decode, CPU can rapidly become a bottleneck

@Former user "I think our configuration of Vegas is the best compromise " but I don't understand why the developers won't solve this problem, which stretches LITERALLY from the introduction of this So4 decoder in version 15? Why should users of PAID SOFTWARE suffer and understand why freezes occur? I know that the development team is very small, but this is not an excuse. instead of implementing less important functions like Text to Speech, they should have focused on optimization and troubleshooting with their MAIN decoder. Don't they understand that? many Vegas users leave not because they don't get new "roof-top" features, but because Vegas freezes and is extremely unstable. (With So4 enabled). Therefore, if they think that the implementation of new functions will somehow help the development and increase of the community as well as increase sales, then they are very mistaken. I think it's obvious.

I know that the development team is very small, but this is not an excuse. instead of implementing less important functions like Text to Speech, they should have focused on optimization and troubleshooting with their MAIN decoder. Don't they understand that?

Maybe whoever is responsible for the retrofit of the SO4 GPU decoder is high up in a small company. Nobody is willing to say it was a mistake after 5 years. Probably due to Sony Vegas never built with future plans of a GPU decoder. If you look back in the forum history, the introduction of GPU processing was also a major headache in the Sony days

I do not think that the introduction of GPU acceleration and even more so decoding was a mistake. on the contrary, it was a necessary right step, without which Vegas would now look like a complete outsider. I wonder if the developers plan to fix this problem in principle, or will they just ignore it?