Crashing in pro 18 build 527

gruva wrote on 10/4/2023, 7:15 AM

Hi,

To put it simply, it's crashing during rendering at exactly the same place.
I've already read soooo many articles asking me to turn off graphic acc/turn it on to stop the program crashes or to switch off graphic acc in the render template or render using a different template (no joy). I've increased the ram allocation and alsorts.

I also tried just rendering the section it stopped on (and a little either side of it) this gave no crash. Is there anyway to transfer everything to a new project and start over? at this stage it feels like the project is corrupted, or maybe on of the videos in the file, but I'm at a loss.
Any clues welcome

Comments

gruva wrote on 10/4/2023, 7:30 AM

Extra Information
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\fileio_x64.log
   File:                C:\Users\gruva\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\gruva\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\dx_video_grovel_x64.log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\svfx_video_grovel_x64.log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (0, Multiple Contexts).log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (0, Filter).log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (1, Multiple Contexts).log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (1, Filter).log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\ocio_x64.log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\dx_grovel_x64.log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\vegas_script_x64.log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\gpu_video_x64.log
   File:                C:\Users\gruva\AppData\Local\VEGAS Pro\18.0\hub.log
   File:                C:\Users\gruva\Gruva\Recordings\Reacts\BifWellington\BiffWell.veg
   File:                C:\Users\gruva\Gruva\Recordings\Reacts\Assests\Video Assests\Pause.veg
   File:                C:\Users\gruva\Gruva\Recordings\Reacts\Assests\Video Assests\SubButton.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 18.0 (Build 527)

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 18.0\vegas180.exe
   Process Version:     Version 18.0 (Build 527)
   Process Description: VEGAS Pro
   Process Image Date:  2021-05-03 (Mon May 03) 17:45:44
 

mark-y wrote on 10/4/2023, 7:57 AM

Does it work if you remove the Style Transfer plugin from your project?

gruva wrote on 10/4/2023, 8:01 AM

I've not used any transitions, it's all just straight cuts (I think)

gruva wrote on 10/4/2023, 8:18 AM

Looking through the timeline it's all just fades crossfades and straight cuts. If there were some other transition lurking on the timeline, how would I find it?

j-v wrote on 10/4/2023, 8:52 AM

How much free space is available at your render-to location?
You need there at least 2x the expected space of the rendered file

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

gruva wrote on 10/4/2023, 8:54 AM

the output is going to be about 1GB and there's about 300+ GB at the destination

RogerS wrote on 10/4/2023, 10:00 AM

What's your CPU and GPU?

Does the sample project in my signature render okay with your desired render template? If so it's an issue with the media or project.

gruva wrote on 10/4/2023, 10:03 AM

Ok I'm using a MSI 3060ti and the cpu is AMD Ryzen 5 3600XT
I'll have a look at the project in the sig now/.

RogerS wrote on 10/4/2023, 10:09 AM

If you're on an old version, try the current NVIDIA studio driver for your MSI- I have it working fine with my 2080 Super.

gruva wrote on 10/4/2023, 10:18 AM

your project rendered totally fine. Is there nay way to find the issues that it's stumbling on?

gruva wrote on 10/4/2023, 10:27 AM

sod it, I'm done. going to try and re edit everything in davinci

RogerS wrote on 10/4/2023, 10:51 AM

Sure, you could share Mediainfo for the main media you are using: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

(players like MPC have this under file properties)

It's probably an issue with VEGAS not liking it.

gruva wrote on 10/5/2023, 3:46 AM

Thanks for the help everyone, for the possible benefit of future trawlers of the forums, Solved (Kinda)
I tried Davinci Resolve and hated it, so I went back to the drawing board with Vegas Pro.
I exported as XML then started a new project and imported via XML.

All the cuts are there in the right place, most of the fades work fine too, just some fixing of sound levels on the main tracks, and a few masks to fix.

I did a test render right away to see if it suddenly worked and it did, so I'm going to go back through and fix all the broken bits. If you hear nothing more from me then it worked even after adding the stuff back in.