Comments

michael-harrison wrote on 6/8/2020, 8:41 PM

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

https://www.vegascreativesoftware.info/us/forum/vegas-pro-faqs-and-troubleshooting-guides--104787/

Try:

The recommendations in the FAQ for solutions when VP is crashing.

A driver cleaning http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Make sure your cache folder is clean by deleting everything in  C:\Users\<user name>\AppData\Local\VEGAS Pro\<version #> (delete everything with VP closed and use task manager to make sure it's really gone from memory). The initial startup will be kind of long after this cleaning but once it's up, restart VP. Use task manager to make sure VP is completely gone from memory before starting it back up.

Try these tips too 

Disable so4compoundplug.dll if videos are AVC https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-16-try-disabling-so4compoundplug-dll--108345/

Trim your project looking for fx combinations that cause problems.  For example, Picture in Picture and Layer Dimensionality together are lethal on my machine

 

fifonik wrote on 6/8/2020, 9:37 PM

I have something similar with the most recent VP17 build 452. If I leave VP with opened project minimized for some time, then I have the same issue when returning to editing (start preview: I hear audio, but video is not played).

I did not have such issue with previous builds. Not sure if this caused bu recent Windows 10 updates. I'm going to try previous VP build to check if this fix the issue.

P.S. I have not changed anything in HW and in VP settings. The same GPU driver, so4 disabled.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

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

KenB wrote on 6/9/2020, 3:25 AM

@fifonik has you checked to see if "Close media files when not the active application" is unticked? It is enabled by default and the upgrade to b452 may have re-enabled it when you upgraded?

Ken.

Dr Zen wrote on 6/9/2020, 3:35 AM

I have no idea if this has anything to do with your problem, but I thought it was worth mentioning.

Every time a major new version of Windows 10 is released and installed, Vegas will sometimes stop working and/or do weird shit. As well as resetting Vegas, which cleans the temp files cache, I recommend un-installing Vegas and then re-installing.

Every time I have re-installed Vegas, all the weird problems have gone away.
I also saw improvements with the Preview Window after switching from Game ready Nvidia Drivers to the newer Studio Drivers. If you are using an Nvidia graphics card and gaming is not important to you, I highly recommend giving the Studio drivers a go.

https://www.nvidia.com/Download/index.aspx

Regards
Derek

fifonik wrote on 6/9/2020, 5:17 AM

I'm aware about the option and it is always ticked in my case. I do not have the issue in my VP15 (the option is also ticked), so I do not think the issue is related to the OS change.

Installing new build means uninstalling previous one first. I have installed the latest VP17 build just recently.

I have not checking if the issue persist in my system on the previous VP17 build. I need to finish current VP project first, then I will do the experiments. Will provide more details later.

 

UPDATE: The same issue is in VP15. So something happened with my system. Investigating.

Last changed by fifonik on 6/9/2020, 11:57 PM, changed a total of 3 times.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

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

VEGASDerek wrote on 6/9/2020, 7:59 AM

@SomeAMan
We have had reports of this behavior for quite some time, but have continued to have a hard time tracking down exactly the scenario which is causing this for some users. Could you provide a sample piece of media that exhibits this behavior and also your system configuration, including CPU, GPU and RAM?