Render crawls with a green screen on the preview. I hate this software

sbrx wrote on 5/21/2025, 12:43 PM

I don't know what to do anymore. I'm trying to render a video with around 28 minutes, doesn't have a lot of FX but they are continuous. It reaches 20% and the preview goes green. Then it slows to a crawl. I tried software rendering, hardware rendering, less FX, etc, same result.

I have Vegas Pro 22. I'm tired of this stupid software. It's buggy, crashes often, it's slow, and when the damn video is complete, it doesn't render. I have the minimum requirements for this software - 16 GB of RAM, RX 580, Ryzen 5 2600. I'm working on 1080p video.

I would ask for a refund if I could - I bought this software a couple of months ago to start working on YouTube videos. Thank all the saints that I don't actually have to make a living of this software. Vegas 13 used to work a whole lot better than 22.

It's just unbelievable. This is a screenshot - I had to go caveman to take it because Vegas brings the computer to a halt.

Back to post

Comments

Reyfox wrote on 5/23/2025, 8:31 AM

I added to 5 clips on the timeline, and even twice to one clip Autolooks and I was still able to do anything. My GPU RAM usage (with Firefox and Brave open) topped at 11.8GB and never went higher. It even dropped to 11.6GB.

I looped the playback to see if I could get it to go to a point of crash, nope. Never a crash.

Now System RAM usage continued to creep upward with each playback. But when I would stop the playback, I could see the System RAM slowly drop.

sbrx wrote on 5/23/2025, 8:32 AM

Google -

Yes, Vegas Pro's "Auto Looks" function utilizes Look-Up Tables (LUTs) to automatically apply color grading presets to your video footage. LUTs are essentially a set of instructions that tell the software how to modify colors and tones in your video.

Sorry Gid, I had no clue Autolooks used LUTs.

Reyfox wrote on 5/23/2025, 8:52 AM

Ok... a further test. I have 7 4K clips on the timeline from one of my videos. The clips also have other effects on them such as proDAD's Mercalli V6, Picture Enhanzr on two of the clips,

With nothing running except antivirus stuff, GPU usage at desktop is 0.8GB. I load my project into VP22 B250 and it goes up to 7.8GB GPU RAM. I add Autolooks to 8 events on the timeline totally 1 minute in length, loop the playback and GPU RAM never exceeded 11.7GB after playing the timeline back 8 times, Preview was Preview>Half, 25P with cross dissolve transitions between all the clips tested.

I could continue on doing anything else I wanted in the project. No crash.

RogerS wrote on 5/23/2025, 8:56 AM

As a workaround what if you use the look LUT function in the color grading panel? I haven't see a memory leak with the CGP.

Gid wrote on 5/23/2025, 9:11 AM

For me on brief testing with Auto Looks the RAM usage is dependant on how much Dynamic Ram I have set, it does continue to rise as the clip plays but only to the amount set in DR. I have too much RAM (256Gb) to be able to test whether it would eventually cause a crash or not, I'd prob have to set DR @ 100% which I'm not going to do.

RogerS wrote on 5/23/2025, 3:37 PM

I was able to replicate the issue and fill up all of my ram with just the autolooks filter. I used the same project I had tested the LUT filter before with. This is with my RTX 4060 laptop so it's not GPU specific.

RogerS wrote on 5/23/2025, 5:22 PM

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.

@VEGASPascal It's the same issue users reported with the LUT filter in VP 22.243 link, this time with the autolooks Fx, which presumably works the same way.

Please take the project I shared previously on this topic link and just put the timeline on repeat play and watch the ram fill up. Swap the LUT Fx for autolooks and the same thing happens.