Vegas 22: Crashing when rendering

James-Segwell wrote on 9/11/2024, 12:25 PM

Computer details: Lenovo laptop - Ryzen 9 5900HX - NVIDIA RTX 3060 (+ embedded AMD graphics) - 32GB RAM - 1TB SSD - Windows 10 Pro 22H2.

I have tried Vegas 19, 20, 21, 22 (legit versions). I have downgraded/upgraded NVIDIA graphics drivers.

The problem still persists: Vegas crashes when clicking on rendering. On a fresh install, with default settings, it renders the first time, but after I close, and restart Vegas, the (rendering) crash happens. I've tried so many different online tips/tricks.

I also work with another video editor, with no problems. Vegas has some things the other editor doesn't have, and vise-versa, hence why I like working with both.

Interestingly, I have an old portable Vegas 10 version, which works flawlessly. Food for thought.

I can be a very patient person, so if anyone has some suggestions, I'd be thankful.

Back to post

Comments

EricLNZ wrote on 9/28/2024, 1:07 AM

Hopefully the formats it decodes can be migrated to new decoders.

Provided the transparency provided by some MOV files can be maintained. This was the great advantage of some files such as those encoded with Format ID PNG.

To my limited knowledge Quicktime is only required for MOV files where the Format ID is identified as JPEG or PNG encoded video You don't need QT for MOV H264/AVC encoded import.

Xectis wrote on 9/28/2024, 4:12 AM

Thank you all for your contribution to the subject. I have no doubt Magix is aware how important Vegas is, as a video editor.

hurricane1951 wrote on 8/9/2025, 11:48 PM

I'm often amazed at the smart people who seem to know the technical details of Vegas sow well. This problem (Vegas crashing when attempting to render) has plagued me ever since I first installed version 22. I've tried so many things without success, pinned so many hopes that subsequent patches would fix it, that I just got into the habit of saving and closing any project that I just edited. While not a bad idea in itself, it was annoying.

Deleting the x86 folder made all the difference, and I would never have thought of it on my own. A tremendous thanks for this fix.