Vegas Pro 21 - crashing when opening up Video Event FX

Wolfgang S. wrote on 5/15/2024, 2:09 PM

Please post us your computer specifications.

Do you use an AMD GPU? Which one? Driverversion?

nikola-herss wrote on 5/15/2024, 2:10 PM

Please post us your computer specifications.

Do you use an AMD GPU? Driverversion?

My bad. Here it is.

My PC setup:
CPU: AMD RYZEN 5 1600X (driver version 10.0.19041.4355)
Graphic card: Sapphire Radeon Nitro+ RX 580 4GB OC
Power Supply Unit: Seasonic S12II-520 - 520W
Internal disk: Seagate BarraCuda, 3,5"

Wolfgang S. wrote on 5/15/2024, 2:19 PM

Thank you!

And what is your AMD Radeon driver?

And - what type of footage do you use? Is it HD or 4K/UHD?

nikola-herss wrote on 5/15/2024, 2:50 PM

Thank you!

And what is your AMD Radeon driver?

And - what type of footage do you use? Is it HD or 4K/UHD?

Driver version AMD: 23.19.12-240220a-402263C-AMD-Software-Adrenalin-Edition
Driver version AMD for Windows:31.0.21912.14

Footage is full HD.

iEmby wrote on 5/15/2024, 3:00 PM

@Wolfgang S. @nikola-herss

my vegas also crashed when click on PAN & CROP tool on events.
in 300 it was working good.

my GPU is AMD Radeon RX 560 4GB

Wolfgang S. wrote on 5/15/2024, 3:03 PM

Indeed, the discussion has been about the Event FX bug, yet so far, there has been no mention of any issues with the Pan/Crop feature.

VEGASDerek wrote on 5/15/2024, 3:05 PM

Very likely the same problem. The issue has to do with pulling frames from the mxcompound plug...this is done at any number of places. The error reports show a number of different paths ending up in the same place which causes the crash. Our team is looking at this right now and we hope to be able to expedite a patch for this problem.

nikola-herss wrote on 5/15/2024, 3:09 PM

Indeed, the discussion has been about the Event FX bug, yet so far, there has been no mention of any issues with the Pan/Crop feature.

It doesnt matter if I click on Event FX or the Pan/Crop feature - both ways it crash :/

nikola-herss wrote on 5/15/2024, 3:11 PM

Very likely the same problem. The issue has to do with pulling frames from the mxcompound plug...this is done at any number of places. The error reports show a number of different paths ending up in the same place which causes the crash. Our team is looking at this right now and we hope to be able to expedite a patch for this problem.

Thank you for explanation. That would be amazing If there would be solution for this in the new patch. I will be looking forward to it.

iEmby wrote on 5/15/2024, 11:54 PM

Very likely the same problem. The issue has to do with pulling frames from the mxcompound plug...this is done at any number of places. The error reports show a number of different paths ending up in the same place which causes the crash. Our team is looking at this right now and we hope to be able to expedite a patch for this problem.

just wanna know sir, what do you mean by a patch, is this will be new update or emergency fix thing and how will we get it as an auto update while using 21_314 or will get offline setup too. and any information will be provided? for that when it will be issued by the team?

actually due to some major bugs i have to shift back to use 21_300, so i may not be get known about this patch comes or not... thats why i am asking..

Thank you.

RogerS wrote on 5/16/2024, 12:17 AM

A patch would be an update to 300 and 314 and it will notify you when it becomes available.

You'd also read about it here.

iEmby wrote on 5/16/2024, 12:23 AM

A patch would be an update to 300 and 314 and it will notify you when it becomes available.

You'd also read about it here.

Thats sounds great. Thankyou

NickHope wrote on 5/16/2024, 12:33 AM

This is affecting me too.

VEGAS Pro 21 build 314
Windows Version: 10 22H2
GPU: AMD Radeon VEGA 64
GPU Driver: Pro driver 22.Q4 (Driver Version: 22.20.27.09-230330a-390451C, AMD Windows Driver Version: 31.0.12044.3).

Steps to reproduce:

Options > Preferences > File I/O > Hardware Decoder To Use > Select Radeon RX Vega (or auto).
Options > Preferences > File I/O > Deselect Enable Legacy AVC decoding.
AVC MP4 file on the timeline, such as the 1920x1080 file from this page.
Open Video Event Pan/Crop or Video Event FX.
Crash with details below:

Extra Information
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\gpu_video_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\fileio_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\persist.prefs
   File:                C:\Users\nick\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\nick\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\dx_video_grovel_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\svfx_video_grovel_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\ocio_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\dx_grovel_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\vst_grovel.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\vegas_script_x64.log
   File:                C:\Users\nick\AppData\Local\VEGAS Pro\21.0\hub.log
   File:                D:\Dropbox\Documents\0-Vegas-projects\VEGAS-Pro-21\vp21-b314-event-fx-bug-test.vegProblem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 314)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Windows\SYSTEM32\VCRUNTIME140.dll
   Fault Address:       0x00007FF8785312B1
   Fault Offset:        0x00000000000112B1Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 314)
   Process Description: VEGAS Pro
   Process Image Date:  2024-05-06 (Mon May 06) 21:53:14

I have submitted a crash report.

WORKAROUNDS WHILE WE WAIT FOR A PATCH:

1. Options > Preferences > File I/O > Hardware Decoder To Use > Select Off > Restart.

(AVC clips will still be decoded by mxcompoundplug.dll but without hardware decoding.)

OR

2. Options > Preferences > File I/O > Select Enable Legacy AVC decoding > Restart.

(AVC clips will be decoded by the legacy so4compoundplug.dll. Note that there might be minor differences in how clips are decoded.)

OR

3. Roll back to VEGAS Pro 21 build 300.

Build 300 installer is here.

Note that projects saved in VP21 build 314 cannot be opened in earlier builds, so...

TAKE A BACKUP BEFORE SAVING PROJECTS IN BUILD 314!

I would recommend option #1, but if playback performance is poor then try #2.

iEmby wrote on 5/16/2024, 2:51 AM

rolling back 300 is best option for now.. thankyou

nikola-herss wrote on 5/16/2024, 3:13 AM

in build 300 it works fine. Thanks everyone for the help.

Gid wrote on 5/16/2024, 3:41 AM

@VEGASDerek @NickHope Hi, just got to say as a non-AMD GPU user I'm loving the (300) build, next to 0 crashes, & so far (314) is performing just as well.

I've been playing with the metallic dancer in your link, beat reactor, Pan/Crop ... pretty much whatever I want to do to it I can - 0 crashes. - (I had 1 crash with 4 Sapphire fxs applied, beat reactor on the track fx, I changed the preview to Good (Half) from Good (Auto) while it was playing, didn't wait for it to adjust & then tried adjusting an S_ fx. Sapphire fx are always a bit more 'temperamental' than any other fx on my PC, so I put that crash down to user error, Also the USB hardrive needs to wake up before they show thumbnails in the fx window, whether that is relevant to the crash I don't know.

bitman wrote on 5/16/2024, 3:59 AM

I also do not crash with the metallic dancer, probably because I am using an NVIDEA GPU, I wanted to ask/confirm this is only an issue with AMD GPU users, but since @Gid does not have an issue as well, it seems to point in that direction (at least for 2 persons so far)...

Wolfgang S. wrote on 5/16/2024, 4:04 AM

@Gid

do you see any issues with B 314 on your system? As non-AMD GPU user?

Nick's suggestion is not an actual solution; rather, it serves as a temporary workaround until the development team addresses the issue with AMD cards.

In addition, a lot of users had issues with e.g. MXF files with b 300 - so a rollback to earlier versions like b 187 is also an option for those MXF users.

Wolfgang S. wrote on 5/16/2024, 4:07 AM

I also do not crash with the metallic dancer, probably because I am using an NVIDEA GPU, I wanted to ask/confirm this is only an issue with AMD GPU users, but since @Gid does not have an issue as well, it seems to point in that direction (at least for 2 persons so far)...

@bitman

I also experience the same situation; there are no issues with my Nvidia-based systems, so I can stick with B314.

Peter_P wrote on 5/16/2024, 4:36 AM

Another workaround could be to use the 'Video FX' window and drag the FX to the event.

Gid wrote on 5/16/2024, 4:39 AM

@Wolfgang S. Hi, no problems that I can mention. The title of this post is 'crashing when opening up Video Event FX', later Pan/crop was mentioned & AMD GPU/AMD drivers was asked about so that maybe implied it was possibly an AMD issue but wasn't specifically mentioned. So my comment was just a general statemen for balance to say the list @NickHope gave to recreate the problem doesn't happen to me.... with Nvidia.

There's a problem with BCC+ corner pin keyframes that I've posted about but that's another issue, it could be my PC rather than a Vegas thing & it was in the (300) build but it could've been in previous version.

RogerS wrote on 5/16/2024, 4:42 AM

It appears to be an AMD-only issue as there aren't any reports of issues with NVIDIA/Intel (which is true on my two systems as well). I'm also seeing 314 work well.

NickHope wrote on 5/16/2024, 5:17 AM

Another workaround could be to use the 'Video FX' window and drag the FX to the event.

That does work, but if you then delete the FX, revealing the default Event Pan/Crop earlier in the chain, it still crashes. So it's a workaround but it's not very robust.

gabgilson wrote on 5/16/2024, 5:31 AM

So I have AMD 6700XT graphics and 5900x CPU. A new project in v21.314 works fine, and I don't get any crashes when I click on event fx or pan/crop!

In file i/o I have Auto for hardware decoder (so it's using the 6700xt) and legacy and experimental are both unchecked - i.e. not using legacy avc or experimental HEVC. This is with HEVC Sony 10 bit files.

I installed the latest AMD graphics driver yesterday, 24.5.1 (WHQL). But presumably everyone else has tried that. I wonder why I got lucky on this?

I had a problem yesterday with a v21.300 project that wouldn't open without crashing, but having reverted to 300, and resaved the project, then reinstalled 314 and opened up the project it's running OK so far. So I think that project file had just got confused in the migration.