wavelab is taking AGES to launch, like one minute. It just stays frozen, until suddenly, everything is accessible.
when wavelab bugs and I kill it with the task manager, all the previous history is lost : by previous history, I mean the recent files (in file menu or by right clicking on icons in commuting bar)
I use a lot the superclip feature for mastering : that way, I save the master chain in the submontage, and render the file with hardware processing, and I get the mastered file back in the master montage. But for some reason, on some project, I open it the next day, and wavelab says that ALL submontages needs to be rendered, and it does that even on all backup in the Backup.mon folder. That’s really frustrating, and takes a lot of times to re-render stuff.
Always, or only for some projects?
Do you access files over a network?
We’ll try to improve this case. In the mean time, you could make from time to time a backup of the following file, that contains the file history:
C:\Users[YourName]\AppData\Roaming\Steinberg\WaveLab 8\Cache\lru.txt
WaveLab checks file date to guess if something is to be updated or not. Do you see any reason why the dates could be affected? Again, do you access files over a network?
As always, it’s really appreciated that you answer this fast to questions !
ok cool. Thanks for the history file path
I quit wavelab with ctrl+Q, and when I open it again, all my projects reopen. But I did just test with closing all projects then ctrl+Q, wavelab takes 1 minute to open, and there is no project loaded. And I’m not accessing files on network, everything is on my computer. And btw, I disabled my antivirus software and other things like that : no changes.
Is there a log of the application loading somethere to see what takes this long ?
There again, not accessing files over a network. And No reason why the dates could be affected.
That leads me to this date cheking : when you make multiple version (incremental saving) of a project, if the sub montages are changing, wavelab absolutely wants to re-render them. Could it just be a warning, with a choise, like a list, when you can check or not, clip by clip, which ones to re render and which ones to leave alone ?
For the long loading time, I have no clue. Do you think it’s proportional to the number of super clips?
There is a possibility of log, but without timing information. Hence you could look at it in real time and maybe guess something.
Do this: Run WaveLab. Then press and maintain the Alt key, and using the mouse, open the main preferences.
Now you can see a new tab called “Diagnostics”.
Click on Reports
Then enable all options
Quit WaveLab.
Under Windows:
Run C:\Program Files\Steinberg\WaveLab 8.5\Tools\Tracer.exe
Launch WaveLab.
The Tracer/Console window will display many informations.
Maybe you can see when WaveLab halts. No guarantee, though.
When you don’t need diagnostics, you should switch them off, to avoid a small performance lost.
if the sub montages are changing, wavelab absolutely wants to re-render them.
If there are not rendered, that could lead to confusing situations for the user.
It’s not a question of super clips or not, because when opening wavelab empty it takes one minute to just be able to use the program (with no files, no montages opened in the workspaces).
I installed WL on my other boot (win 7, on the same computer) and there is absolutely no problems.
Could this be related to win 8.1 ? I’m on 8 since one year, had no problems with wavelab, but as far as I remember, the long loading time problem is there for a month and a half MAX. And not so long ago I did upgrade to win 8.1 …
I’m gonna try uninstalling wavelab completely, removing preferences and all that stuff and re-installing again.
But then if I open a montage window, it freezes like 10 seconds.
What’s weird is yesterday, I uninstalled a lot of things on my computer, also my old Wavelab 7 install, even my audio card driver, disabled my network and then uninstalled my antivirus, etc.
I re installed Wavelab 8 only. At first launch, Wavelab did freeze a few second. I did setup my preferences, closed Wavelab, relaunched : freezed a little bit more longer. After 2-3 start/quit, it launched really slow, and stayed that way.
I’m thinking about trying a fresh install of win 8 and test if wavelab is still slow, but I don’t think I have the time to do that for the moment (and I need to source a win 8 DVD).
And for info, that is my clean boot for professional work, so there is absolutely no junk installed on this system.
