I'll check about the media, but I don't usually get to the crash stage. It just hangs.

I've "fixed" the green screen issue, and now I have a memory leak issue. The usage just grows and grows until everything stops. Can't seem to disable GPU acceleration, as then it says a file "has changed too much" or something like it and it doesn't play that video track anymore...

For the hang you can type in "reliability" in the Windows search bar and see what the reliability history says for the crash. You can also make VEGAS do crash reports when it hangs by holding shift, going to the options menu and clicking internal at bottom. Search for "hang" and change false to true.

How did you "fix" the green screen issue?

The only memory leak I'm aware of is with the LUT Fx. I'd use the color grading panel instead of that. Is something else triggering the leak or are you using that Fx?

@sbrx That is not normal behaviour for Vegas Pro 22, it means that Vegas is having conflicting issues with your RX 580, Ryzen 5 2600 Graphics Card or its driver etc...... I can't be more specific than that because i don't know the exact details of your system configurations.

For the hang you can type in "reliability" in the Windows search bar and see what the reliability history says for the crash. You can also make VEGAS do crash reports when it hangs by holding shift, going to the options menu and clicking internal at bottom. Search for "hang" and change false to true.

How did you "fix" the green screen issue?

The only memory leak I'm aware of is with the LUT Fx. I'd use the color grading panel instead of that. Is something else triggering the leak or are you using that Fx?

This was one of the crashes, according to Reliability feature in Windows:

Descrição
A problem caused this program to stop interacting with Windows.
Caminho de Aplicação Com Falha:    G:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe

Assinatura do problema
Nome do Evento de Problema:    AppHangB1
Application Name:    vegas220.exe
Application Version:    22.0.0.243
Application Timestamp:    67c5d94e
Hang Signature:    308a
Hang Type:    134217729
Versão do SO:    10.0.19045.2.0.0.256.48
ID de Região:    2070
Additional Hang Signature 1:    308a61d2979112f2ccddbf0299685e01
Additional Hang Signature 2:    30d7
Additional Hang Signature 3:    30d78e2b60daafa4d0fb3ecc0cf0d98f
Additional Hang Signature 4:    346c
Additional Hang Signature 5:    346ce90843c04d114793fe40e56d88f2
Additional Hang Signature 6:    d38a
Additional Hang Signature 7:    d38ad42d920b7d5fc126181e6fe2c4f5
 

Doesn't seem to provide a lot of information.

As for the fix, honestly, I don't know. I did many things, including updating drivers, disabling GPU acceleration, enabling AVC legacy, disabling dynamic ram. Now, it doesn't crash, but just keeps raising the memory usage until it reaches 99%, and then it slows down, to the point where it renders at 1 fps, which is basically nothing and I cancel it.

I tried rendering in chunks, but even that is problematic. It finishes, but about 2/3 of the render, the video glitches:

I don't know what else to do. I do not use LUT plugins, so that is not the cause for the memory leak.

I agree this problem report doesn't provide much information. I'd file an official support request (scroll back up to the top and click support) and hopefully the specific crash message can help them.

Please provide mediainfo, too- usually success in VEGAS starts from using easy to edit media. If yours is problematic it's easy to convert it in batch with a free tool like ShutterEncoder. https://www.shutterencoder.com

Convert to output format h264 with GOP set to your framerate in the advanced settings should edit really well. ProRes works great, too.

There was another user here who had issues with his RX 470 GPU, but never got back to whether the drivers were updated to the current ones. Before I updated my GPU to the RX 6700XT, I ran with the RX480 for a long time without any issues, and with some fairly complex video editing. What driver version did you update to?

Looking at the memory usage, it is showing 5.2GB used by Vegas in your rendering. How long is the project, and what effects are used (if any), and what created the video files? And have you updated to the latest version of VP22? I don't seem to remember 243 being a version that is listed HERE or HERE so where did you get this version?

Descrição
A problem caused this program to stop interacting with Windows.
Caminho de Aplicação Com Falha:    G:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe

Assinatura do problema
Nome do Evento de Problema:    AppHangB1
Application Name:    vegas220.exe
Application Version:    22.0.0.243
Application Timestamp:    67c5d94e
Hang Signature:    308a
Hang Type:    134217729
Versão do SO:    10.0.19045.2.0.0.256.48
ID de Região:    2070
Additional Hang Signature 1:    308a61d2979112f2ccddbf0299685e01
Additional Hang Signature 2:    30d7
Additional Hang Signature 3:    30d78e2b60daafa4d0fb3ecc0cf0d98f
Additional Hang Signature 4:    346c
Additional Hang Signature 5:    346ce90843c04d114793fe40e56d88f2
Additional Hang Signature 6:    d38a
Additional Hang Signature 7:    d38ad42d920b7d5fc126181e6fe2c4f5

I don't seem to remember 243 being a version that is listed HERE or HERE so where did you get this version?

 

@Reyfox @sbrx 

UPDATE BETA RELEASE: VEGAS Pro 22 BETA Build 243 Feedback

IMPORTANT INFORMATION 

This is beta software that may still contain known and unknown issues. Do not use this, or any beta software, to work on critical projects 

@Gid my bad... so busy with video and work, I tend to forget these, along with other important things.

Apologies to everyone.

It is true - I'm using the beta version right now. Funnily enough, I tried the beta version to fix another issue I was having. I'm currently exporting chunks of 6 minutes and will merge them at the end, but after that I will reinstall everything with the main version. And if that's what is indeed causing the issue, when I will own my mistake, but honestly it seems weird. I'll let you know. @RogerS I will also post the media info on the 2 video clips that I'm using. One is a screencapture using OBS, the other is a H264 at 12 MBPS recording with my OnePlus 11 Android phone, using Blackmagic Camera app. The only thing weird with these videos, at first glance, is that the Android one is recorded at 30,257 FPS. Usually I see 29.XXX, but maybe this is normal.

Another thing that I'm noting - I have to restart Vegas every time I want to do a new render, since the RAM is kept almost at full capacity after the render is completed.

Here's the info of my latest render:

• 6 minutes of video, render of 530 MB using the AMD VCE profile.
• average fps: 16.5
• memory usage started at 1.8 and ended at 10.84 GB
• task manager reported 92% of RAM usage at the end, 11 GB just for Vegas. I do not have other applications open, just the usual background stuff.

@sbrx thanks for the additional information. If at all possible, can you provide to the cloud, a few sample clips to download and test?

@sbrx thanks for the additional information. If at all possible, can you provide to the cloud, a few sample clips to download and test?

of course - is it ok to record new ones using the same phone and settings?

@sbrx Please ignore the RAM usage. This is no bug or memory leak. VEGAS tries to keep the used frame buffers to support faster rendering. In the case a different application needs some memory VEGAS will release it.

@sbrx Please ignore the RAM usage. This is no bug or memory leak. VEGAS tries to keep the used frame buffers to support faster rendering. In the case a different application needs some memory VEGAS will release it.

But if the render grinds to a crawl when the memory reaches 99% of utilization, should it really be ignored?

Additonally, I've tried 10 minute renders. They complete, but at minute 6:30 or around it starts glitching. That's around the stage when RAM usage reaches 95% utilization during the render process.

A green or red screen is always a hint that your gpu is in trouble. You and VEGAS are in conflict with the GPU (driver, memory, hardware encoder/decoder).

@sbrx Please ignore the RAM usage. This is no bug or memory leak. VEGAS tries to keep the used frame buffers to support faster rendering. In the case a different application needs some memory VEGAS will release it.

But if the render grinds to a crawl when the memory reaches 99% of utilization, should it really be ignored?

Additonally, I've tried 10 minute renders. They complete, but at minute 6:30 or around it starts glitching. That's around the stage when RAM usage reaches 95% utilization during the render process.

Can you reproduce this with a simple file? Can you give us some reproducable steps... like

• add this clip to the timeline (link)
• add this effect
• click render with XYZ
• crash, glitch ect.