Vegas Pro 17 Crashing

Sam-Ray wrote on 2/7/2020, 5:24 AM

Hi - Just wondered if anyone's found a solution to the freezing/crashing problem that some users of Vegas Pro 17 have been experiencing? I've been using version 16 for a while and love it - the user interface is intuitive and it's as stable as a rock, but I wanted to use the nested timeline feature of version 17 so am using a trial version (17.0 build 387). BUT it keeps crashing. I have a new high spec PC which has no problems with my Adobe software, Pro Tools, or any other programs, so I'm pretty sure it's not a hardware issue (Windows 10 Professional 64-bit, 64GB RAM, Intel Core i9-9900K CPU 3.60GHz, and two graphics cards, an NVIDIA GeForce RTX 2070 and a NVIDIA Quadro P400 to handle 10-bit colour).

I've already watched a bunch of YouTube 'fixes' about disabling and changing all sorts of settings to increase stability, but haven't had any success so far.

So... any suggestions to help get VP17 working properly would be GREATLY appreciated. I work (in both a paid and voluntary capacity) for a non-profit mental health service by the way, so your help would be contributing to a very good cause :)

Many thanks, Sam

Comments

fr0sty wrote on 2/7/2020, 11:35 AM

First of all, I'd get rid of the other Nvidia card, you no longer need pro cards to have 10 bit color with Nvidia (AMD needs to catch up there, big time), just install the Nvidia studio drivers on the one RTX card and you're good to go. Also keep in mind this only applies if editing 10 bit source video in HDR mode and viewing on a HDR capable display with Windows HDR mode enabled on that display. Also, don't enable HDR until you're done editing, as 32 bit mode is much slower than 8 bit mode, so it is always best to cut in 8 bit, then go back and color in 32 (again, only if HDR is your planned output format and you have a HDR display with 10 bit or higher video being edited).

Youtube is not a good source for help with repairing Vegas issues. It rarely works out and there are a ton of people with no idea what they are talking about trying to give advice.

Try to disable or remove that Quadro card, install the latest studio driver from Nvidia for the RTX, and see if stability improves. We'll start there, there's still some other things to try.

Last changed by fr0sty on 2/7/2020, 11:39 AM, changed a total of 2 times.

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)

j-v wrote on 2/7/2020, 11:42 AM

Youtube is not a good source for help with repairing Vegas issues. It rarely works out and there are a ton of people with no idea what they are talking about trying to give advice.

+ 100 😉

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 580.97 and Intel UHD Graphics 630 with driver 26.20.100.7985
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)

 

Sam-Ray wrote on 2/8/2020, 4:46 AM

Thank you fr0sty and j-v :) very much appreciate you taking the time to respond. I've disabled the Quadro graphics card in the device manager and the computer seems to be working fine without it. I also installed the latest NVIDIA studio drivers for both cards yesterday as part of my troubleshooting efforts, so that's two suggestions checked off the list. I've got to take the dog for a walk and then I'll try some editing this afternoon to see if the stability improves. Your comments about 8 and 32-bit colour, and HDR are a little beyond my understanding, but I'll try to look up those settings and configure them as you've suggested. Thanks again, I'll report back and let you know how things go. Fingers crossed.

fr0sty wrote on 2/8/2020, 8:21 AM

If it's beyond your understanding, you don't have a need for it yet. The main thing is you must start with 10 bit or higher video to even need any of that stuff, and then you must be targeting a TV that can display 10 bit or higher, which most cannot. Otherwise, keep your Vegas project settings at 8 bit at all times, do not use 32 bit mode.

Last changed by fr0sty on 2/8/2020, 8:22 AM, changed a total of 1 times.

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)

john_dennis wrote on 2/8/2020, 8:24 AM

"I've got to take the dog for a walk..."

You've got the important things covered already.

Sam-Ray wrote on 2/8/2020, 10:51 AM

Regarding the 10-bit colour, my Panasonic GH-5 can record in 10-bit colour, so I was planning to record in 10 bit, edit and grade the footage, and then export in 8-bit colour. But if my RTX 2070 graphics card can now handle 10-bits of colour with the new drivers installed then that's a non-issue. So that's that problem solved.

Re. the stability of Vegas (the bigger issue) I just rendered a little sequence in After Effects and tried to import the uncompressed .avi file into Vegas, which I've done before with no problems, but when I tried it this time (via the import media function) it immediately crashed. When I tried again by dragging and dropping the same file straight onto the timeline it was okay. Things have gotten buggy, I fix one problem and another one materialises (especially since deleting the temporary files folder as per one of the troubleshooting suggestions on another thread).

I may try a re-install. I'm determined to get it working one way or another because I find it so much more intuitive and user friendly than the main alternative - Premier Pro. Thanks again for the suggestions and support, I'll report back when I've tinkered some more to give some closure to this micro drama :)

fr0sty wrote on 2/8/2020, 12:55 PM

Did it crash or hang? There's a difference... many times, a hang will recover if given enough time. Still not what you want to have happen, obviously.

As for 10 bit color, I'm not sure if Vegas can still utilize the extra bit depth in 8 bit mode or not, someone else may be able to chime in on that one, but keep in mind that if you must enable 32 bit mode to grade your 10 bit color, performance is going to drop significantly (so make the switch after you're done editing), and because 32 bit changes everything about the way gamma is mapped, etc... your video is going to look different and may need some adjustments or the proper view transform applied to make it work with 8 bit output.

I'd set the project up this way, open it up 32 bit full range, right click on your GH5 clips, and select "vlog/vgamut" (this assumes you are recording using the VLOG-L picture profile in the GH5, which must be added on separately unless you have a GH5s, but it is highly recommended you shoot this way because it captures the max amount of dynamic range your camera can capture) under the color space settings. This should properly map the colors so that you get the most out of your 8 bit export and the video looks correct when previewing it in Vegas. Alternately, you can leave your GH5 footage (again, this relies on you shooting in VLOG-L mode) as-is, and use a VLOG to Rec709 conversion LUT (panasonic has some on their website, and there are others you can score for free as well, just do a google search for it) and then apply that LUT to the input side of your color grading panel, or add the LUT filter effect to any track your GH5 video is on and apply the LUT there instead, so it applies to the entire track at once.

Last changed by fr0sty on 2/8/2020, 12:57 PM, changed a total of 2 times.

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)

joost-berk wrote on 2/10/2020, 1:14 PM

@Sam-Ray Your where saying that when you render an uncompressed .AVI in AE, this will immediately crash Vegas? Have you already tried rendering an uncompressed .AVI in Vegas? And try to import this in to Vegas? Uncompressed .AVI is the most elementary kind of video material, so it would be very strange if Vegas crash on it. Does the file crash in (for example) Windows Media Player? Reinstalling Vegas is always a good idea by the way.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

fifonik wrote on 2/10/2020, 4:18 PM

If VP16 worked fine in your system but VP17 crashes, I'd try to disable GPU decoding in VP17 preferences.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B650P, CPU: AMD Ryzen 9700X, RAM: G'Skill 32 GB DDR5@6000, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer