Vegas Pro 16 random freezes, already tried the support article here

Trentonius-Maximus wrote on 6/1/2020, 12:37 PM

I have a ridiculously powerful system and when Vegas freezes at random, I don't see anything in the Performance Monitor ramping up, so this isn't a disk or memory bottleneck, GPU / CPU overload, etc. This can happen with a 4K video project or a 720p project with minimal edits. For every bit of work I do, a specific Project is created to handle all the assets.

Specs:

Intel Core i7 9650X Xtreme Edition processor

G.Skill Trident OCZ RAM, 128GB (@8 x 16), XMP enabled

2 x nVidia GeForce RTX Ti Founders' Edition video cards

Windows 10 64-bit running on Samsung 950 PRO series M.2 SSD

Working on a RAID 0 array of Samsung 850 EVO series SSDs (2 x 1TB)

Suggestions?

Comments

j-v wrote on 6/1/2020, 2:06 PM

Suggestions?


    I would not dare . . .

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.48 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

michael-harrison wrote on 6/1/2020, 3:51 PM

@Trentonius-Maximus To be clear, turning off GPU support had absolutely zero effect on the freezing?

Trentonius-Maximus wrote on 6/2/2020, 10:10 AM

Correct! I've tried different variations on this based on various troubleshooting videos I've run across (closing and re-opening Vegas between changes):

1) No GPU and default Dynamic RAM of 200

2) No GPU and default Dynamic RAM of 0

3) GPU and default Dynamic RAM of 0

4) GPU and default Dynamic RAM of 2000 <--hey, for testing, why not?

After a few hours of working in Vegas last night, it looks like no GPU and Dynamic RAM of 200 makes the freezes a bit shorter (like 10-15 seconds instead of 20-30), but the other variations are still random freezes of about 20-30 seconds.

I should also mention that I gave the entire program carte blanche access to the system, running it as an Administrator and telling my anti-virus/anti-malware to ignore Vegas and anything in its folder(s).

I also tried the advanced option of setting processor affinity to 4 of the higher cores (of 10) in the CPU. I haven't tried disabling multi-processor affinity though. I may try that next.

Thank you all for the replies! @j-v I'm not sure why you 'wouldn't dare', but I'm certainly open to feedback. ^_^

RogerS wrote on 6/2/2020, 10:50 AM

Maybe put everything back to defaults and turn off NVIDIA decoding on the file I/O tab?

JN- wrote on 6/3/2020, 5:59 AM

@Trentonius-Maximus Try completing removing one of your gpu's. If possible make available for testing a sample that does give trouble. Supply Mediainfo info. of your media, plus a screenshot of your project settings. Is any of your media variable frame rate, if so try converting to CFR.

Last changed by JN- on 6/3/2020, 7:47 AM, changed a total of 2 times.

---------------------------------------------

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

michael-harrison wrote on 6/3/2020, 7:26 AM

You mention trying it with different media types but were those attempts with a project with just that media playing, no fx of any kind (other than the default audio fx added by vp)?

I ask this because I found that mixing PIP with layer dimensionality was the key to the hanging I was regularly experiencing.

Removing LD worked around this issue for me.

So you might try seeing what the raw video does and if you can isolate a common "when" the program dies, you might be able to isolate what fx aren't combining well

Trentonius-Maximus wrote on 6/3/2020, 9:03 AM

Maybe put everything back to defaults and turn off NVIDIA decoding on the file I/O tab?

I'll give this a try, thanks. I can't work in Vegas today but I'll try it and update here as soon as I get the chance to.

Trentonius-Maximus wrote on 6/3/2020, 9:13 AM

@Trentonius-Maximus Try completing removing one of your gpu's. If possible make available for testing a sample that does give trouble. Supply Mediainfo info. of your media, plus a screenshot of your project settings. Is any of your media variable frame rate, if so try converting to CFR.

Thanks JN! I'll take this in bits.

1) I can't remove a GPU. This is a custom water loop with a hard parallel cooling block, so it's not worth the risk and mess that would entail. :)

2) Let me know what kind of 'sample' would be useful (how best to package such a thing)

3) Two example projects:

One is a 3-minute 720p iPhone video that has a combination of small phone still images and short phone-captured video clips. Simple fade transitions from asset to asset. Eventually I did audio processing chains but this problem emerges pretty much from the get-go of Project creation.

Another is a series of 4K clips @30 FPS captured on a Nikon Z-series, laid in sequence with simple fades from clip to clip.

I do like to use the default prompt of making the project's specs match the first asset I drag into the timeline.

CFR for the win, I don't care for VFR. I can look at the individual assets on that first project and see if any are VFR and update you accordingly.

JN- wrote on 6/3/2020, 1:41 PM

@Trentonius-Maximus 2) A small sample project that makes your system fall over, so to speak. Put it in a downloadable zip for users to check out on their machines.

Its quite likely that item 2) above won’t be necessary as I now know that you’re using iphone media which may be VFR. If so convert to CFR first and then see how it goes. It can save a lot of time posting your media info first, as sometimes its the cause of the problem.

VP16 does handle VFR but not as well as VP17, but even with VP17 it makes everything easier if its CFR.

”I do like to use the default prompt of making the project's specs match the first asset I drag into the timeline.”

If u have mixed media type, best to set project properties to what is the most used media, that may not be necessarily the first clip you load into the project.

Last changed by JN- on 6/3/2020, 1:47 PM, changed a total of 3 times.

---------------------------------------------

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

Trentonius-Maximus wrote on 6/4/2020, 1:25 PM

You mention trying it with different media types but were those attempts with a project with just that media playing, no fx of any kind (other than the default audio fx added by vp)?

I ask this because I found that mixing PIP with layer dimensionality was the key to the hanging I was regularly experiencing.

Removing LD worked around this issue for me.

So you might try seeing what the raw video does and if you can isolate a common "when" the program dies, you might be able to isolate what fx aren't combining well

Correct! Very simple media drop-ins and cross-fades with no FX added in, no PIP, and I didn't fiddle with the audio track until I was close to render-ready. To both you and @michael-harrison, I'll add that I have a weeny nerdy project of just 4K clips on a timeline that I'll spend some time working on and see how that goes. Right now I'm at GPU acceleration off, 0MB Dynamic RAM preview. @RogerS can you tell me where to get to the File I/O tab? I'm on Vegas Pro 16, I don't see it if I Shift+Ctrl+click Preferences, but I do know that some of the Prefs tabs are different in Vegas Pro 17.

michael-harrison wrote on 6/4/2020, 1:36 PM

You may also want to try https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-16-try-disabling-so4compoundplug-dll--108345/

in addition to disabling the nvidia hw decoding

vkmast wrote on 6/4/2020, 2:06 PM

michael-harrison wrote on 6/4/2020, 2:10 PM

@vkmast hmmm. Wonder where I got that idea. I looked again and I definitely don't have a speacial-to-me fileio tab in my version of 15

VEGASDerek wrote on 6/4/2020, 4:42 PM

The File I/O tab was added in VP 17. It did not exist prior to that.

Trentonius-Maximus wrote on 6/4/2020, 9:20 PM

Thank you! I have 15 and 16 and was digging around questioning my sanity! XD

RogerS wrote on 6/5/2020, 6:52 AM

Sorry, I forgot we were discussing 16, not 17.

Trentonius-Maximus wrote on 6/5/2020, 2:59 PM

Hi folks! I think the problem is solved - it looks like the solution was the one-two combo of GPU off and 0MB VRAM:

I used 'vanilla 4K' to test it and then went back to 'iPhone Hodgepodge' project and started doing goofy edits, inserting transitions and VideoFX during playback, etc., and Vegas Pro never flinched. Hooray!

I'm having a hard time picking any one clear "Tag as solution" here because if I have performance problems beyond this, I'm going to be coming back here and trying other things like forcing constant frame rate, checking PiP and LD, etc. (and if I ever upgrade to Vegas Pro 17, using the File I/O tab).

Thanks everybody! I really appreciate the help.

@JN- thanks for the media sample tip - I'll keep that in mind if I need to get help in future

@michael-harrison thanks for the tips and links!

@RogerS thanks for the File I/O suggestion for possible future VPro 17 users who come across this thread

@vkmast @VEGASDerek thanks for confirming I'm not crazy :D