Long opening and superclip bug

Hello,

I’m currently dealing with some weird things :

  1. wavelab is taking AGES to launch, like one minute. It just stays frozen, until suddenly, everything is accessible.

  2. 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)

  3. 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.

any ideas ?

Thanks

edit : i’m on win8, wavelab 8.0.3 (build 698), 32 bits

  1. Always, or only for some projects?
    Do you access files over a network?

  2. 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

  3. 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?

Philippe

Hi Philippe,

As always, it’s really appreciated that you answer this fast to questions ! :slight_smile:

  1. ok cool. Thanks for the history file path

  2. 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 ?

  1. 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 ?

Thanks !

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’m gonna try right now the tracer, thanks.

it scans really fast all plugins, the last lines are those ones :

32A8: Evaluating file : C:\Program Files\VSTPlugIns\xChorus.dll
32A8: Evaluating file : Vst2InternalPlugin\Ducker
32A8: Evaluating file : Vst2InternalPlugin\Peak Master
32A8: Evaluating file : Vst3ExInternalPlugin\MBit+ Dithering
32A8: Evaluating file : Vst3InternalPlugin\PluginSet-698
32A8: Plugin loop exit
2590: No need updating plugin cache.
2590: End checking plugins.

and then the wavelab workspace open, and are frozen for one minute, with no more loging.

hum i didn’t saw, after wavelab is loaded and operationnal, the tracer logs this :

468: InitBasis
C48: TComponentFactory::createClassInstance for “Baios” (“Asio Manager”)
C48: Idle handler added (06C9055C) Number of handlers: 1
C48: Idle handler added (06C90CC0) Number of handlers: 2
468: /InitBasis
468: EnsureAudioDevice
C48: m_deviceManager->countRegisteredDevices -> 4
C48: m_deviceManager->getDeviceName / id -> ASIO Hammerfall DSP / ASIO Hammerfall DSP
C48: Already registered: ASIO Hammerfall DSP
C48: m_deviceManager->getDeviceName / id -> Virus USB ASIO driver / Virus USB ASIO driver
C48: Already registered: Virus USB ASIO driver
C48: Will load device: ASIO Hammerfall DSP / ASIO Hammerfall DSP
C48: THostApplicationA::getMainWindow -> 004E0CAA
C48: Idle handler added (06C9C5B8) Number of handlers: 3
C48: Loaded device: ASIO Hammerfall DSP / ASIO Hammerfall DSP
C48: m_deviceManager->performPortActivations() -> 1
468: /EnsureAudioDevice

All that is normal. The question is: do you see some delay of several seconds between 2 steps of the log?

yes ~one minute, and wavelab is frozen during this time

Between which steps then?

C14: Evaluating file : C:\Program Files\VSTPlugIns\xChorus.dll
C14: Evaluating file : Vst2InternalPlugin\Ducker
C14: Evaluating file : Vst2InternalPlugin\Peak Master
C14: Evaluating file : Vst3ExInternalPlugin\MBit+ Dithering
C14: Evaluating file : Vst3InternalPlugin\PluginSet-698
C14: Plugin loop exit
168C: No need updating plugin cache.
168C: End checking plugins.

Wavelab workspace open and are frozen for one minute
then wavelab unfreeze
then the log shouts

168C: InitBasis
21C: TComponentFactory::createClassInstance for “Baios” (“Asio Manager”)
21C: Idle handler added (0B0B055C) Number of handlers: 1
21C: Idle handler added (0B0B0CC0) Number of handlers: 2
168C: /InitBasis
168C: EnsureAudioDevice
21C: m_deviceManager->countRegisteredDevices -> 4
21C: m_deviceManager->getDeviceName / id -> ASIO Hammerfall DSP / ASIO Hammerfall DSP
21C: Already registered: ASIO Hammerfall DSP
21C: m_deviceManager->getDeviceName / id -> Virus USB ASIO driver / Virus USB ASIO driver
21C: Already registered: Virus USB ASIO driver
21C: Will load device: ASIO Hammerfall DSP / ASIO Hammerfall DSP
21C: THostApplicationA::getMainWindow -> 000A0A2A
21C: Idle handler added (0B0BC5E8) Number of handlers: 3
21C: Loaded device: ASIO Hammerfall DSP / ASIO Hammerfall DSP
21C: m_deviceManager->performPortActivations() -> 1
168C: /EnsureAudioDevice

Any ideas Philippe ?

Thanks

The only thing I can imagine, is that the workspace contains some montage(s) that contain plugins that takes time to initialize (eg. Waves).

The problem happens without any montage loading …

I did have some problem with e licencer and cubase 7, so I installed the last e licencer software, just in case, and it did nothing about that also.

Try to erase these setting files:
C:\Users\YourName\AppData\Roaming\Steinberg\WaveLab 8\Cache\Window Config\MasterSectionPreset.dat
C:\Users\YourName\AppData\Roaming\Steinberg\WaveLab 8\Preferences\General.dat

I tried, still the same.

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.

Ok, did all that, problem still the same.

I did find a log in the wavelab preferences, from 4 days ago. As you can see, it’s more 2min and a half than 1 …

[2014/01/24 17:53:59] INFO: Evaluating file : Vst2InternalPlugin\Ducker
[2014/01/24 17:53:59] INFO: Evaluating file : Vst2InternalPlugin\Peak Master
[2014/01/24 17:53:59] INFO: Evaluating file : Vst3ExInternalPlugin\MBit+ Dithering
[2014/01/24 17:53:59] INFO: Evaluating file : Vst3InternalPlugin\PluginSet-698
[2014/01/24 17:53:59] INFO: Plugin loop exit
[2014/01/24 17:53:59] INFO: No need updating plugin cache.
[2014/01/24 17:53:59] INFO: End checking plugins.
[2014/01/24 17:56:24] INFO: InitBasis
[2014/01/24 17:56:24] INFO: TComponentFactory::createClassInstance for “Baios” (“Asio Manager”)
[2014/01/24 17:56:24] INFO: Idle handler added (0B0B055C) Number of handlers: 1
[2014/01/24 17:56:24] INFO: Idle handler added (0B0B0CC0) Number of handlers: 2
[2014/01/24 17:56:24] INFO: /InitBasis
[2014/01/24 17:56:24] INFO: EnsureAudioDevice
[2014/01/24 17:56:24] INFO: m_deviceManager->countRegisteredDevices -> 4
[2014/01/24 17:56:24] INFO: m_deviceManager->getDeviceName / id -> ASIO Hammerfall DSP / ASIO Hammerfall DSP
[2014/01/24 17:56:24] INFO: Already registered: ASIO Hammerfall DSP
[2014/01/24 17:56:24] INFO: m_deviceManager->getDeviceName / id -> Virus USB ASIO driver / Virus USB ASIO driver
[2014/01/24 17:56:24] INFO: Already registered: Virus USB ASIO driver
[2014/01/24 17:56:24] INFO: Will load device: ASIO Hammerfall DSP / ASIO Hammerfall DSP
[2014/01/24 17:56:24] INFO: THostApplicationA::getMainWindow -> 000A0A2A
[2014/01/24 17:56:24] INFO: Idle handler added (0B0BC5E8) Number of handlers: 3
[2014/01/24 17:56:24] INFO: Loaded device: ASIO Hammerfall DSP / ASIO Hammerfall DSP
[2014/01/24 17:56:24] INFO: m_deviceManager->performPortActivations() -> 1
[2014/01/24 17:56:24] INFO: /EnsureAudioDevice
[2014/01/24 17:57:52] INFO: Control + No key / 0x202, 0x1D, 0x11
[2014/01/24 17:57:55] INFO: Dialog name for Assistant: main_preferences_dialog
[2014/01/24 17:58:04] INFO: ////// WaveLab Diagnostics //////
[2014/01/24 17:58:04] INFO: WaveLab 8.0.3 (build 698)
[2014/01/24 17:58:04] INFO: Operating System: Windows 8

Strange. If you have a single audio file workspace with no file open, same thing?

Without montage window, same thing.

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.