@Robert Johnston Thanks, just tried it, but it did not fix it for me.

@altarvic Maybe look into language, regional , PAL, or decimal point (. vs ,) issue?

Or Vegas 17 POST version versus Vegas 17 to reproduce? As said before, Vegas 16 does not exhibit the issue with Vegasaur on my (same) PC using the exact same source clip...

@bitman Do you have the so4 options in Internal Preferences set to true or false? I have three of them set to FALSE, but the blacklist set to TRUE. I decided to set all of them to TRUE, and the next time I started Vegas 17 there was a crash like before. I then set the so4 options to false again, and the crashes stopped. So I have Vegasaur 3.9.1 installed and have enabled the automatic loading of previous project on startup, and have set the so4 options to false (except for blacklist).

@Robert Johnston my So4 options are usually set to true, (including now with the crash), setting them to false is one workaround to avoid the crash (I mentioned this before in this post a few pages back). At that time I was not aware the culprit was Vegasaur. Another workaround (and a better one) is of course disable "automaticly open last project on startup" in the preferences...

@altarvic Strangely enough if you mix source clips with use so4 by default and others which are blacklisted e.g. .mov (they use the old "compoundplug.dll") in the same project and save and exit, then there is no crash with vegasaur when re-opening the project.

I admit that Vegasaur may be the culprit, but at present I do not know how it causes the error.

Maybe it makes some API calls, which in turn throw an exception when loading a project at startup, maybe something was not initialized at that moment, I don’t know. As I said, I could not reproduce this bug on my PC, but I continue to investigate the issue.

If changing So4 settings can fix the error, I suspect that the problem is in the Vegas API, and I'm going to find it.

@altarvic Thanks, If you want me to try something out, I am all ears.

I have the exact same issue since I installed Vegasaur.
I opened a project just 2mn before installing Vegasaur.
I closed the project then reopened it right after intalling Vegasaur and now it crash.
As @bitman said, disabling the So4 option is an effective workaround.

The issue lies 100% within Vegasaur

@altarvic @VEGASPascal @Kenshin9977 @Robert Johnston

Found yet another sollution / workaround for the issue of Vegasaur + VP17 crashing on opening with saved project: if you enable QuickTime plugin in the deprecated features tab of preference, Vegas 17 (when Vegasaur is installed) will not crash anymore when automaticly opening a saved project...

With this workaround you do not need to disable s04 anymore, nor disable the automatic opening of a project in the preferences. Not sure what the consequences are of enabling the deprecated QuickTime plugin are.

@bitman

Thank you Thank you Thank you. That worked for me, too.

Maybe we should deprecate the people who decided to deprecate the plugin.

"Important: QuickTime 7 for Windows is no longer supported by Apple...."

So in theory it's a potential security risk, although I don't believe it's ever been exploited. IIRC the main risk is thought to be the player, which is not necessary to have the codec.

No idea if/why Vegasaur needs it.

It would be better if VEGAS could identify formats that require Quicktime and flag up a note about enabling the plugin at your own risk. Or just a warning/disclaimer as the plugin is first engaged.

It would be better if VEGAS could identify formats that require Quicktime and flag up a note about enabling the plugin at your own risk. Or just a warning/disclaimer as the plugin is first engaged.

@NickHope Are you sure Vegas use the external Quicktime and not an internal substitute (which is maybe more safe)?

From my side, Vegas still doesn't detect installed external Quicktime7, so i guess Vegas doesn't need Quicktime7 install.

It has some "surrogate" link but still needs the external Quicktime. Some mainstream Quicktime formats decode natively in VEGAS these days, but many still do not.

@NickHope There may still be another another application which still needs Vegas "deprecated" QuickTime: Mocha Pro 2020 (which is brand new, so not really a deprecated OFX): it has something written in the Mocha pro 2020 release notes about Vegas:

https://borisfx.com/release-notes/mochapro-2020-release-notes/

If you scroll down to the known issues (or do a search on vegas) you see:

MO-10242 Rendering in Vegas causes host to crash if Deprecated QuickTime support is not enabled