Vegas Pro 22 Build 194 - keeps crashing during render

Rosled wrote on 12/18/2024, 2:33 PM

Vegas keeps crashing during render.

Here's the info :

 

Extra Information
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\fileio_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\persist.prefs
   File:                
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\dx_video_grovel_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\svfx_video_grovel_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\ocio_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\dx_grovel_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\vst_grovel.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\vegas_script_x64.log
   File:                C:\Users\Roll\AppData\Local\VEGAS Pro\22.0\hub.log
   File:                I:\GB\Vegas Pro\G&B Final Full (New Vegas Version).veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 194)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 22.0\OFX Video Plug-Ins\Vfx1.ofx.bundle\Contents\Win64\Vfx1.ofx
   Fault Address:       0x00007FFF2DD68687
   Fault Offset:        0x0000000000698687

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

Comments

RogerS wrote on 12/18/2024, 6:11 PM

Do you know what video Fx are in use (esp. as the point where the render crashes)?

Rosled wrote on 12/20/2024, 10:34 AM

I shot a wedding with 3 cameras - Here are the cameras, profiles and media info about the video files.

Sony A7IV - slog3
3840 * 2160 - 23.98fps
Data rate  - 229505kbps

GH4 - VLOG
3840 * 2160 - 24fps
95923kbps

GH5 - Natural
3840 * 2160 - 24fps
Data rate  - 149129kbps

 

In Vegas Pro 22, I edited the trailer (about 5mins long). Even though I had imported all videos from all 3 cameras, I only used footages from the Sony A7SIV. Here, I used the colour grading panel, added LUTS with the LUT filter and also used the sharpening FX. Upon rendering the trailer, I had no single issue. It was actually very smooth.

I proceeded to edit the full video (about 2 hours long). This is made up of footages from all 3 cameras. I copied the grade and video fx from the trailer and pasted it in the full video project. I then did some adjustments in the grade and also used the colour match fx.

Here are some screenshots with the project settings, render settings, pc specs and fx used.

Wolfgang S. wrote on 12/20/2024, 11:24 AM

Why do you use the CGP and the LUT plugin? The CGP could use LUTs too. But that is only one question.

One idea would be, to substitute the CGP by a combination of the LUT plugin and the classical color corrector. The CGP makes some troubles - but I cannot be sure if that is the issue really. I assume that this will be fixed by the new video engine.

The mixture of the framerates is not so great. For the future, I would try to stick to one overall frame rate, used in all cameras.

But to find out what is the real issue, we would need the possibility to repro that. In other words, we would need to identify much more in detail where the project crashes during rendering. Specific footage? Specific effects? And so on.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Steve_Rhoden wrote on 12/20/2024, 11:29 AM

If you have any long duration Adjustment Event in your project, temporarily remove them and see if the render completes..... Also from your crash report, an issue seems to be originating from a particular OFX Plugin you have installed

Rosled wrote on 12/20/2024, 11:39 AM

Why do you use the CGP and the LUT plugin? The CGP could use LUTs too. But that is only one question.

I combined both the CGP and LUT plugin because I don't have the possibility to add 2 luts in the CGP.

 

One idea would be, to substitute the CGP by a combination of the LUT plugin and the classical color corrector. The CGP makes some troubles - but I cannot be sure if that is the issue really. I assume that this will be fixed by the new video engine.

Ok I will give this a shot however I didn't have any issue with this when I edited the trailer which was 5mins long.

The mixture of the framerates is not so great. For the future, I would try to stick to one overall frame rate, used in all cameras.

Noted.

But to find out what is the real issue, we would need the possibility to repro that. In other words, we would need to identify much more in detail where the project crashes during rendering. Specific footage? Specific effects? And so on.

Initially, the project always crashed at 14% which was frame 23,095. This isn't the first frame of that cut so I found it strange that it still rendered a bit and crashed at a certain frame of the same video file cut and not the beginning of that video file cut.

After trying other things, it now crashes at 2%.

Both the frame at 2% and the frame at 14% are from the Sony cameras.

 

 

Rosled wrote on 12/20/2024, 11:43 AM

If you have any long duration Adjustment Event in your project, temporarily remove them and see if the render completes..... Also from your crash report, an issue seems to be originating from a particular OFX Plugin you have installed

What I've noticed is that when I only select a portion of the exact frame where it crashes at, say about 20seconds, it renders fine without problem.

The entire video is 2hours.

Wolfgang S. wrote on 12/20/2024, 2:00 PM

If you see a crash at a specific frame number, as at 23095 or whatever number are at 2%, then the question is what comes after 23095. Is it at the beginning of a cut/another event/a change in framerate? The best what you can do is to explore that.

It could also be a complex counteraction - something that you have in the timeline interacting with specific settings, e.g in the project settings.

If the crash happens with specific clip, as you say Sony slog3 footage, you could check which clip that is - and render that with tools like the Shutterencoder to quite robust intermediates - for example ProRes. It could also be a damaged clip.

Or you try to take the clip where Vegas crashes, and test what happens if you put this clip in the timeline - and render it alone. Does it crash too? Add the effects, same project settings - it is a trial and error test.
 

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems