V22 239 cannot render project, crashes every time

Mindmatter wrote on 2/18/2025, 4:20 PM

Hi all
this is extremely annoying to say the least.
I cannot render my finished project, it crashes every single time between 54% and 57%, I have no idea why, as those error reports are too cryptic for the common mortal and leave you totally clueless.
10bit 4k XAVCI files from my Sony FX3. Rendering in HD in 32bit, plugins used: Vegas LUT filter, NB colorfast2, BCC magic sharp. I tried deleting BCC on all events, same result.

FWIW...:

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 239)
   Problem:             Unmanaged Exception (0x00000000)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 22.0\OpenColorIO_2_0.dll
   Fault Address:       0x00007FF93237B7FB
   Fault Offset:        0x000000000028B7FB

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
   Process Version:     Version 22.0 (Build 239)
   Process Description: VEGAS Pro
   Process Image Date: 2025-01-21 (Tue Jan 21) 22:08:50

Comments

RogerS wrote on 2/18/2025, 7:27 PM

Are you using both ACES and a LUT filter? It's really one or the other. (at least for transforms, I suppose you could add a look one at the end)

That the crash says open color io suggests a problem with ACES transforms

Mindmatter wrote on 2/19/2025, 3:03 AM

Thanks RogerS,
but I'm just using the Vegas LUT filter with a Phantom LUT.
EDIT:
I just checked the task manager , it's at 97% memory at the crash point. Something's off here.

RogerS wrote on 2/19/2025, 3:04 AM

What do you mean "just using the LUT filter"?

Can you please share a screenshot of your project properties?

RogerS wrote on 2/19/2025, 3:05 AM

That is it crashing with OpenColorIO suggests ACES is in use.
https://github.com/AcademySoftwareFoundation/OpenColorIO

Mindmatter wrote on 2/19/2025, 3:43 AM

I don't use ACES, although I found it to be the most color accurate transform.. I use the Vegas LUT filter in the track FX with a Phantom LUT. ACES is greyed out. I never use it as I work with LUTS to transform my LOG footage.

andyrpsmith wrote on 2/19/2025, 4:34 AM

https://www.vegascreativesoftware.info/us/forum/v22-render-crashes-at-39-bfx-error-code-25--147874/

Similar error in Vegas reported above too.

Mindmatter wrote on 2/19/2025, 4:35 AM

new attempt with build 192: total GPU crash, black screens etc etc.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 194)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Windows\SYSTEM32\VCRUNTIME140.dll
   Fault Address:       0x00007FFA93551703
   Fault Offset:        0x0000000000011703

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
   Process Version:     Version 22.0 (Build 194)
   Process Description: VEGAS Pro
   Process Image Date: 2024-10-22 (Tue Oct 22) 20:54:16

Dexcon wrote on 2/19/2025, 4:53 AM

Particularly if you have any event, track or project level FX where Vegas Pro's CGP and NBFX's CF2 are active at the same time, try deleting or just disabling the NB CF2 FX and do a new render to see if CF2 is the problem. The reason I mention this is that some time ago I found that a clash with VP's CGP and CF2 caused a problem - I can't recall if it was a render failure or just a bad render.

Even if not using VP's CGP, other color grading options such as a Vegas LUT might be clashing with CF2. If this doesn't change the situation, then CF2 can be rules out as you've already established with BCC FX.

Mindmatter wrote on 2/19/2025, 5:03 AM

OK so I just transferred the whole project to V21, copying all events and setting to the exact same state.

Rendered faster and without a glitch. So I'd say V22 has issues.
An observation was that task manager showed memory consistantly at around 68% while rendering, whereas V22 ramped itself up to 99% pretty fast and crashed at more or less 67 % of the render.
So unfortunately, it's back to V21 for me as of now. Can't have another day of troubleshooting.
Also, can the Vegas team please fix the " Vegas has stopped working" thing each time I quit Vegas?

RogerS wrote on 2/19/2025, 5:44 AM

I don't use ACES, although I found it to be the most color accurate transform.. I use the Vegas LUT filter in the track FX with a Phantom LUT. ACES is greyed out. I never use it as I work with LUTS to transform my LOG footage.

You couldn't share project properties? So you are rendering in 32-bit full mode with view transform off? I have FX3 footage and a NVIDIA GPU but not really enough info here to try to reproduce the issue.

VCRUNTIME140.dll is Visual C++. That's up to date?

There were reports of a memory leak with the LUT filter; haven't personally seen it as I use LUTs through the color grading panel which is far faster than the LUT Fx in VP 22.

Hopefully the crash reports are of use to the developers.

Mindmatter wrote on 2/20/2025, 4:02 AM

There were reports of a memory leak with the LUT filter; haven't personally seen it as I use LUTs through the color grading panel which is far faster than the LUT Fx in VP 22.

Thanks for that info, I'll try using the LUTs via the CGP., would be great if that's any faster.
Project properties:

Steve_Rhoden wrote on 2/20/2025, 6:28 AM

@Mindmatter Which build of Vegas 21 you went back to that rendered this without an issue?

Mindmatter wrote on 2/20/2025, 11:44 AM

@Mindmatter Which build of Vegas 21 you went back to that rendered this without an issue?

Build 315