I am starting to get upset with WL 8.5.3

Personally, I use WL in what I think would objectively be regarded as an ‘intense way’. Every day.

For some reason, I do not have the level of issues that have plagued some users (the 1s and 0s are smiling on me). But, what happened to me last night in a highly pressured environment was not cool.

And, FWIW, I can tell you that WYCA’s team KNOW what they are doing.

I do agree that crash dumps etc would be a good start.

I am still waiting to learn where I find these for WL?

…plus: I am a “hardcore” WL user. I am nearly using every feature, with many plugins - many hours every day.
So, as someone before said: details matter!
BTW, I use a RME HDSP 9632 interface…

The way I use WL is for Mastering with two to three plugins. Or I do restoration work again using maybe one plugin at a time. Or I am transferring something off a reel to reel tape or cassette or DAT on to WL. The crashes have all been random.Sometimes I get a white screen, sometimes I get a notice that Wavelab has stopped working. Sometimes my whole computer crashes to a BSOD. When I get eh BSOD is is always something different but usually involves a “mini dump”. I have spent hours trying to get WL to crash like it did the last time but with no luck. The one constant is that WL does not seem to play well with FAB plugins. I don’t know enough about how programmers work but if this is a known fact couldn’t PG pick up the phone or email the guys at FAB and find out why their stuff does not play well with WL. I know I am not the only one who is having problems with FAB Filters and WL it is all over the WWW. There are other plugins that have strange problems with their GUIs and again is it a big problem for all the programmers to talk about problems and FIX THEM! Does this have something to do with “intellectual rights” and programmers can’t share information? If it does couldn’t they get everyone to sighn a non disclosure contract?

Honestly I would rather PG fix this version of WL before he starts on WL 9 which will probably have its own set of start up problems.

I am half way through my new computer build and hopefully with all state of the art components it will run WL better, but I am not sure if that will be the case if there is something in WL that is causing random crashes.

By the way once you go down the slippery slope of random crashes it seem to get much worse the more you use WL after the crashes have started. Could this be something in the way WL caches its information or stores things in the preferences? Just wondering.FWIW

I guess … just to allay any doubt … that I should add that I am still WL 8.5’s ‘biggest fan’. Love what it can do and how it does it.

It is easy to loose sight of the fact that it has been absolutely rock solid for me now for such a long time across different versions that when something like this surfaces it is, in context, unusual indeed. In fact, if I don’t do the things that consistently causes the white screen/crash it still is very stable here.

I am sure that the issues will be resolved.

Brand new super computer. Brand new install of WL 8.5.3. Doing a simple montage. Only the montage and edit widows are open. Press play. WL crashes.

Here is what I have.


Sentey® Power Supply 725w Xpp725-hs / Computer Power Supply ATX / 140mm Fan Sleeve Bearing / 48ampers / 5 Sata / 2 Pci-e 6-2 / SLI Ready / Crossfire Ready / 115-230 Voltage / Power Cord / 3 Years Warranty

Corsair Vengeance Series Black C70 Mid Tower Computer Case (CC-9011016-WW)

Cooler Master Hyper 212 EVO - CPU Cooler with 120mm PWM Fan (RR-212E-20PK-R2)

Kingston HyperX FURY 16GB Kit (2x8GB) 1866MHz DDR3 CL10 DIMM - Blue (HX318C10FK2/16)

MSI ATX DDR3 2600 LGA 1150 Motherboards H97 GAMING 3

Intel Core i5-4460 LGA 1150 CPU - BX80646I54460

Samsung 850 Pro 256GB 2.5-Inch SATA III Internal SSD (MZ-7KE256BW)

Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD (MZ-75E500B/AM)

WIN 7 PRO SP1 64 Bit OEM 1PK

NVIDIA GT 740 overclocked video card.

My other passion is Fight Simulator and this is the same setup I have for my Flight Simulator that has been running since last spring without a crash or a hiccup. I know there are better/different systems out there and I could have gone with an I7 processor but this is what I decided to do.

The computer is running nicely and when WL runs it is doing saving in one second or less of a 3 minute file and processing that same file in 10 seconds. NICE

Any ideas???

Thanks in advance

Do you have an actual audio interface in this new machine? If so - what is it?


What is the sample rate and bit depth of the montage?

How many tracks on the montage?

Under Windows, you can generate one crash dump from WaveLab if you do so:
While pressing the Alternate key (press first and maintain), select “Gobal 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”, at the bottom. If a crash happens, one crash dump is generated.

Thank you!

After I finish these urgent jobs I’ll try and reproduce a crash for you.

Thank you again …

Yes it is an RME HDSP 9632 bought from these people http://www.sweetwater.com/store/detail/HDSP9632?adpos=1t1&creative=83049426001&device=c&matchtype=b&network=g&gclid=CKmKioev-8cCFUqRHwodJrMBEg..I moved it over from the other computer.

44.1/24 bit

Stereo/ Two tracks

Thanks! I will try that.

I tried it and…you have to be in the “track” window and not the montage and you can leave this on all the time with a check mark in the Diagnostics tab. Who knew???

What RME driver are you using with the new box?


I use here the same soundcard with the latest drivers and it works perfect with Wavelab 8.5.3.
What settings do you use ? (SR, clocksource )


This one http://www.rme-audio.de/download/driver_hdsp_win_410.zip it is the most current one I know of. Is there a better one?

That’s the one I am running. And I still get crashes, freezes etc. If you are hoping to “fix” this yourself - I would not invest too much time in it.

This is a discussion for PG to have with folks at RME - because as I have stated in many a thread response already - WL is not or cannot communicate sample rate changes correctly with the latest RME drivers. I have been fighting the same for several years now.

I notice that you are 44.1/24bit. If you want to get work done - suggest a standard of 44.1/16bit and you will probably be fine.

Until PG and RME get their heads together on this - nothing will change. Unfortunately.

Sadly - I can have files of all kinds of sample rates and bit depths open in Studio One Or IzoTope RX Advanced and never see any issues. The rates/depth switches perfectly every time. Only in WL does everything freeze hard.



  1. Wavelab cannot support the plugin INSIGHT and will close. Only the edit window open

  2. Wavelab cannot continue due to a problem with the plugin FAB Pro L. Only the edit window open

  3. Wavelab crashed today playing a file with no plugins and no warning. 44.1 16 bit Wav file

These problems are all on a clean machine with nothing extra running on it. There has to be a MAJOR fix and soon.

It is beginning to look like WL does not play well with other developer’s plugins and that is not acceptable in today’s world.

I am running Sound Forge on the same machine as well as Samplitude and Audition with none of these problems.

How can I go back to 8.5.2 and make sure I have all the “junque” off my machine left over from 8.5.3 with out doing a fresh install of Windows 7.

Personal Note: PG can you please get this fixed before spending a lot of time on 9.0?? - Thanks in advance!!!

What a royal mess.

I have no clue what this happens to you. This is not a general problem.
If you run in 32 bit, can you try in 64 bit, or reciprocally?
And what about a crash log?

I have the crash log and can post it. it is like WL is possessed. I have been with WL since version 1.6 and never had all the problems I am having now. The last stable version for me was Version 6. Thanks for your concern.

Are you able to at least temporarily try another sound card or interface to rule out the RME?

It seems like that could be a factor at this point.