Best Settings for Vegas 18 Projects that won't crash?

NickyT wrote on 8/3/2020, 8:27 PM

Gear:

Ryzen 3950x, RTX 2080TI, 64 GB Ram

Context to Topic:

I've been using Vegas Pro since 12. (Skipped 15 and 16 because 14 worked great until I started filming in 4K) I just upgraded to Vegas Pro 18 from 17 today. I did a 5 minute, 4K 24FPS test between both programs (with color correction) and discovered that V17 finished it in 9:20. While V18 finished it in 8:30. Which I thought was amazing. However, once I tried to render a 15 minute, multi layered video on V18. It continued to crash. I changed the DRam fix from 200 to 0. (A bug that Vegas has had since Vegas 14) and it worked like a charm. However, the project at 200 DRam, before it crashed, had an estimated duration of 28 minutes. But at 0 DRam it took 47 minutes to render.

The Topic at Hand:

So the question is, what are the best settings for me so that I can get faster render speeds but the software won't crash? Will their be a bug fix at some point that will fix this? Will Vegas Software consider making like a PC specs page with the best settings per CPU so everyone can figure out their best settings?

If anyone has any ideas. I'd love to hear them. Hopefully we can get this post seen by some of the devs.

Comments

RogerS wrote on 8/3/2020, 9:34 PM

You should post project and media info to try to figure out what the issue is.

Are you using DJI or GoPro clips?

You shouldn't have to manually intervene to get a stable program- that's the direction Vegas is going in, not per-CPU workarounds. Leave file i/o to auto, etc.

Former user wrote on 8/3/2020, 11:04 PM

 

So the question is, what are the best settings for me so that I can get faster render speeds but the software won't crash? Will their be a bug fix at some point that will fix this? Will Vegas Software consider making like a PC specs page with the best settings per CPU so everyone can figure out their best settings?

 

As you said the unstable with GPU preview set to above 0 has been a problem they've known about for years, and they can't fix I had to set to 0 earlier today when editing some Samasung Galaxy HEVC video. Could not render without the change. Interesting to hear about the speed increases between 17 and 18 with encoding, when gpu preview set to default (200), just the small problem of the speed increasing making the software even more unstable by the sound of it. I happen to like gpu preview previewing especially transitions and even on vp17 it's faster than gpu preview 0, although the speed difference isn't like you're talking about with vp18

 

fr0sty wrote on 8/4/2020, 1:06 AM

This issue seems to be exclusive to Nvidia cards, as I never have any issues on my AMD system (though I don't have them on my RTX 2060 laptop either, so...). Hopefully they can sort this out soon.

It would be helpful if you could give us a mediainfo report of your project's media. We only need one report per type of media used. Also please include your project settings, GPU driver version, and windows 10 version.

Robert-H wrote on 12/3/2020, 7:30 AM

When I set my ram setting to zero it pretty much crashed out (worse than it was). Setting ram to 1/3 of my total available ram worked like a charm though (32gb, so set it to 10000). For what it's worth I'm using a high end ryzen cpu with a 2080ti and vegas 18. It's great, but isn't it about f time it worked without $%^&* about?

RogerS wrote on 12/3/2020, 7:52 AM

When I set my ram setting to zero it pretty much crashed out (worse than it was). Setting ram to 1/3 of my total available ram worked like a charm though (32gb, so set it to 10000). For what it's worth I'm using a high end ryzen cpu with a 2080ti and vegas 18. It's great, but isn't it about f time it worked without $%^&* about?

If my understanding of dynamic ram preview is right, 10000MB (10GB) is going to cut into the amount of ram Vegas has to use pretty significantly as I believe the program is capped at 1/2 system ram (so 16GB). My suggestion would be for zero and there may be a confounding third factor making it appear to help.

But this thread is 4 months old so hopefully the original poster has it resolved.

Robert-H wrote on 12/3/2020, 7:57 AM

yeah I tried that and it just crashed out even worse than before. For me at least, setting it manually to 10000 made it stable. Going to zero actually prevented mine working AT ALL. Strange that. Why are we having to mess with v18 though? But I might try upping that 10000 to see if stability improves further.

Illusion wrote on 12/3/2020, 8:15 AM

Ryzen 3900x and RTX 2070 here, more details in my signature. Latest studio driver. I cannot get VP18 to work with any amount of Dram except 0. If I set to a value different than 0, it works for about 1 minute and then the preview window freezes and goes red.

  • ASUS ROG Strix X570-E
  • Ryzen 9 3900x 12-core
  • 128GB RAM (4x32GB)
  • Nvidia RTX 2070 8GDDR6
  • 1TB WD Black NVMe M.2 for OS/Prog
  • 1TB WD Black NVMe M.2 for Media
  • 1TB/2TB/4TB SATA3 SSDs for projects/media
  • 4TB WD Red drive for local cache
  • 10TB EXOS Enterprise, 14TB Toshiba drive for local cache
  • 32in 4K main monitor, 24in 1080 second
  • Win 11 Pro
  • 28TB NAS for long term archive storage
  • Sony a6000
  • Sony A7C
  • GoPro Hero 8
  • GoPro Hero 11
  • Sony BRAVIA XR X90J 75" 4K HDR10
  • Nvidia Shield TV Pro media player (GigE wired)
  • JBL Bar 5.1

 

Robert-H wrote on 12/3/2020, 12:32 PM

the frustration! Something that I had to do after a crash was to reset the setting (ctrl + shift held down as you click on the program icon). It's a longshot, but worth trying in case.

RogerS wrote on 12/3/2020, 6:30 PM

Freezing and red screen is a GPU issue I thought. Did you file a support request? That's unusual for newer versions of Vegas.

Robert-H wrote on 12/6/2020, 7:40 AM

It's been pretty stable since upping the ram and resetting the menus. Worked for me. I also find that regular saving and closing / re-opening files helps, as does limiting the amount of cuts (complex edits seem to become unstable).