Hi - I’m experiencing a fairly frequent crash when loading a plugin chain to a clip in Wavelab:
select clip
open floating clip inspector
click load plug-in chain
browse for .plugs file
click open
About 1 in 10 times the plugins start to load and then a crash happens - Wavelab closes without warning or error message. I can’t quite pinpoint the exact circumstances when this happens, as the plugin chain is always the same.
I realise I could help diagnose this by repeated experiment and trying the chain with each of the plugins present or not to find the culprit - but due to workload it’s difficult to allocate time to experiment
So - is there a log file I could find and send to help diagnose the issue? I have looked for Windows crash dumps, but there is only one and I’m not sure it’s related to this repeated crash.
Under Windows, you can generate one crash dump from WaveLab if you do so:
While pressing the Alternate key (press first and maintain), select “Global preferences” from the WaveLab menu with the mouse.
In that case, there is a new tab called “Diagnostics”. There you can activate several functions.
Activate the option “Enable crash report”. Quit and relaunch WaveLab.
If a crash happens, one crash dump is generated and a dialog proposes to save it.
In the crashdumps folder there are two old dumps from WL but nothing from recent crashes - though I am pretty sure this is the only crash type I have experienced in WL. Dumps here if that is helpful: Unique Download Link | WeTransfer
Otherwise I will check the folder after other crashes.
Thanks for checking them out - I’ve now had a couple more crashes and no crash dump is being created. Should I create a special entry for the WL exe in LocalDumps in the registry? And what should be the key values?
Perhaps you might want to share the plugin chain that was used on the last crash … with the idea that some here might have had experience with a particular plugin that has been troublesome. Just a thought.
@PG1 Thanks for your efforts - I will try the long way
And thanks @Paul_Rat_Blakey - if there’s no easy way to trap the crash!
The clip chain loads the following, all disabled to start with:
TB Pro Audio ABLM2
TDR Infrasonic
SIR Standard Clip
TDR Slick EQ M
TB Pro Audio DSEQ3
Ozone 11 Advance
I also experienced a crash last night loading the following chain for the first time:
TDR Slick EQ GE
Ozone 11 Vintage Limiter
Lin Dither
I’m wondering if it’s a memory issue, as yesterday the crashes happened frequently as I worked towards the end of a 15 clip Montage. I have 32GB RAM, Windows was only reporting ~20GB used at this point - but I believe the Ozone mothership is something of a memory hog?
Eitherway, this is slowing down my workflow now, so adding plugins manually won’t be so much of a penalty!
Thanks for the detail and I am sure others will chime in with possible suspects.
For me, in the first chain, my money would be on the TB plugins. Although it says it’s been tested with WL,and I have almost zero direct experience, the AI matching functions may not play well with others and try to load the last comparison. Maybe take a moment to do a simple single plug test on them with a 32 f 96 sine wav and render at 32 f 96 and see what the result looks like. Or of it crashes. And/or take it out of the chain and see if that results in stability.
In the second chain, and although it is a stock plugin, the Lin Dither always seems to have something going on under the hood. Maybe substitute that for another dither like GoodHertz.
A search for Ozone modules will show a long history of concerns that it is a memory hog.
My personal experience with TDR is that they are well coded by someone that really does know what they are doing and solid performers with WL.
I totally feel for you and hope you get this sorted quickly.
Cheers - appreciate you taking the time to check this through!
I’m trying another approach now - rather than load plugins each time, I’ll copy and paste the chain using that excellent feature in WL … hopefully I can narrow down the crash.
I love the TB plugins though - lots of bang for not many bucks! Also the same with TDR, though I have another small problem in WL with TDR plugins not always saving patches properly… that’s for another day!
Thanks for highlighting that @stingray - I never thought that a VST would not officially support a host! Hopefully I can identify whether it’s Ozone or one of the others… then I can think about changes to my toolset, or other workarounds.
Many VST plugin developers do not test in Wavelab. As mentioned in the other topic the only way to make things change on this front is to contact the plugin developer.
I’d recommend using VST3 plugins only and if it doesn’t function in Wavelab then simply don’t use it (yes this is a radical but pragmatic solution!) and tell the developer that the plugin is causing issues in Wavelab. My view is that all plugin developers should test their plugins in Wavelab as a matter of standard practice.
Perhaps try removing Ozone from the chain presets you outline above and then test again for crashes. If the issues are intermittent it may be more difficult to pin down.
In a previous life I was a support engineer for software and hardware, so my instinct is to look for logs… but failing that you are right - the good old-fashioned process of elimination
