Projects load much quicker if you disable so4compound.dll

Thank you for responding. It loads up, and then just says "not responding". And other times, it only gets 40%

Can you check the properties of a clip, is it using so4compound.dll?

Just run V17, import one clip from your V16 project and check clip properties. Its on the general tab at the bottom under plug-in

It loads up, and then just says "not responding". And other times, it only gets 40%

@daniel-t2081 - Been bashing VP17 for the last 24 hours and I’m too finding it a Crash-Test-Dummy. It’s not my specifications. It’s not the Media since I used the same in VP16.

IMHO, more work needs to done on VP17 to get it stable. Let’s hope it’s sooner rather than later.

I just checked under properties, and it says " Folder: C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\so4compoundplug"

Could you go into Options/preferences and hold shift while clicking preferences. Click the internal tab and type so4 in search bar. You can then change the Value from TRUE to FALSE (just do the one for enable s04 compound reader for AVC if you mainly use MP4/AVC files) and click apply. Restart and try to load your V16 project. The so4 reader is mainly for HEVC files.

So in other words, change Enable S04 compound reader for AVC to FALSE while keeping everything else as TRUE?

Yes (are your clips AVC?)

Even if it says not responding when loading wait for two/three minutes to see if it will complete.

Well it actually says "Enable S04 compound reader for AVC/M2TS" . I just checked, the clips I am using are MP4 but the format is AVC. Here's a photo, if that helps.

Great change it to false

Ok, just changed it to FALSE.

Hopefully it will load your project

There are 2 projects which need to be combined to make the full film. The smaller project opened and worked, after what you said to do, so thank you! The other project (which is bigger) just crashed and computer froze after getting to 100%. So unfortunately I couldn't click any options at the top or anything like that. Any suggestions?

 

With the bigger one does Vegas completely crash and close down? If so what is the fault module identified in the crash box?

Also are you using any plug-in videoFX such as Boris/NewBlue ?

Yeah, crashes and closes down. It did it a few times, and the last time, it totally froze computer. I'll try it again and send you the Fault Module in the crash box. One sec.

Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\VEGAS\VEGAS PRO 17.0\FileIP Plug-Ins\mxhevcplug\MXVideoAllocator.dll
Fault Address: 0x00007FF949B31758
Fault Offset: 0x0000000000001758

Fault Process Details

Process Path: C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe

Process Version: Version 17.0 (Build 284)

Process Description: VEGAS Pro

Process Image Date: 2019-7-30 (Tue Jul 30) 13:16:54

I have found this:

Kloverton wrote on 8/6/2019, 11:55 AM

Hello again. I'm sorry for my emotional post yesterday.

I figured out that certain files don't work correctly in VP17 and it crashes.

Those are 10BIT 21:9 4K HDR Files recorded in h265 from Xperia 1.

Works fine in Vegas 16 though. Thats the module that crashes - Something to do with HEVC.

VEGAS Pro 17.0\FileIO Plug-Ins\mxhevcplug\MXVideoAllocator.dll

Is he suggesting to go back to Vegas 16?

Also in same post:

MAGIXheman wrote on 8/7/2019, 1:31 AM

Kloverton, I am one of the VEGAS Engineers, and like posters above, I also could not reproduce the problem after downloading the file. But the module you listed (MXVideoAllocator.dll) is a new component added to VP17, so I assume this is a problem related to it. Could you recreate the crash, and send in a problem report, listing your name in the comments field, so we can search for it and take a deeper look?

In the meantime, as you have a GTX 1080 on that machine, you may want to enable the NVIDIA NVDEC hardware decoder (from Preferences -> FileIO), and try to use it instead till we sort out this problem.