Wavelab crashing on startup
-
- KVRAF
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
Many times when I install a new VST/VSTi (and I'm constantly testing new ones, free ones, evaluating, buying, etc.)Wavelab crashes on startup. It's a very time consuming process to empty the plug-ins folder, go through them one by one to see which one (or ocmbination) gets Wavelab to open again.
I am also open to suggestions on other Wave editors for Windows XP, maybe a clever alternative to Wavelab and Soundforge? I intend to master right in Tracktion, so I suppose plug-in support isn't a major issue. Just really good editing features would be nice.
I am also open to suggestions on other Wave editors for Windows XP, maybe a clever alternative to Wavelab and Soundforge? I intend to master right in Tracktion, so I suppose plug-in support isn't a major issue. Just really good editing features would be nice.
-
- KVRian
- 1325 posts since 1 Sep, 2004
You can actually see, which plugin the crash caused. It is shown at the splash screen, if the load failes. So no need to manually search the bad thing.
- KVRian
- 1469 posts since 18 Sep, 2004 from Suffolk, UK
Have you tried Audacity ?
Open Source, stable and free

Apart from that, I find Adobe Audition is very good
Open Source, stable and free
Apart from that, I find Adobe Audition is very good
-
- KVRAF
- Topic Starter
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
I noticed that, it was actually several of them. And some it passed by that crashed it before!jackle&hyde wrote:You can actually see, which plugin the crash caused. It is shown at the splash screen, if the load failes. So no need to manually search the bad thing.
The last time I went through the process, it was enough to move the instruments out, and all the effects worked. But now it doesn't even like PSP Vintage Warmer, which I've used in Wavelab a hundred times.
It would be handy if you could start Wavelab from the command line with a switch for safe mode. Is there such a thing? Then I could at least go in and set up a separate plugins folder for it.
Thanks for the tip on Audacity, I'll check it out!
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
Is that Wavelab 5? I've had pretty good luck with WL5 and plug-ins. With older versions, I found WL would just decide one day that it doesn't like a lot of plugins. I had to move the ones I wanted to use to the Steinberg\Wavelab\System\Plugins folder to get them back. You can also manipulate where and what WL looks at in the Preferneces/general dialogue. And you can always edit "C:\Program Files\Steinberg\Wavelab\Presets\Plugins\plugins to ignore.txt"
-
- KVRist
- 102 posts since 1 Feb, 2005 from Denmark
I don´t know how Wavelab works but
Cubase SX writes to an VST Plug File in Documents Settings/.../...Steinberg/Cubase.
When Cubase Crashes or I am having trouble with a plug I delete this file. Then Cubase writes a new one - Of course I have to remove the plug that are making trouble.
Something goes wrong with this file when Cubase writes in to it - It could have something to do with W XP security.But I am not shure.
Cubase SX writes to an VST Plug File in Documents Settings/.../...Steinberg/Cubase.
When Cubase Crashes or I am having trouble with a plug I delete this file. Then Cubase writes a new one - Of course I have to remove the plug that are making trouble.
Something goes wrong with this file when Cubase writes in to it - It could have something to do with W XP security.But I am not shure.
JSL
-
- KVRAF
- Topic Starter
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
That's the ticket! I downloaded a little freeware program that listed the entire contents of my VST directory in a text file, then I just removed the ones I need for mastering (EQ's, compressor, limiter), and pasted the list into this file. Finally I have a solid working Wavelab again!bduffy wrote:And you can always edit "C:\Program Files\Steinberg\Wavelab\Presets\Plugins\plugins to ignore.txt"
Thanks bduffy!
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
