WL13.0.20 still crashes when loading clip plugin chains

@PG1 WL13.0.20 still crashes randomly when loading clip effect plugin chains that were saved with the montage or saved as a plugin chain. I removed the program and reinstalled the updated version, deleting all of the application data before reinstalling to be sure it’s fresh which was confirmed by the dialog “this is the first time you have run WL13” upon opening, and this issue still persists on the montages that previously crashed. If I recreate a new montage in WL13 with the exact same plugin chain, it will work fine. The exact same chain of plugins loads and works repeatedly without issue on WL12 as well. I’ve provided the crash report in the previous thread about WL13 crashing when opening where this issue wasn’t resolved so I was hoping this update would fix it. Something is getting corrupted in certain instances when loading a clip plugin chain in WL13. This does not occur on every instance of any of the plugins, or like I said even if the exact plugin chain has been created in another clip in WL13 it works fine as well passing audio without issue until it sometimes randomly crashes. Once it crashes, that montage is not openable again except in safe mode which doesn’t allow me to view the plugin settings so I’ve lost any work I’ve done in that montage. I took the time to recreate the same montage with each plugin individually and none of them crashed, so it’s not the plugins causing the problem.

What could be causing this? I suspect it has something to do with buffering when loading clip effects since this will happen mid way during the clip effect loading process when opening the montage. It does not always crash on the same plugin either.

How is the buffering or cache of clip effect plugins different in WL13?

Thank you.

There is no change compared to WaveLab 12.

When you come to the point of having e a montage that crashes, does it then happen 100% of the time after with this montage, or is it still random?

Are some of the involved plugins protected with iLok?

Once a particular montage crashes WL13, it won’t reopen again. Even after re-installing the program and deleting app data etc. Loading that specific saved plugin chain to a new montage also crashes. Loading the exact same plugins in the same order in a new montage does not crash in WL13. Some of the plugins are iLok protected, but they are authorized properly and always working fine in WL12 and other DAWs. This seems like a loading error of some sort. I can’t figure out why it crashes sometimes and not always with the same sequence. It appears to get corrupted somehow once it first crashes.
Thanks.

Also, the point of the crash happening is not the same each time I attempt to load it. It doesn’t seem like there is a specific plugin that’s causing this problem. Sometimes it will load one or two and crash, on other attempts it will load more plugins before crashing. None of this ever happens in WL12 with the same exact plugin chain.

Please send me such a plug-in chain file that causes a crash. But one that has no iLok-protected plugin.

Does WL13 not support iLok protected plug ins?

It does of course but PG may not have that particular plugin.

I’m not trying to create montages that crash. The ones that do have the combination of plug-ins they had for that session. Since it’s a phenomenon that does not occur with a set plug in chain, I cannot create a chain intentionally that will crash. I haven’t had a plug-in chain without something that is iLok protected in years. None of them had ever crashed in WL12

I am not saying that iLok is the cause, but I would like to exclude potential causes.
iLok copy protection sometimes cause application crashes and various stability issues according to widespread reports on social media platforms.

Send me anyway both a plugin chain as well as a montage that crash, so that I can (maybe) find if there is a data fault in the files, independently from the plugins.

FWIW, my direct experience is that Pace did a big update over the last few days (I always auto check this after a big update like to WL 13.0.20).

Thanks Paul, I’ll check that too.

Unfortunately, updating Pace did not resolve the issue but glad to have it updated regardless.

And did you switch to only using VST-3 plugins?

Yes, I also tried that, thanks for the suggestion, and I’ve swapped that plugin out to a VST3 in my start template going forward. I opened the corrupted montage in safe mode, switched to the VST3 version, saved as a new montage and also saved another montage without any UAD or VST2 plugins and both still crash when opening the montage while loading the plugins, and not at the same place in the chain every time. Probably Gremlins in WL13? I’m just going to keep using WL12 which works completely fine with all of these plugins and has never had any of these problems. WL13 was also working normally for the few days I used it except for when random montages would crash and then couldn’t be reopened, I even tried re-installing WL and deleting app data. The montage that now can’t be opened was previously opened successfully multiple times and I worked on a multi hour session on that montage with the same plugin chain before it crashed and is now corrupted somehow. I started over on that project in WL12 with the same exact plugin chain and had no problems (except for losing the time I had already put into it)

Perhaps another user will experience this issue as well and eventually locate the cause. Until then I’m good just using WL12.