[Sean Michael]

Hi Edward, I’d be happy to collaborate sometime. This is a problem that seems to happen regularly on the latest build of VEGAS 19. The solution right now seems to be rebooting the entire project. After a fresh reboot, Pan/Crop will work for a while as intended — but the problem inevitably surfaces again after a while. Thanks for your comments, I would be able to post videos more frequently if I didn’t hit these time-killing issues! I may start outsourcing more of the editing in the near future because it has really been affecting our upload schedule.

[Sean Michael]

Thank you Setiawan, I will give this approach a try if matters get desperate. I would regret losing all of my other settings though.

[Sean Michael]

Just a quick update. Thanks to all who have replied to this thread.

Since my original post, a couple of major updates have been made to VEGAS 19 (the most recent is Build 532). Overall the program seems to be more stable for me now. I’m experiencing far fewer whiteouts and crashes. Crashes still happen occasionally but they are rare.

One key change to my workflow has been the use of proxy files. I’ve found that VEGAS struggles with the files produced by my Sony A7Siii (usually shot in 4k 10-bit color etc.). I am now creating proxy files for all of the Sony A7Siii files (a simple right click on the file and “Create Video Proxy”). It takes some extra time but the performance benefits seem to be worth it.

[Sean Michael]

Hi Edward, thank you very much for your kind note. Yes, I’m sure you have seen Titler Pro in my videos! I have used VEGAS pretty much exclusively on Long Long Honeymoon. Pretty much every video I’ve ever posted on the channel has been edited with some version of VEGAS. I like the way it handles many aspects of editing and agree it has usually seemed to be easy and intuitive.

I did go ahead and upgrade to version 19. I’ve got good news and bad news. Frankly I’m not a fan of the interface changes because they just made it harder to use (icons now visually blend together and are harder for my 50-something year old eyes to distinguish) but that’s a minor quibble. The good news is that I have experienced fewer whiteouts/crashes while editing in 19. This is promising! Alas, the bad news is that I’ve experienced crashing while rendering. For example, I was planning to post a new video tonight — I have been trying to render the video for several hours. It has crashed multiple times. I know a few render tricks — for example, to drag and drop the final project file into a fresh project timeline. But I am still working to render the project. It’s after 8PM EST so I will likely not post the video tonight as planned. Needless to say, this is very disappointing.

I agree that FCPX feels a lot more different than I would like. I do not look forward to learning the new interface (and for that matter, the Mac OS) but I’ve got to find a reliable solution that doesn’t leave me gnashing my teeth with every new project. My preference would be to stick with VEGAS but I am at a loss. Thanks again for your comments; yes that fire on I-24 was a day we will never forget.

[Sean Michael]

I ended up buying a new MacBook Pro (M1 Max!) and Final Cut Pro X. $4000 expense. Honestly I am intimidated by the learning curve of FCP X — it will take me years to attain a similar proficiency with this software.

I may give VEGAS 19 a shot while I bring myself up to speed with FCP. I’ll report back with regards to stability. I wish Magix would focus on stability, first and foremost. New features are useless if the software crashes every 15 minutes.

[Sean Michael]

Thanks for your replies. I have watched the video and made all of the suggested changes.

I edited for about an hour today before my first crash (sadly this is doing well for VEGAS 18).

During a typical editing crash, video preview playback freezes, then the program stalls. I get a program “Not Responding” message, the page goes grey, and I am completely unable to interact with the program. My only recourse is to shut down, reboot, and restore from the autosave file. A disruptive 5-10 minute process. This usually works until the next crash, which may happen at any time. I rarely get an error report since the program is simply frozen. I will check out the Vegas Creative forums and see if there are any other suggestions. In the past I’ve had better luck finding solutions from online forums than from corporate emails.

I do often mix different camera files in a typical project — for example, DJI drone / action camera footage, 10-bit Sony A7Siii footage, and Sony AX700 video camera footage. In the past VEGAS was a champ at ingesting different codecs (in fact this was a chief advantage in the early days). Perhaps that’s what’s tripping up the software now.

I don’t enjoy posting complaints. I certainly don’t relish the thought of leaving VEGAS behind and learning a new platform (not to mention transitioning all of my archived video content to the Mac platform) but I’m at my wit’s end. I was hoping that MAGIX would focus on stability/reliability but it doesn’t seem to be happening. Thanks again for your help.

[Sean Michael]

Thanks Steve for your comments. I am still having the crashing issues with 18. My hardware is very powerful (desktop is a 16-core AMD Ryzen 9 with 64 GB RAM, laptop is Intel(R) Core(TM) i7-10875H CPU with 32GB RAM) so I don’t think that is the issue. I have turned off GPU acceleration and maxed out the dynamic RAM allocation. Still crashes. The screen fades, the cursor starts spinning, and I get the dreaded “(Not Responding)” freeze. My only solution is to shut down everything and restart. The crashing happens every 15 minutes or so. I have set advanced save to save every 1 minute. I understand that there may be driver conflicts, but I do not know how to identify the conflict or change the drivers. Today I’m using my laptop, an Asus Zephyrus Duo GX550LWS-x579. I will doublecheck and update drivers, but again I don’t really know what drivers are causing the problem, or how to fix it. It would be helpful if Vegas at least displayed which driver caused the conflict.

[Sean Michael]

I upgraded to 18 from 13 (mainly to edit A7Siii files) and am regretting it. Most changes seem to be for the worse. It crashes much more frequently.

[Sean Michael]

Wow! Thanks Don, this fix seems to have worked! I really appreciate you and everyone else for taking the time to reply to this thread.

For future reference, if anyone else has this problem on Windows 10:

Open your Start menu and click the Settings button. From the Settings menu, choose Apps & Features. Enter “OpenCL” in the box labeled Search this list. If “Intel SDK for OpenCL” appears in the search results, select and uninstall it

[Sean Michael]

Thanks to everyone for your replies. Still no luck, but I will be working on the problem more today. The reason I know it was Catalyst Browse that caused the problem is that I use 3 different laptops to edit video… On two of the laptops I installed Catalyst Browse, and Vegas immediately began crashing. Thankfully I realized what was happening before installing Catalyst Browse on my 3rd laptop! So I at least still have one that works for editing.

I know it has something to do with OpenCL.dll and Vegas’ GPU-accelerated video processing. I would recommend VEGAS users avoid Catalyst Browse (at all costs!).