Pressing "Render As" Crashes Vegas Pro 18 | Unable to render anything

Deata wrote on 8/5/2020, 6:41 AM

Hey just installed Vegas pro 18 and finished my first project with it, issue is that i cant render it because no matter what i do, when i press "Render As" the program hangs for a second and then closes itself without a crash report.

This is an issue because Vegas Pro doesn't have any backwards compatibility so im gonna have to basically start from the beginning using Vegas Pro 17.

Does anyone have any workaround because a NLE that can't render and has no backwards compatibility/proper export options is as usefull as a rock

Comments

fr0sty wrote on 8/5/2020, 6:43 AM

What render format and template are you using? One thing to try first would be to click Help, and then use the new driver update utility to download the recommended drivers for your GPU.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Deata wrote on 8/5/2020, 6:53 AM

What render format and template are you using? One thing to try first would be to click Help, and then use the new driver update utility to download the recommended drivers for your GPU.

I cant choose a render format because when i click "Render as" the program instantly freezes and closes.

I never even see the window to choose a render format.

I have updated all my drivers with a driver update tool and checked they are all latest and correct and every others software and version of Vegas Pro that i own renders fine.

j-v wrote on 8/5/2020, 6:58 AM

I have updated all my drivers with a driver update tool and checked they are all latest and correct ....

Did you updated with VPro18's own option to update drivers in the Help?

 

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)

 

Deata wrote on 8/5/2020, 7:02 AM

I have updated all my drivers with a driver update tool and checked they are all latest and correct ....

Did you updated with VPro18's own option to update drivers in the Help?

 

I did not, though im using the latest nvidia studio drivers so unless there are vegas pro only nvidia studio drivers then i don't see the point ?

This is clearly not a driver issue because its not that i cant render, its that opening the panel where i would choose a render format causes Vegas Pro to crash.

fr0sty wrote on 8/5/2020, 7:08 AM

I imagine if there were any issues with a particular driver, the dev team would link to a driver they know works in the driver update utility, so I'd recommend using it.

That said, it seems as if the issue isn't related to that. Perhaps try a re-install?

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Steve_Rhoden wrote on 8/5/2020, 8:08 AM

Try re-installing....

 

VEGASDerek wrote on 8/5/2020, 8:11 AM

I'd like to help, but no relevant information has been provided.

fr0sty wrote on 8/5/2020, 8:15 AM

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

VEGASHeman wrote on 8/6/2020, 7:48 AM

Please make sure you do not have any third-party FileIO plugins installed, which are not compatible with VEGAS Pro 18. If you do not have any third-party FileIO plugins, can you provide the contents of your FileIO log (from C:\Users\<USERNAME>\AppData\Local\VEGAS Pro\18.0\fileio_x64.log), to help us diagnose the problem?

Howard-Vigorita wrote on 8/6/2020, 9:45 PM

Just did a small single camera piano/vocal 4K h.265 project with Vegas 17 and 18 in parallel without proxies... lots of freeze-ups in both. But playback was very smooth in 18 till wamo, it would just go busy with the hour-glass. Oddly, it was happening when I was doing allot of envelope editing on the vocal and piano audio tracks. Before I even got to any video editing. Seemed like the more often I saved, the less it happened. When I got to the render stage after color grading with Vegas 18 and rendered the 20-minute set with Magix HEVC 4K AMD preset, it worked fine once but after that render started hanging. Reboots didn't help. Finally deleted everything in the Vegas temp directory (the one listed at the bottom of the General Preferences screen) and that fixed it. Had a number of log files in there plus allot of other stuff. Been rendering fine since then.

Deata wrote on 8/14/2020, 6:50 AM

Just did a small single camera piano/vocal 4K h.265 project with Vegas 17 and 18 in parallel without proxies... lots of freeze-ups in both. But playback was very smooth in 18 till wamo, it would just go busy with the hour-glass. Oddly, it was happening when I was doing allot of envelope editing on the vocal and piano audio tracks. Before I even got to any video editing. Seemed like the more often I saved, the less it happened. When I got to the render stage after color grading with Vegas 18 and rendered the 20-minute set with Magix HEVC 4K AMD preset, it worked fine once but after that render started hanging. Reboots didn't help. Finally deleted everything in the Vegas temp directory (the one listed at the bottom of the General Preferences screen) and that fixed it. Had a number of log files in there plus allot of other stuff. Been rendering fine since then.

Yup this solved the issue, though i need to apparently clear it a few times during editing if i want to keep rendering.