Okeydokey.

C1 - My source footage and source audio varies widely and comes from multiple different sources in multiple different formats, filmed / audio-recorded on PC, Mac, and other apps. The same problem of constant freeze-ups and crashes happens across every different format of video and every different source. I could list every video / audio file's meta info here but it would be unreadable due to the sheer amount of information required. I can't believe the problem has anything to do with the source footage as it is consistently occurring regardless of the footage format and origin.

It happens with audio, from multiple sources and in multiple formats, and with video, from multiple sources and in multiple formats.

Here is my computer info:

Processor - Intel(r) Core(TM) i7-8700 CPU @ 3.20GHz, 3.19 GHz
Installed RAM - 16.0 GB (15.8 usable)
System type - 64-bit operating system, x64-based processor
Windows edition - Windows 10 Home
Version - 21H1

Graphics Card - NVIDIA GeForce GTX 1060 6GB

Please let me know if you need any more info

@bluesguitarjimi As a matter of interest can you see if you can load and render this self contained Vegas Project (extract the zip file, open the .veg file located in the SampleProject 4K directory), Render using Nvenc using MagixAVC 4K25 template

https://www.dropbox.com/s/3i4xgnhl9fmc0je/BenchmarkProject4K.zip?dl=0

When my VP19b643 got sick I could not load and complete the render without crashing. Vp19b643 and first build of Vp20 are very similar. Also when editing in general, keep your task manager or similar displayed so as to keep an eye on ram usage. I had situations where 99% of ram got used . If you aren't looking at ram usage you wouldn't even consider it possible because it's not normal, it's a memory leak, a coding bug. That is going to cause a problem.

I ditched Vp19b643 and never had the memory problem since.

Side note, I will recommend

https://www.alcpu.com/CoreTemp/

to get temp,ram,load on the taskbar. I use it for ages.

@bluesguitarjimi, while that may be true, what are the formats when it does die? I sincerely doubt it happens "across every different format of video and every different source"

In Options - Preferences - File IO, if you uncheck "Legacy HEVC", does that help any?

Just thought I would try the Todd-b render on both V19(643) and V20. Both loaded the project with no issues and both rendered the file with no issues. Ram usage in V20 was around 11GB (out of 32) and in V19 16.3GB. But V20 was open when rendering with V19 so may have been using some ram.

@andyrpsmith I was using the project as a way to diagnose corruption taking place. When first installed the benchmark project worked fine, after a number of weeks, it started to get more unstable, crashing much more frequently. It is then I discovered I could no longer load the benchmark project without crashing. If that were to be the case, a reset would likely fix the problem, but for me I reverted back to VP19b550

Sad that the memory leak was never fixed in VP19 B643....

@bluesguitarjimi, while that may be true, what are the formats when it does die? I sincerely doubt it happens "across every different format of video and every different source"

In Options - Preferences - File IO, if you uncheck "Legacy HEVC", does that help any?

Hi

I'm afraid that, despite your sincere doubts, this is the truth.

Right now I use 1080 video filmed on an iphone 12. The crashing-past-a-certain-size happens with video filmed on a wide range of different formats that come from my colleagues' phones too. Previously it happened on video filmed on an iphone 8. Before that it happened on video filmed on a samsung galaxy and a sony alpha series camera. Before that it happened on footage filmed on a very basic sony digital camera, and on footage from a kindle fire.

I have changed and upgraded computers several times during my usage of Vegas (I started using a version of it when it was owned by sony in I think 2006), and my RAM usage is never anywhere near my computer's capabilities. I have used multiple cameras, computers and video formats, but the problem of constant crashing has remained. The one constant has been Vegas itself.

And just to underscore that the problem is within Vegas, not my video files or computer, I recently tried Adobe Premiere for a while. I hated it, and soon came back to Vegas - but it never crashed on me once, despite me making many videos of the same or larger size.

And yes, I have unchecked Legacy HEVC, and it has not stopped the crashing.

All of those phones have variable framerate footage which just isn't optimal for Vegas. Not blaming the user but that's how it is. Try to re-encode to short GOP (key interval of 1s) constant framerate AVC and see if that helps. I use Shutter Encoder for that (set GOP length under advanced).

Make sure your Intel® UHD Graphics 630 is set to decoding in preferences/ file io as I had stability issues with NVDEC in Vegas.

I'm mainly using 19.550 and still testing 20.

All of those phones have variable framerate footage which just isn't optimal for Vegas. Not blaming the user but that's how it is. Try to re-encode to short GOP (key interval of 1s) constant framerate AVC and see if that helps. I use Shutter Encoder for that (set GOP length under advanced).

Make sure your Intel® UHD Graphics 630 is set to decoding in preferences/ file io as I had stability issues with NVDEC in Vegas.

I'm mainly using 19.550 and still testing 20.

OK... but it also happens on complex audio-only mixes, in which there is no video.

It also happened on footage from a sony alpha camera which was not variable frame rate

I have set the 630 for decoding (it was already selected via the auto setting anyway) so I will see if that makes any difference.

Truth be told however, the fact that the crashing happens across computers, video types - and even on audio only projects - suggests to me that it's not a problem with the video types.

@RogerS, I've tested several variable frame rate cellphone video tests in Vegas. Nothing fancy, and Vegas worked well. Also webinars that I've had to edit, never an issue. I think that VFR cellphone videos are getting better without that wide swing in minimum and maximum frame rates.

@bluesguitarjimi sorry to say, I haven't experienced what you say is happening "across computers, video types - and audio only projects". I'm just not seeing the crashing or frequency you seem to be saying.

But I don't use Sony Alpha cameras, or footage from any, but Panasonic.

I've had a lot of crashes with the NVDEC decoder and VFR footage makes that more likely. You'll see bigger swings in low light where the camera cheats a bit with low framerates. And potentially long GOPs on top of that which Vegas also doesn't like.

AMD may be a different story but neither the OP nor I have such a GPU.
Media x GPU decoder makes a big difference in Vegas.

Understood. VFR video seems to be problematic not only with Vegas, but other software too.

Testing Vegas with VFR of 7-43fps from a cellphone, it played everything back without issue. But that was with no editing to it.

@bluesguitarjimi Iphones will automatically drop to 24fps from 30/60fps if it needs to when it's dark, depending on your settings. google 'auto fps iphone' find the option and turn it off, see if that helps. Your Iphone like other phones most likely drops frames also which Media Info will report as VFR even if you're recording outside in the middle of the day. Samsungs also have an auto fps option but it activates only if phone is recording at 60fps and needs more light, it changes fps to 30, but I don't think that's on by default.

@Reyfox It's not a problem on other NLE' with the limited testing I"ve done with submitted phone videos that don't play well on Vegas.

The problem recordings that every NLE has problems with is more like VFR zoom recordings where it holds the frame if it doesn't need to be updated or my security cameras that has an option to record between 0.25fps and 30fps dynamically(limited uses) depending on light levels(color night vision) as well as only updating the frame on change.