Before WaveLab 11 with WL10 i had never crashed by loading vst mastering chains. Since WaveLab 11 i get a lot of wavelab crashed. It start’s and then suddenly after loading vsts, it crashes without any message. Then i need to make use of my batchfile, which deletes this file:
del MasterSectionPreset.dat
I am realy unhappy. Where the heck i can check, if it’s the same plugin wich make’s my system crash??
Is it possible to downgrade back to WL 10 ?? I don’t see any godies to use WL11!
Thank’s a lot for you hint! All of them are working well until i close WaveLab and restart WaveLab 10 or 11 (tried 10 yesterday). As soon all where loaded → takk, and good bye… I think it must be something with VST3… Never had this a year ago… It would be interessting to know, where the debug file is or how i could activate it. So by adding them one by one, works fine. Never had a crash. Only when i start wavelab with 10 VSTs added like izotope or softube and waves… Strange… Fabfilter L2 seem’s also by unfriendly i think…
These are sometimes found at fault but not waves and Fabfilter. Try for a while without the formers. Also, loading the Master Section preset is an option that you can switch off.
Under Windows (are you there?), 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.
Thank’s a lot for you help… The interessting thing is:
WaveLabPro11.exe caused ACCESS_VIOLATION in module “C:\Users\xxx\AppData\Local\Temp.vtFA61.tmp” at 0033:00000000122FE1E2, Vertigo()+845378 byte(s)
Found that Vertigo Sound makes the crash… Hm…
Asking myself how to get rid of such crashes?
Ideas? Contact VertigoSound?
Best, Fab
PS: Yes, Wavelab crashes by opening it with that chain and if i’m in at wavelab and loading that presaved chain wavelab crashes… But for now, i know which plugin is the culpable…
Made a crash dump analysis. It’s a access denied error!
PROCESS_NAME: WaveLabPro11.exe
READ_ADDRESS: ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
Yes, VSE-4 out since some days. Awesome EQ but smashing Wavelab… Only if i open an existing mastering chain or load the chain in wavelab. If i load it from an empty chain, no issues…
I ran into this yesterday and thought to see here what I’m doing wrong but @oldskool4ever already reported it
Wavelab 11 Plugin Chain bug?
Mac mini M1 / macOS 13.1 (22C65). WL pro 11.0.30 build 114 / plugin 11.5.30.82
While loading my plug-in chain on a clip or output, WaveLab crashes.
WL 10 does load the same plug-chain but with 10 plugins instead of 16 because WL 10 can only handle 10 plugins?
Tried saving the chain, and then every plugin in bypass (also on the plugin itself if the option is on it)
But when opening in WL11, WL crashes.
10 plugins (both in bypass) will work… @Justin_Perkins I use the JP template and had also looked at the ignore plugin list and emptied it because it belongs to JP (not because of JP himself but I don’t think that helps either… I don’t get a bug report either…I hope this contributes something
I’ll see if updating helps
Greetings Muziekkamer
@oldskool4ever@Justin_Perkins History pdf P-5239 Loading a plug-in chain preset in the audio montage Inspector after using the
Clean and Enhance options now works as expected.
Yesssss!!! 11.1.20.62 works well! now also get a report of certain vst2 plugins that don’t work from PA de BAX as an example.
Greetings Muziekkamer
update …in ROsetta all 16 plugins load (in the chain) work great here
Hi OldSkool4Ever, Well today problems again now it was a Sonnox plug-in removed the VSt2 now it works well again without Rosetta…Now just see why my TC Electronic Clarty M plug-in is no longer found by WL
Thanks JP, seeing now that part of my problem was Oxford Inflator I thought everything is working… so I’m done and going to work without Rosetta… Thank you so much!