When did that come out?

About an hour ago. When I opened VP19, the update window popped up with the Perform Update Now button.

Maybe today as it's a Monday. Expect an "official announcement" from Madison, WI, US later today.

@walter-i.  ... that screen shot is not the one I sent to Support. The one I sent was a crash report with Mocha Pro as the fault module, and it did have an explanation about what was happening and the extra information was also ticked. Unfortunately, I couldn't add a pic of the vegas190.exe fault module so I used it here as it may get back to Support if they are monitoring the forum which I understand that they do.

I am also having this issue, completely unusuable, crashes right on startup. We're off to a pretty bad start with their new update system. It was working perfectly fine before the update.

Here's my crash report.

Extra Information
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\fileio_x64.log
   File:                C:\Users\johni\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\johni\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\dx_video_grovel_x64.log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_video_grovel_x64.log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (0, Multiple Contexts).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (0, Filter).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (1, Multiple Contexts).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (1, Filter).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Upscale' (2, Multiple Contexts).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Upscale' (2, Filter).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'com.NewBlue.Titler2.0' (0, Multiple Contexts).log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\ocio_x64.log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\dx_grovel_x64.log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\vegas_script_x64.log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\gpu_video_x64.log
   File:                C:\Users\johni\AppData\Local\VEGAS Pro\19.0\hub.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 19.0 (Build 361)
   Problem:             Unmanaged Exception (0xe0434352)
   Fault Module:        C:\WINDOWS\System32\KERNELBASE.dll
   Fault Address:       0x00007FF8D5E44ED9
   Fault Offset:        0x0000000000034ED9

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
   Process Version:     Version 19.0 (Build 361)
   Process Description: VEGAS Pro
   Process Image Date:  2021-09-02 (Thu Sep 02) 19:28:28

Crash on startup and shutdown don't seem the same. The exception # and fault addresses are also different.

Shutdown might be something interfering with Vegas? Are there other plugins installed?

No crash on start up for me or on close down. Takes a while to load at the creating windows stage. Does loose the UI when playing my projects but I expected that as the fix for this is coming in next update.

Are there other plugins installed?

Lots - BCC, Mocha Pro, NBFX, Neat. But I'm not inclined to uninstall and then reinstall them all. It would seem a lot easier to go back to VP19 b341 and then wait for the next update. In any event, the extra information on the crash report seems to be limited to Vegas Pro issues:

It actually seems rather similar to the one posted above by John-Ivar.

Just uninstalled and reverted to the old 341 build. Luckily, their installer app will still install the 341 build, if anyone is wondering how to revert. Everything works as before now. This is a shame, though.

I'd suggest waiting to see if there are any official comments on this situation before updating to the latest build. I usually always update to the latest version, but unfortunately can't complete my work if I update to the 361 build.


(Screenshot from the newly installed old 341 build).


(You might not want to hit that update button if you have critical projects going on right now)

@Dexcon - Been meaning to post this. I too was getting intermittent crashes and whiteouts, until I purposefully setup the VP Saving Utility. If you’ve done this, and you still get this issues, then ignore me.

OK, for me so far, hoping for the best, but expecting the same as others have reported. Anybody know what the changes are in 361?

Anybody know what the changes are in 361?

There's a button on the update window that provides the following:

Features

· Update to OpenVino 1.4

· Danish voice added to Text to Speech

· Added a more accurate optical flow mode for the Slow Motion FX

· Realtime Optical Flow for the Slow Motion FX

Bug Fixes

· Fixed crash when undo is used on an Audio Effect during playback

· Hub Explorer will now properly update after a VEGAS Hub download

· Fixed crash on startup when Hub Window is open by default

· Interacts for the Bezier Mask now work properly after motion analysis

· Link in login error message for non-365 users is now clickable

· Crash when dropping data from the Motion Tracking panel is fixed

· Arrow keys now work properly in the FX Plugins windows

· Fixed issue with the deactivation menu item and have now returned it to the Help menu

· Waveforms for audio events on the timeline are visible

· File Explorer will no longer crash when refreshing with no folder selected

· Fixed crash that could occur when using the Upscaler plugin

· Improved the search functionality of the FX Plugins windows

· Errors that may occur on some systems when attempting to burn a BluRay disc have been resolved

· Problem where Pre-Render scrambles the image has been resolved

· Made names of the Camera LUTs in the Color Grading panel more readable

· Fixed issues discovered in beta testing of the Blackmagic RAW decoder

· No error will now occur when importing an SRT subtitle file that has two consecutive lines empty lines

· Line 255 no longer goes missing in the Histogram window

· Artifacts are no longer left behind on the Vectorscope window

· Issue with black frames when using HEVC media is resolved

· Missing icons and keyframe symbols in the FX editor while in Light or White interface modes is now resolved

· The Color Grading panel now properly invalidates pre-rendered parts of the timeline

· Issues with the highlight and alignment of buttons in the Track Header have been resolved.

· Correct icon is now being used for opening the Media Generator editor

· Now using the proper file icons in the Project Media window when in List view

· Reset of the Color Grading panel now properly resets the Look LUT

· The timeline is put into focus after a Project Note is selected and the cursor is moved the the associated timecode

· The Auto Adjustments menu now indicates with preset is currently selected

· Fixed orientation detection issues with some media

· Fixed crash when reading MTS files with 5.1 LPCM audio

· Issue where drag and drop does not work after a render has been resolved

· Double clicking on the title bar of the Pan/Crop window when it is floating now works as expected

· Properly scaled the fade handles, opacity handle and the loop notches for High DPI displays

· Event buttons will no longer scroll off the right side of the timeline

@Grazie  ... VP Saving Utility ... please forgive my ignorance, but what is the VP Saving Utitlity? I can't recall seeing it as a menu option in VP, so you've got me baffled (not there's anything unusual about me being baffled).

@Dexcon - It’s the new option under either under Prefs or Tools, sorry not on PC.

Update. I just installed VP18 b341 on my laptop and it works fine. After a long DL, b361 was installed via the update window - and it also works fine. On the laptop, there are no 3rd party FX at all. Also, AI Coloization works well.

Thanks @Grazie  ... I'll do a search for it soon.

If you mean "VEGAS Advanced Save Utility", please read this comment.

I have just tried the Video Stabilization, before the update I thought it was a major improvement, but with 361, it's unusable, It seems they have gone backwards with this one!

I've got the same crash problem. I can't open anything. I'll try to reinstall Build 341 to continue working and hope it's sorted soon. I cannot understand how they failed to identify this before release.

@walter-i.  ... that screen shot is not the one I sent to Support. The one I sent was a crash report with Mocha Pro as the fault module, and it did have an explanation about what was happening and the extra information was also ticked. Unfortunately, I couldn't add a pic of the vegas190.exe fault module so I used it here as it may get back to Support if they are monitoring the forum which I understand that they do.

@Dexcon
You are very quick - I deleted my post a minute after I pressed "COMMENT" because I realised that I had written nonsense.
Please excuse me!

No crash here, getting in and out of Vegas (I have Vegas post, perpetual) - 361,

I have not tried to save any project yet, just goofing about and exit. No crashes so far.

Updated and no crash problem here- wonder what is common about the systems where it occurs?

@walter-i.  ...

"... because I realised that I had written nonsense."

No, not all. I thought that it was a reasonable point. And I hadn't pointed out in my original post that the image in my post was not representative of what I had sent to Support - which is why I left the later explanatory comment on the forum just in case anybody else drew the same conclusion. All is good. Cheers.

All is good. Cheers.

@Dexcon Cheers ! 👍