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

john_dennis wrote on 1/19/2026, 1:26 AM

Vegas Pro 9 did it right. It dis-allowed the Remove Selected Plug-in button...

... while Vegas Pro 10 introduced the possibility of the exception when the Remove Selected Plugin button was enabled even though the data in the field had changed.

3POINT wrote on 1/19/2026, 1:52 AM

Seems to me not an urgent to be fixed bug...when it took 13 Vegasversions to be discovered. I think that 99.99% of us use to change the volume of a clip by dragging the volume line of a clip and not by applying a volume fx to a clip.

BTW I cannot confirm your issue, I can remove the volume fx without crashing Vegas.

Dexcon wrote on 1/19/2026, 2:16 AM

I can confirm that this crash occurs in VP23, VP22 and VP16 BUT it only happens when removing the FX window after manually entering a volume value - it does not occur after changing the volume using the slider and then removing the FX window - and it doesn't occur if manually entering a volume value, clicking anywhere on the slider (so that the volume change takes effect) and then removing the FX window.

Sorry, but what I am finding hard to reconcile is why the FX needs to be removed immediately after making an adjustment to it. In the case of the Volume FX, I've found that I need to click on the slider (or close the FX window) for the manually entered volume value to take effect before being able to preview the adjusted volume level.