Please Fix: Vegas 23 Audio fX Window Mis-operation Unhandled Exception

john_dennis wrote on 1/18/2026, 11:47 PM

After making a change to an audio fX (Volume, in this example), if a user strikes the "Remove Selected Plugin" button instead of the big red Close button,

she is greeted with this

Extra Information
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\gpu_video_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\fileio_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\persist.prefs
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\fileio_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\dx_video_grovel_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\svfx_video_grovel_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\ocio_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\dx_grovel_x64.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\vst_grovel.log
   File:                C:\Users\John\AppData\Local\VEGAS Pro\23.0\vegas_script_x64.log
   File:                C:\Users\John\Desktop\2023-03-20 Dance.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 302)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
   Fault Address:       0x00007FF77EDBA345
   Fault Offset:        0x000000000016A345

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
   Process Version:     Version 23.0 (Build 302)
   Process Description: VEGAS Pro
   Process Image Date:  2025-09-27 (Sat Sep 27) 09:42:20

Please handle this exception to normal operation even if you just put up a full screen message pointing out that I'm either a complete idiot or my mousing skills have deteriorated of late.

I checked earlier versions of Magix Vegas Pro until my arms got tired and I never got to a build that handled the exception gracefully.

@RogerS  @EricLNZ @VEGASDerek

Comments

No comments yet - be the first to write a comment...