VP17 "Not Responding" seemingly at random on Windows 10

James-Montgomery wrote on 9/6/2022, 12:28 AM

Sometimes it triggers from a CTRL + Z, sometimes it's just dragging a clip on the timeline, sometimes it's opening something in the trimmer, sometimes it's just clicking somewhere inside the program.

I turned off the GPU acceleration, drivers are updated, RAM is not being maximized, but I still get regular crashing from doing basically anything in the program. Though I think I see it most happen when working on the timeline itself.

If nothing else, could other Windows users corroborate? Do you also have issues of Vegas just pooping out on you?

And unrelated, but does anyone experience issues with dragging the In and Out segment in the trimmer? I can't really get it to consistently let me drag out segment I've set. I usually have to click in and out of the trimmer window before it lets me drag what I want out of it.

Comments

RogerS wrote on 9/6/2022, 5:12 AM

What's the media? What's the CPU and GPU?

17 was much improved from 15 and 16 but still isn't stable with all media types as I recall.

James-Montgomery wrote on 9/6/2022, 9:48 AM

Howdy Roger.

CPU: AMD Ryzen 5 3600x 6-Core Processor

GPU: NVIDIA GeForce RTX 2060

The media files are AVC. I remember starting with I think Vegas 8 and I would say the crashes are lower now than they used to be (I also have a much better computer now.)

I've also bumped up Vegas' priorty to High in the task manager.

RogerS wrote on 9/7/2022, 1:46 AM

For AVC can you specify details? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

For the GPU try the latest Studio driver from NVIDIA.

The undo bug/lag was addressed in VP 19 I believe (still lags but doesn't crash Vegas usually).

Musicvid wrote on 9/7/2022, 9:28 AM

It may have something to do with your expectations of the program. Yes, Vegas takes time to think; yes, that's what the spinning circle indicates; it can pop up at inopportune times. If the screen doesn't turn white, consider letting it spin for a while.

Oh, have you updated your graphics drivers from the Help menu? That can make a difference.

James-Montgomery wrote on 9/7/2022, 12:46 PM

Here's the properties of the raw clips I'm using. It's a several hour long stream but I segmented them down into hour-long clips to work with.

General
  Name: 1579880018-30014514-eaf07ad6-1dbd-4616-b35d-5687ff4475a4.mp4
  Folder: E:\xxxx\xxxx\Downloads
  Type: AVC
  Size: 32.82 GB (33,605,837,807 bytes)
  Created: Saturday, September 3, 2022, 10:25:33 PM
  Modified: Saturday, September 3, 2022, 10:41:02 PM
  Accessed: Wednesday, September 7, 2022, 12:33:33 PM
  Attributes: Archive

Streams
  Video: 12:05:07.917, 60.000 (VFR) fps progressive, 1920x1080x32, AVC
  Audio: 12:05:08.841, 48,000 Hz, Stereo, AAC

Summary
  [TCFM]: 6

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: E:\Program Files\VEGAS\VEGAS PRO 17\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 1.0 (Build 8532)
  Company: MAGIX Computer Products Intl. Co.

Unfortunately, when my Vegas begins to hang up, the white screen is guaranteed. It's pretty quick at injesting media and moving the timeline around besides, but something as small as clicking between the Trimmer and the Timeline can trigger it.

I went ahead and installed that studio driver, I've just been updating the "game-ready" drivers till now. I'll check to see if that might make the difference.

Musicvid wrote on 9/7/2022, 1:01 PM

Your video is 60 fps Variable Frame Rate. That looks like the biggest cause of your slowdown because it requires a lot of computing power to decode in real time, even though you have a good system.

Your most accessible solution is to create a Proxy File. You may also get some help by changing your decoder preference. Search.

j-v wrote on 9/7/2022, 1:44 PM

Program files on E:\ ????
And Windows on ???

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)

 

James-Montgomery wrote on 9/7/2022, 2:30 PM

I have Windows and Vegas installed on an SSD, the C:\, and all my other files installed on a disk drive, E:\.

Speaking of, in the middle of typing this post I suddenly had my entire computer crash. I think I may need to check some things out on the hardware side of things and then worry about Vegas. 😓

After that I will try using proxy files and check out the decoder options. After I attempt everything I may resurrect the thread if the issue persists.

I appreciate the help from everyone.

j-v wrote on 9/7/2022, 2:45 PM

How is this possible?

Plug-In
  Name: so4compoundplug.dll
  Folder: E:\Program Files\VEGAS\VEGAS PRO 17\FileIO Plug-Ins\so4compoundplug
  Format: AVC

and

I have Windows and Vegas installed on an SSD, the C:\

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)

 

James-Montgomery wrote on 9/7/2022, 9:47 PM

Ah nvm, just Windows. I thought I had Vegas on there. Wasn't thinking. 😅

James-Montgomery wrote on 9/10/2022, 7:05 PM

I think the issue with the crash was due to installing the studio driver. Changed the boot device and good to go. I'm trying to make those proxy files, but the progress bar sits at 0, and then this error pops:

An error coccured while creating a proxy file for a stream.

The file could not be opened. make sure the file exists and that you have access to the file/folder.

Tried deleting the SFK files and attempting to make the proxy again, but ends with the same result.

I notice when I delete the SFK files, vegas tries to rebuild them automatically as soon as I click inside the program. Could that be preventing the proxy files from being made?

RogerS wrote on 9/10/2022, 7:25 PM

I doubt it's the studio driver- it's just the regular driver released less frequently.

Don't delete SFK files as they are used for audio peaks. Video proxies are a different process.

I usually make variable framerate files into constant before bringing into Vegas to avoid decoding issues. Shutter Encoder and Handbrake are two program that can do that and are free.