That’s very reassuring to know. Fortunately we also have the developer of Wavelab inhere, PG1. My guess is, he also knows what he’s talking about (he is somewhat more laid-back about it though). I prefer to follow his advice over someone’s who debates trashing his preferences because it ‘also didn’t work for Cubase 10.5’.
I am also experiencing an immediate crash after launching of WL…again…
I did trash ALL my prefs before, then it did work for some time, didnt change a thing and now after the update it dissapears again after starting up.
It’s nervewrecking to rebuilt my prefs everytime an update is released.
PG I am with WL since V1.2 or so, and never had such troubles.
I am sure there is something you could do on your side to make it smoother.
respectfully,
1 Like
using WaveLab 11.0.10?
Windows or Mac?
Any crash log?
Philippe
Windows 10
11.0.10
Where do i find the crash log?
It just disappears after loading up… no crash, no blue screen or such…back to desktop
Open the file: \AppData\Roaming\Steinberg\WaveLab Pro 11\Startup.ini
and add the line:
crashReport=true
Thanks, this gives a small idea. This seems related to a plugin that is loaded in the Master Section.
Rather than trashing all your preferences, you can try this:
- Erase the file \AppData\Roaming\Steinberg\WaveLab Pro 11\Cache\Window Config\MasterSectionPreset.dat
- Or maintain Control while launching WaveLab (if you use the startup dialog, maintain Control) after confirming the startup dialog.
Either way will prevent the last Master Section config to load.
Question: do you have more than one screen? (my question, because the crash happens when a plugin window is apparently move to a new screen).
Yes I use 2 screens and the plugins are always on the second one.
I will try your suggestions and will get back.
thx
Alright, deleting the MasterSectionPreset.dat works, but as soon as i load the saved Mastersection Setup its going bye bye again.
That does not happen with WL 10.
FYI
Thats what I am using:, WES Audio, Waves, ADPTR, Izotope, hmm
Try to isolate the plugin causing the problem.
Nice. regardless of who you choose to listen to, Wavelab Elements 11.0.10 definitely has something wrong with it. Multiple things wrong. This past weekend in Los Angeles, W11 Elements decided it didn’t want to display any of my Waves plugins correctly. I could not make any changes because the display of any Waves plugin was 1 1/0th the size. And uneditable. I opened the same effects chain in Wavelab 10 and 9 and they all displayed perfectly. Are you listening to me now?
seem to have problems with the WES Audio plug ins.
I restarted and it loaded the last set of WES Plugs and dissapears.
Again, those work in WL 10 without any Problems.
FYI
As I mentioned, trashing the preferences did not help. But I just upgraded to Wavelab Pro 11.0.10, and it is working perfectly. Opens and closes fine, all plugins display at the proper size gui, and I can save as an mp3 with no error messages. This version of 11 feels stable. So my problems are solved, just not by the way you recommended. I stand by my statement - something is wrong with Wavelab 11 Elements, and whatever it is it’s not in Wavelab 11 Pro.
1 Like
WL 11 and some VST3 plugs don’t like Windows to be set to display other than 100% 
The preferences are Where in the wavelab folders?
Was this Post for me?
If So, I will check this after my Hospital stay and thanks for the moment 
Yes.
regards S-EH
FWIW I still can’t work with WL11.0.10.
The same Masterchain of Plugs which work fine in WL10 do not work with WL 11.xx.
if I restart the app the next time.
Somthing is wrong.
Thanks
It’s likely related to a single plugin (or plugin brand). While tedious, the only real solution is to remove plugins one by one until you find the problem plugin and then when you do, there is a 98% chance the fix has to be made by the plugin developer.
1 Like