No rhyme or reason to it. 20 crashes in a day more times than 19 did at ALL. I LOVED how stable 19 was - now, my monitors are blacking out, the program is crashing a lot - and all over the place - during slip editing, timeline nav, adjust the level of a track - freeze and crash.
Just updated studio drivers (3060i).
Sorry, but thus far Vegas Pro 20 has proved to be extremely stable for me. I even forget to do regular saves as I used to have to do in years past.
@Jessariah67
Now and than I get a freeze, but most of the time I know what the reason is and a little change in settings helps.
I would like to help you but the information you are giving is too few, f.i. what means this:
Just updated studio drivers (3060i).
At your profile I read you have the Nvidia 1060, so ????????????
I'm mainly having white out freezes that are somewhat unpredictable and guaranteed crashes if I leave VP 20 open and do something else for more than a few minutes.
Can't really say if it's Vegas as Windows keeps changing things as well.
No crashing or freezing issues here. Have it running on a laptop as old as dirt using an intel celeron processor.
Regular windows updates often causes those issues also.
I just had a whole system-weirdness-thing with my graphics cards. Somehow, reinstalling drivers and rebooting a few times has ironed things out. Very odd...
Things seem to be ok now.
Yes, I haven't updated - I'm on an i9 / 3060i now.
NOT blaming this on VP20 - just sharing to follow up.
So, I moved back to VP19, and everything seems fine. Open VP20 to check a few new things I had done (to rebuild in 19) and as soon as I started moving around - everything went black again. Closed 20, and everything seems stable again - including inside VP19.
The irony of this is, I NEVER upgrade immediately - I always wait, cuz I'm not "in a hurry" for a feature. Then VST3 support comes along...
In the middle of a job, so I'll probably wait for the next update. I just don't know how it would wreck havoc on my monitors, but nothing else is giving me any issues.
Yes, Vegas 20 build 136 crashes all the time for me. I've filed support and posted thread on this. I've opened the dump file for the crash in the debugger and it's a problem with MXVideoAllocator. Vegas 19 build 550 doesn't have this problem. Sucks I pretty much can't use 20 at all to edit H265 video.
I have Vegas 20 Post 365 and am having problems starting the program. Every time I start Vegas it starts then when it gets to scanning for VST plugins Vegas crashes. A error report comes up to send to Magix. If I reboot my PC Vegas starts OK. Its the 2nd or 3rd start that the program crashes at VST plugin. If I hold Shift-Ctrl Vegas will restart without crashing. I am in contact with support they have offered 3 solutions to the problem with none of them working.
So tonight I uninstalled all of Vegas Post with Revo Uninstaller, reinstalled Vegas and now when the splash screen gets to scanning for VST Plugins at between 50 to 75% Vegas crashes with no error report, splash screen just disappears.
I then uninstalled the AMD Pro drivers ( Latest one from AMD) I used DDU went into safe mode and Vegas starts perfect in safe mode. I started it numerous times and started without any problems. I get back into Windows 11 using the MS basic driver and Vegas started 10 different times with no crashes. I then installed the AMD driver, I installed the driver only, and then tried the full installation package and both times after restart Vegas starts fine the first time then crashes after that searching for VST plugins. ( I have no third party VST plugins installed)
Vegas 19 Post had no problems starting with these same Pro drivers. I am still waiting on support to see if they can figure this out. I did send them this report.
Well, I'm back to problems again in VP19 as well, but I'm thinking I might have it isolated to screen capture footage that I did with Movavi (and older version). Those files "flash black" like some files do sometimes. They were also VFR, but I'm not sure that would be an issue. The problems seemed to start when I started using the original footage. I only did that in 20. When I moved to 19 (with an EDL file), it started happening again. I rerendered the originals with the Magix AVC that I always render out in, and replaced them.
All drivers are up to date. One crash so far, but it didn't send my monitors into a hissy fit, and the rest of the system stayed stable. So far, so good.
I frequently get "whiteout" crashes just as I always have with every version of Vegas I have used and with every machine I have used it on. I have addressed all the usual suspects such as setting "RAM Preview" to zero and disabling the internal Open GL interop setting to no avail. I have an Nvidia RTX 2060 GPU and I have changed the drivers to the Nvidia "Studio" drivers from the "Gaming" drivers with no real improvement. My CPU is an AMD Ryzen 9 3900X with 64GB of RAM running Windows 11. Vegas' RAM and CPU usage on my system is minimal.
The crashes appear to occur and random times and do not directly correlate to the action I am performing. The program just goes non-responsive at random times. Sometimes during timeline editing and sometimes during rendering and sometimes during timeline playback.
There is and has been something inherently wrong with Vegas for many years as I believe I started with something like Vegas 8 back in the Sony days. It seems about time that these stability issues are addressed. I would be happy to work with the Vegas team to provide information to finally isolate and kill these bugs.
Having said all this, I am still totally committed to Vegas, and I just tolerate the crashes, surviving with frequent and incessant saves.
A version of Vegas that does not crash would be a miracle at this point...
@Alan-Kraemer
Which type of sourcefiles do you use when it crashes?
It has been pretty much everything over the years, but now the media is primarily iPhone video at 1080p (Quiicktime mp4 at 29.97fps). Audio AAC LC from the iPhone is included for slating and reference, but my primarily audio is .wav PCM files at 24/48. Generally, .jpg images are also included from the iPhone. Resolution is 4032 x 2268 (16:9).
May not be a problem, so what might be the reason?
Can you show here screenshots of Options/PreferencesVideo and Options/Preferences/File I/O ?
Yes, Vegas 20 build 136 crashes all the time for me. I've filed support and posted thread on this. I've opened the dump file for the crash in the debugger and it's a problem with MXVideoAllocator. Vegas 19 build 550 doesn't have this problem. Sucks I pretty much can't use 20 at all to edit H265 video.
@baksideDisaster_Flicks Other users also seem to be having issues with HEVC and crashes in VP 19 643 to present. Can you provide any more details about the type of footage you use and what triggers a crash? If you already shared this with support no need to do it again.
@Alan-Kraemer
Thank you, nothing wrong as far as I can see.
I don't have any experience with QT files, maybe someone else can help you further, sorry.
Alan, HEVC and NVDEC isn't a happy combination in Vegas now. Comsider setting the iPhone to compatibility mode or use software to convert to AVC before bringing it into Vegas Then put dynamic ram preview back to 5 percent to improve performance.
I have problems with VP20 freezing and going to white screen randomly. I can't correlate it to any action. Really disappointed that this mature product isn't more stable. I'm editing 4K/30p MP4 files.
@Jim-Mickol
Please create a separate thread and provide as much information as possible from your system and your used files using "Mediainfo".
https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/
You are also welcome to add your system data to your profile under "Signature", then they are always easy to find for any helper in future requests.
No rhyme or reason to it. 20 crashes in a day more times than 19 did at ALL. I LOVED how stable 19 was - now, my monitors are blacking out, the program is crashing a lot - and all over the place - during slip editing, timeline nav, adjust the level of a track - freeze and crash.
Just updated studio drivers (3060i).
I never had 19 crash .20 crashed last night when I grabbed the end of a clip and drag to shorten it . So is 20 really an upgrade . Think I will start phasing out of vegas and go to DaVinci. Vegas has crashed for years.I work as a news stringer I don't have time for vegas' BS.
I never had 19 crash
Vegas has crashed for years.
Which is it?
20 crashed last night when I grabbed the end of a clip and drag to shorten it
If that's all it takes to get you to want to switch to Resolve, I have bad news for you... Resolve crashes sometimes too.
After all these years I may have found a solution to all these crashes. Start Vegas then using the details pane of the task manager in Windows 10 or 11 right click on the Vegas executable and set "Priority" to "High". I have not had a single crash after doing this. Unfortunately, this setting is not persistent, so you have to do it manually each time you launch. To solve this issue, create a shortcut and paste the string below into the "Target" box. Then always launch using the shortcut.
%windir%\system32\cmd.exe /c start "vegas200.exe" /high "C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe"
I would be interested to hear if this solves the problem on your systems as well.
After all these years I may have found a solution to all these crashes. Start Vegas then using the details pane of the task manager in Windows 10 or 11 right click on the Vegas executable and set "Priority" to "High". I have not had a single crash after doing this. Unfortunately, this setting is not persistent, so you have to do it manually each time you launch. To solve this issue, create a shortcut and paste the string below into the "Target" box. Then always launch using the shortcut.
%windir%\system32\cmd.exe /c start "vegas200.exe" /high "C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe"
I would be interested to hear if this solves the problem on your systems as well.
Unfortunately this is not the case, I have set the affinity for Vegas to high for some time (there is a small utility on the internet that allows the affinity setting to be maintained) and have seen many white screen not responding and crashes.