Vegas Pro 18 crashes every 2 minutes

AlanH wrote on 9/16/2020, 10:18 AM

Hi,

Vegas Pro 18 crashes every couple of minutes, particularly when I move from one position on the timeline to another. That's not even long enough to create a timed backup. I need to manually save every few keystrokes to make any progress.

I 'upgraded' from Vegas Pro 17 to Vegas Pro 18 a month ago.

I am trying to work on a project originally set up on MovieStudio and subsequently migrated to Vegas Pro 17. It's moderately complex, but does not use any of the 3rd party effects (not installed).

For info, the program crashes on newly created projects as well.

I have done various tweaks as shown in YouTube videos but they have no effect:

  • OpenCL/... FALSE
  • Legacy AVC/HEVC enabled
  • Memory allocation 4096MB (which seems reasonable, especially if I have to open two instances of Vegas to copy material from other projects).

I have the current version of Vegas Pro 18 (build 284).

My PC is Win10 on an i7-6700 processor with 32GB RAM and has been working OK with Vegas for the last 8 years.

My video card is NVIDIA, but as it's only a simple 2GB model, I have turned GPU rendering OFF. (Not as though it makes any difference to stability).

This 'upgrade' has completely sabotaged my editing work.

Does anyone have any idea how I go about debugging this?

Regards,

Alan

Comments

j-v wrote on 9/16/2020, 11:52 AM

Did you already resetted the program to the default settings, changed nothing and than load and try your project?
For resetting follow this exactly: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

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 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

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

AlanH wrote on 9/16/2020, 5:54 PM

Thanks, j-v

I have come to the conclusion that attempting to run 2 instances of the program makes it (them) very unstable, and may have been a significant factor in the repeated crashes I was having.

This is a pity because it's the only way to copy regions from one project and drop them into another, without doing an intermediate render.

After I rationalised the project (deleting tracks, doing things with transitions that I was doing with the track motion function, etc.), and ran only one instance at a time (which means and doing tedious intermediate renders from my source project), the program has settled down to an extent, but I still get random crashes.

I did do the preferences reset as you suggested, although looking at the 'export preferences' file, I had not changed very much.

So it's onwards and upwards, manually re-saving every minute!

Alan

 

j-v wrote on 9/17/2020, 3:47 AM

This is a pity because it's the only way to copy regions from one project and drop them into another, without doing an intermediate render.

Did you ever try the use of "nested" vegs? No need to render in between.

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 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

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

AlanH wrote on 9/17/2020, 4:07 AM

Netsted projects isn't something I've invested time into understanding yet, but I should - I may have to adjust my workflow, but it could be a useful approach - thanks!

walter-i. wrote on 9/17/2020, 4:18 AM

If you try nested projects, don't be surprised that it sometimes seems quite long idle and updates have to be rendered every time. If an individual project becomes shorter or longer due to adjustments, this must be adjusted manually in the "Nested Project".
Otherwise, this is a very good method to keep track of things and prevent multiple render generations.

Last changed by walter-i. on 9/17/2020, 4:19 AM, changed a total of 1 times.

CPU: Intel i9-9900KS 4GHz, (UHD Graphics 630, driver: 27.20.100.8581)
MB: ASUS TUF Z390-PLUS Gaming,
MEM.: 32 GB Ram, DDR4-3200
GPU: Nvidia GTX 1660 SUPER, (driver 451.77)
Storage: SSD 970 EVO Plus 500GB M.2, SSD 860 EVO Series 1TB, Toshiba 3TB SATA,
OS: WIN 10 Pro, 1909
Monitor: HP243i 1920x1200 / BenQ G2200W 1680x1050
NLE: Vegas Pro11-15+17,18 Heroglyph4, RespeedR
Camcorder: Pana HDC SD909, Sony FDR-AX53

AlanH wrote on 9/17/2020, 4:42 AM

Thanks for the warning, Walter. In my immediate application, each nested project would consist of a very short composite of clips from a very large source file, which may be a bit cumbersome. As I'm on a deadline atm, I think I'll wait till I start a new project and try it out then!